Skip to main content

more.static: BowerStatic integration for Morepath

more.static integrates BowerStatic into Morepath.

Also see Static resources with Morepath.

CHANGES

0.6 (2014-11-15)

  • Use BowerStatic 0.7, which makes Tween-based integration much simpler.

  • There was a bug where references were injected but not actually properly published.

0.5 (2014-11-13)

  • It is no longer necessary to wrap the application with Bower using WSGI. Instead a tween is used. To migrate, simply replace the following:

    wsgi = bower.wrap(App())
    morepath.run(wsgi)

    With this:

    morepath.run(App())
  • Requires Morepath 0.8 and Bowerstatic 0.6.

0.4 (2014-11-03)

  • Adjust to handle Morepath 0.7 API changes concerning request construction.

0.3 (2014-09-08)

  • The 0.2 introduced a component method to obtain a component object and thus its URL. This didn’t turn out to be compatible with local components, so I’ve changed it to get_component instead:

    request.static_components.get_component('jquery').url()
  • Depend on version 0.4 of BowerStatic.

0.2 (2014-08-28)

  • Make available a static_components property on the request, which is a BowerStatic static components object. You can use this primarily to get the URL to a component, like this:

    request.static_components.component('jquery').url()
  • Depend on version 0.3 of BowerStatic.

0.1 (2014-07-07)

  • Initial public release.

Metadata

Release files for more.static 0.6

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for more.static 0.6
File Size Uploaded Provenance Actions
more.static-0.6.zip 11.6 kB Without provenance Details for more.static-0.6.zip

Release files / more.static-0.6.zip

Download URL more.static-0.6.zip
Size 11.6 kB
Tags Source
SHA-256 checksum
How to use checksums
580c0f74b1627b8b505821ab21c043fd63f640572a615bcbc3f5b9dd6119c691
BLAKE2b-256 checksum
How to use checksums
f0643708b7cd94a512391dda9d3713918c2a5e4e2b14df31f926144237743380
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for more.static 0.6

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page