Mk.recipe.modwsgi

Latest version: v0.1

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

Scan your dependencies

Page 2 of 3

1.3

----------------------

- Gracefully handle .ini files that do not contain logging configuration.
[wichert]

- don't overwrite existing file permissions when setting execute permission.
This fixes `issue 1
<https://github.com/wichert/collective.recipe.modwsgi/pull/1>`_
[fredj]

1.2

--------------------

- Initialise the python logging module. Based on a patch from Philip Kershaw,
which was based on a discussion on pylons-discuss:
http://groups.google.com/group/pylons-discuss/browse_thread/thread/9b9add4529b3779c?pli=1
[wichert]

1.1

--------------------

* Add an 'extra-paths' option, similar the the zc.recipe.egg one.
[chrism]

1.0

----------------------

* No changes.
[wichert]

1.0rc1

----------------------

* Update the generated wrapper to test if a path is already in sys.path
before adding it. This prevents paths being duplicated in sys.path
when mod_wsgi reloads the module.
[wichert]

1.0b3

---------------------

* Do not make the recipe a subclass of zc.recipe.egg.Eggs but
use a local instance to determine the working set.
[wichert]

* Format the sys.path changes in the wrapper to make it more
human readable. This is purely cosmetic to help with debugging.
[wichert]

* Also recreate the wsgi wrapper file when updating a buildout part.
This is needed to get get changes to versions in the working set
(such as different version pins) reflected in the wrapper.
[wichert]

Page 2 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.