This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients alexis, cool-RR, eric.araujo, tarek, thomas.holmes
Date 2011-07-11.15:28:39
SpamBayes Score 0.000190371
Marked as misclassified No
Message-id <1310398120.1.0.897194110833.issue12449@psf.upfronthosting.co.za>
In-reply-to
Content
> Apparently -m packaging.run and pysetup3 run don't perform
> identically, but that isn't relevant for this bug.
That’s very surprising, given that they have the same one-line code.  Please file that bug.

> Regarding bdist, I got bdist_wininst to work but I had to modify the
> code in place, it did not work by default.
Can you report that too, if there is no existing bug?  (Maybe it’s #10945 or another one.)

> It also creates an exe installer, not an MSI.
Why would you think it creates an MSI?  bdist_wininst is not bdist_msi.

> bdist_msi is not set as a valid command to run inside the commands
> package __init__.py.
Is it a problem?  In distutils too, bdist_msi is not registered in command.__init__, as it can’t run on non-Windows, but the bdist command knows that it exists and can run it.  IOW, there are two registries of bdist commands: in command.__init__, which is used by --help-commands and others, and in bdist.  In distutils, calling bdist --formats=msi or directly bdist_msi works (on Windows); if it doesn’t work with packaging, this is another bug to report.
History
Date User Action Args
2011-07-11 15:28:40eric.araujosetrecipients: + eric.araujo, tarek, cool-RR, thomas.holmes, alexis
2011-07-11 15:28:40eric.araujosetmessageid: <1310398120.1.0.897194110833.issue12449@psf.upfronthosting.co.za>
2011-07-11 15:28:39eric.araujolinkissue12449 messages
2011-07-11 15:28:39eric.araujocreate