-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tag formatter documentation #212
Comments
Bah. Does that mean that, if we use |
Nop. It works as expected when you use |
Yes please :-) |
From https://bugs.python.org/issue20754 it looks like it may help if we initialize |
This seems to work correctly with Python 3, but fails with for Python 2.7.13 https://travis-ci.org/ludia/pyramid_metrics/jobs/256667732 $ python setup.py --version
Traceback (most recent call last):
File "setup.py", line 43, in <module>
'de = devup.app:cli',
File "/Users/piorbastida/.pyenv/versions/2.7.13/lib/python2.7/distutils/core.py", line 124, in setup
dist.parse_config_files()
File "/Users/piorbastida/.pyenv/versions/2.7.13/lib/python2.7/distutils/dist.py", line 397, in parse_config_files
val = parser.get(section,opt)
File "/Users/piorbastida/.pyenv/versions/2.7.13/lib/python2.7/ConfigParser.py", line 623, in get
return self._interpolate(section, option, value, d)
File "/Users/piorbastida/.pyenv/versions/2.7.13/lib/python2.7/ConfigParser.py", line 669, in _interpolate
option, section, rawval, e.args[0])
ConfigParser.InterpolationMissingOptionError: Bad value substitution:
section: [zest.releaser]
option : tag-format
key : version
rawval : v%%(version)s |
Fix in setuptools: pypa/setuptools#889 In Py3, setuptools read the config itself, while this doesn't seem to be the case in Py2... |
Same here, no matter if I use one or two % signs.
|
This reverts commit bb1de00. See zestsoftware/zest.releaser#212 for details: the setup.cfg file is interpolated by distutils, and this fails.
Not sure if this is common knowledge or not but apparently config parser uses interpolation (issue28935 and issue20754) in python3.
That means the
%
signs are causing the loading to crash.It can be fixed by using
%%
instead but it did not occur to me when writing the documentation.Do you thing this should be highlighted ?
The text was updated successfully, but these errors were encountered: