[issue14651] pysetup run cmd can't handle option values in the setup.cfg

2014-03-13 Thread Éric Araujo
Changes by Éric Araujo mer...@netwok.org: -- resolution: - out of date stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14651 ___

[issue14651] pysetup run cmd can't handle option values in the setup.cfg

2012-05-21 Thread Éric Araujo
Éric Araujo mer...@netwok.org added the comment: I have fixed the other bug in distutils2 (to be ported soon to packaging in 3.3). I wrote a test for this bug but the fix was not enough. Need to investigate more. -- ___ Python tracker

[issue14651] pysetup run cmd can't handle option values in the setup.cfg

2012-05-09 Thread Éric Araujo
Changes by Éric Araujo mer...@netwok.org: -- dependencies: +Custom commands don't work ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14651 ___ ___

[issue14651] `pysetup run [cmd]` can't handle option values in the setup.cfg

2012-04-23 Thread Takayuki SHIMIZUKAWA
New submission from Takayuki SHIMIZUKAWA shimizuk...@gmail.com: `pysetup run [cmd]` can't handle option values in the setup.cfg setup.cfg:: [sdist] formats = gztar dist-dir = _dist run on windows:: C: pysetup run sdist That command generate `dist/package-version.zip` instead of

[issue14651] pysetup run cmd can't handle option values in the setup.cfg

2012-04-23 Thread Éric Araujo
É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