forked from stefanfoulis/djangorecipe
-
Notifications
You must be signed in to change notification settings - Fork 0
/
CHANGES.txt
198 lines (138 loc) · 5.49 KB
/
CHANGES.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
Changes
=======
0.20
----
- The recipe know makes the `django` package know to setuptools during install.
This closes #397864. Thanks to Daniel Bruce and Dan Fairs for the patch.
- Fixed #451065 which fixes a problem with the WSGI log file option.
- Added the posibilty to configure more FCGI related settings. Thanks to Vasily
Sulatskov for the patch.
0.19.2
------
- The generated WSGI & FCGI scripts are now properly removed when
options change (fixes #328182). Thanks to Horst Gutmann for the
patch.
- Scripts are now updated when dependencies change. This fixes #44658,
thanks to Paul Carduner for the patch.
0.19.1
------
- Applied fix for the change in WSGI script generation. The previous
release did not work properly.
0.19
----
- When running again with non-newest set the recipe will no longer
update the Subversion checkout. Thanks to vinilios for the patch.
- The WSGI and FCGI scripts are now generated using Buildout's own
system. This makes them more similar to the generated manage script
with regard to the setup of paths. Thanks to Jannis Leidel for the
patch.
0.18
----
- Paths from eggs and extra-paths now get precedence over the default
system path (fixes #370420). Thanks to Horst Gutmann for the patch.
- The generated WSGI script now uses the `python` option if
present. This fixes #361695.
0.17.4
------
- Fixed a problem when not running in verbose mode (fixes #375151).
0.17.3
------
- Removed dependency on setuptools_bzr since it does not seem to work
like I expected.
0.17.2
------
- Changed the download code to use urllib2. This should make it work
from behind proxies (fixes #362822). Thanks to pauld for the patch.
0.17.1
------
- Fixed a problem with the new WSGI logging option #348797. Thanks to
Bertrand Mathieu for the patch.
- Disable generation of the WSGI log if "wsgilog" isn't set, thanks to
Jacob Kaplan-Moss for the patch.
- Updated buildout.cfg and .bzrignore, thanks Jacob Kaplan-Moss.
0.17
----
- Added an option to specify a log file for output redirection from
the WSGI script. Thanks to Guido Wesdorp for the patch.
0.16
----
- Subversion aliases are now supported (something like
svn+mystuff://myjunk). Thanks to Remco for the patch.
0.15.2
------
- Update to move pth-files finder from the __init__ method to the
install method so it runs in buildout-order, else it looks for pth
files in dirs that may not yet exist. Thanks to Chris Shenton for
the update to his original patch.
0.15.1
------
- Update to make the previously added pth-files option better
documented.
0.15
----
- Added "pth-files" option to add libraries to extra-paths from
site .pth files. Thanks to Chris Shenton for the patch.
0.14
----
- The recipe now supports creating a FCGI script. Thanks to Jannis
Leidel for the patch.
- When downloading a Django recipe for the first time the recipe now
properly reports the url it is downloading from.
0.13
----
- Specifying a user name within a subversion url now works. The code
that determined the revision has been updated. This fixes issue
#274004. Thanks to Remco for the patch.
- Updated the template for creating new projects. It now uses the
current admin system when generating it's `urls.py` file. This fixes
issue #276255. Thanks to Roland for the patch.
0.12.1
------
- Re-upload since CHANGES.txt was missing from the release
0.12
----
- The recipe no longer executes subversion to determine whether the
versions is to be downloaded using subversion. This fixes issue
#271145. Thanks to Kapil Thangavelu for the patch.
- Changed the `pythonpath` option to `extra-paths`. This makes the
recipe more consistent with other recipes (see issue #270908).
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.