forked from camptocamp/z3c.recipe.filetemplate
-
Notifications
You must be signed in to change notification settings - Fork 0
/
CHANGES.txt
146 lines (106 loc) · 4.12 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
=======
Changes
=======
2.1.1 (Unreleased)
==================
--------
Features
--------
-----
Fixes
-----
- Added undeclared but necessary test dependency on `zope.testing` in a
test extra.
- Added test dependency on `z3c.recipe.scripts` as it is required by newer
`zc.buildout` versions.
- Using python's `doctest` module instead of deprecated
`zope.testing.doctest`.
2.1.0 (2010-04-21)
==================
--------
Features
--------
- Enable cross-platform paths by allowing an extended syntax for path
suffixes. Example: If ``${buildout:directory}`` resolves to
``/sample_buildout`` on a POSIX system and ``C:\sample_buildout`` in
Windows, ``${buildout:directory/foo.txt}`` will resolve to
``/sample_buildout/foo.txt`` and ``C:\sample_buildout\foo.txt``,
respectively.
- Add filters via a pipe syntax, reminiscent of UNIX pipes or Django template
filters. Simple example: if ``${name}`` resolves to ``harry`` then
``${name|upper}`` resolves to ``HARRY``. Simple string filters are
upper, lower, title, and capitalize, just like the Python string
methods. Also see the next bullet.
- Added support for the buildout relative-paths option. Shell scripts should
include ``${shell-relative-path-setup}`` before commands with
buildout-generated paths are executed. Python scripts should use
``${python-relative-path-setup}`` similarly. ``${os-paths}`` (shell),
``${space-paths}`` (shell), and ``${string-paths}`` (Python) will have
relative paths if the buildout relative-paths option is used. To convert
individual absolute paths to relative paths, use the ``path-repr`` filter
in Python scripts and the ``shell-path`` filter in shell scripts. Path
suffixes can be combined with these filters, so, if buildout's
relative-paths option is true, ``${buildout:directory/foo.txt|path-repr}``
will produce a buildout-relative, platform appropriate path to
foo.txt. Note that for shell scripts, Windows is not supported at
this time.
- Support escaping ``${...}`` with ``$${...}`` in templates. This is
particularly useful for UNIX shell scripts.
-----
Fixes
-----
- Make tests less susceptible to timing errors.
-------
Changes
-------
- ``${os-paths}`` and ``${space-paths}`` no longer filter out .zip paths.
- The entries in ``${string-paths}`` now are separated by newlines. Each
entry is indented to the level of the initial placement of the marker.
2.0.3 (2009-07-02)
==================
-----
Fixes
-----
- Use ``realpath`` helper function from zc.buildout on the buildout
directory too, such that it goes through the same normalization as
the path being compared and stands a chance of working on Windows,
due to possible drive letter case differences.
2.0.2 (2009-05-04)
==================
-----
Fixes
-----
- Turns out sorting paths was a bad idea. They are already in a deterministic
order, AFAICT, because of the order or processing dependencies. Sorting
them makes them *less* deterministic in practice, across machines.
2.0.1 (2009-04-30)
==================
-----
Fixes
-----
- Correct sdist generation to include all necessary files.
- Doc formatting fixes.
- Correct "Destinations already exist" message to list destinations without
``.in`` suffix.
2.0 (2009-04-30)
================
--------
Features
--------
- Store your template files in a separate directory structure, using the
``source-directory`` option.
- Specify multiple files automatically with globs.
- Templates can reference other buildout sections using the usual syntax, e.g.
${buildout:parts}
- Share options with other sections using the typical ``extends`` option.
- Create destination directories automatically.
- Define option values for templates dynamically in Python with the
``interpreted-options`` option.
- Get paths for eggs by specifying ``eggs`` and ``extra-paths``, just like
zc.recipe.egg script recipe. These are available in template options in
colon-delimited, space-delimited, and quoted variants. You can also build
your own using the ``interpreted-options`` feature.
- Templates are not processed if there are no changes to them or the buildout.
1.0 (2007-09-30)
================
Initial release.