Éric Araujo <mer...@netwok.org> added the comment: Thanks for the report. This is weird, given that the code for setting command options in setup.cfg directly comes from distutils and works there. I think that this error may come from another bug in pysetup (i.e. in distutils2.run) where the config file is parsed too late; I discovered that bug a week ago and did not find the time to apply the fix. I’ll keep you updated on this.
---------- title: `pysetup run [cmd]` can't handle option values in the setup.cfg -> pysetup run cmd can't handle option values in the setup.cfg versions: +3rd party, Python 3.3 -Python 2.6, Python 2.7 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14651> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
