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

Changes by Éric Araujo : -- resolution: -> out of date stage: -> committed/rejected status: open -> closed ___ Python tracker ___ __

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

Éric Araujo 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

Changes by Éric Araujo : -- dependencies: +Custom commands don't work ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

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

Éric Araujo 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 par

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

New submission from Takayuki SHIMIZUKAWA : `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 `_dist/packcage-version.