Cykooz-djangorecipe

Latest version: v1.2.1

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

Scan your dependencies

Page 5 of 5

0.11

----

- Another go at fixing the updating problem (250811) by making sure
the update method is always called. It would not be called in the
previous version since the recipe wrote a random secret (if it
wasn't specified) to the options for use with a template. Buildout
saw this as a change in options and therefore always decided to
un-install & install.

- When both projectegg and wsgi=True are specified, the generated wsgi
file did not have the correct settings file in it. This has been
fixed with a patch from Dan Fairs.

- The recipe now has logging. All print statements have been replaced
and a few extra logging calls have been added. This makes the recipe
more informative about long running tasks. Thanks erny for the patch
from issue 260628.

0.10

----

- The recipe no longer expects the top level directory name in a
release tarball to be consistent with the version number. This fixes
issue 260097. Thanks to erny for reporting this issue and
suggesting a solution.

- Revision pinns for the svn checkout now stay pinned when re-running
the buildout. This fixes issue 250811. Thanks to Remco for
reporting this.

- Added an option to specify an egg to use as the project. This
disables the code which creates the basic project structure. Thanks
to Dan Fairs for the patch from issue 252647.

0.9.1

-----

- Fixed the previous release which was broken due to a missing
manifest file

0.9

---

- The settings option is fixed so that it supports arbitrary depth
settings paths (example; `conf.customer.development`).

- The version argument now excepts a full svn url as well. You can use
this to get a branch or fix any url to a specific revision with the
standard svn syntax

- The wsgi script is no longer made executable and readable only by
the user who ran buildout. This avoids problems with deployment.

Page 5 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.