Zc-resourcelibrary

Latest version: v2.0.0

Safety actively analyzes 628477 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 4

1.2.0

==================

- Use ``zope.site`` instead of ``zope.app.component``. Removes direct
dependency on ``zope.app.component``.

1.1.0

==================

New features:

- An attempt to generate resource URLs using the "resources view" ()
is now made; if unsuccesful, we fall back to the previous method of
crafting the URL by hand from the site url. This ensures that the
resource library respects the existing plugging points for resource
publishing (see ``zope.app.publisher.browser.resources``).

- You can now explicitly specify where resource links should be
inserted using the special marker comment '<!-- zc.resourcelibrary -->'.

1.0.2

==================

- Remove zope.app.zapi from dependencies, substituting
its uses with direct imports.

- Use zope-dev at zope.org mailing list address instead of
zope3-dev at zope.org as the latter one is retired.

- Change "cheeseshop" to "pypi" in the package homepage.

1.0.1

==================

Bugs fixed:

- added the behavior from the standard Zope 3 response to guess that a body
that is not HTML without an explicit mimetype should have a
'text/plain' mimetype. This means that, for instance, redirects with
a body of '' and no explicit content type will no longer cause an
exception in the resourcelibrary response code.

1.0.0

==================

New features:

- You can now provide an alternative "directory-resource"
factory. This facilitates implementation of dynamic resources.


Bugs fixed:

- Updated the functional-testing zcml file to get rid of a deprecation
warning.

0.8.2

==================

- bug fix: when checking content type, take into account that it may be None

Page 2 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.