OLD | NEW |
| (Empty) |
1 == 18 January 2012 == | |
2 | |
3 [Prependum:] I just realized I should have named the new version 2.0, | |
4 to reflect the new ownership and status as a community run project. | |
5 Not too late, I guess. I've just released python-gflags 2.0, which is | |
6 identical to python-gflags 1.8 except for the version number. | |
7 | |
8 I've just released python-gflags 1.8. This fixes a bug, allowing | |
9 modules defining flags to be re-imported without raising duplicate | |
10 flag errors. | |
11 | |
12 Administrative note: In the coming weeks, I'll be stepping down as | |
13 maintainer for the python-gflags project, and as part of that Google | |
14 is relinquishing ownership of the project; it will now be entirely | |
15 community run. The remaining | |
16 [http://python-gflags.googlecode.com/svn/tags/python-gflags-1.8/ChangeLog change
s] | |
17 in this release reflect that shift. | |
18 | |
19 | |
20 === 20 December 2011 === | |
21 | |
22 I've just released python-gflags 1.7. The major change here is | |
23 improved unicode support, in both flag default values and | |
24 help-strings. We've also made big steps toward making gflags work | |
25 with python 3.x (while keeping 2.4 compatibility), and improving | |
26 --help output in the common case where output is a tty. | |
27 | |
28 For a full list of changes since last release, see the | |
29 [http://python-gflags.googlecode.com/svn/tags/python-gflags-1.7/ChangeLog Change
Log]. | |
30 | |
31 === 29 July 2011 === | |
32 | |
33 I've just released python-gflags 1.6. This release has only minor | |
34 changes, including support for multi_float flags. The full list of | |
35 changes is in the | |
36 [http://python-gflags.googlecode.com/svn/tags/python-gflags-1.6/ChangeLog Change
Log]. | |
37 | |
38 The major change with this release is procedural: I've changed the | |
39 internal tools used to integrate Google-supplied patches for gflags | |
40 into the opensource release. These new tools should result in more | |
41 frequent updates with better change descriptions. They will also | |
42 result in future `ChangeLog` entries being much more verbose (for | |
43 better or for worse). | |
44 | |
45 === 26 January 2011 === | |
46 | |
47 I've just released python-gflags 1.5.1. I had improperly packaged | |
48 python-gflags 1.5, so it probably doesn't work. All users who have | |
49 updated to python-gflags 1.5 are encouraged to update again to 1.5.1. | |
50 | |
51 === 24 January 2011 === | |
52 | |
53 I've just released python-gflags 1.5. This release adds support for | |
54 flag verifiers: small functions you can associate with flags, that are | |
55 called whenever the flag value is set or modified, and can verify that | |
56 the new value is legal. It also has other, minor changes, described | |
57 in the | |
58 [http://python-gflags.googlecode.com/svn/tags/python-gflags-1.5/ChangeLog Change
Log]. | |
59 | |
60 === 11 October 2010 === | |
61 | |
62 I've just released python-gflags 1.4. This release has only minor | |
63 changes from 1.3, including support for printing flags of a specific | |
64 module, allowing key-flags to work with special flags, somewhat better | |
65 error messaging, and | |
66 [http://python-gflags.googlecode.com/svn/tags/python-gflags-1.4/ChangeLog so for
th]. | |
67 If 1.3 is working well for you, there's no particular reason to upgrade. | |
68 | |
69 === 4 January 2010 === | |
70 | |
71 I just released python-gflags 1.3. This is the first python-gflags | |
72 release; it is version 1.3 because this code is forked from the 1.3 | |
73 release of google-gflags. | |
74 | |
75 I don't have a tarball or .deb file up quite yet, so for now you will | |
76 have to get the source files by browsing under the 'source' | |
77 tag. Downloadable files will be available soon. | |
78 | |
OLD | NEW |