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 bethard
Recipients bethard, tarek
Date 2009-02-19.04:16:04
SpamBayes Score 1.54808e-09
Marked as misclassified No
Message-id <1235016969.03.0.818386696301.issue5311@psf.upfronthosting.co.za>
In-reply-to
Content
I just ran "setup.py bdist_msi" with NLTK which is a pure Python
package. You can see the setup.py here:
http://code.google.com/p/nltk/source/browse/trunk/nltk/setup.py. Despite
the fact that NLTK is pure Python, the generated .msi's look like
nltk-0.9.8.win32-py2.5.msi and nltk-0.9.8.win32-py2.6.msi (built with
Python 2.5 and 2.6 respectively).

So, two questions: (1) are the version numbers supposed to be there? and
(2) if so, does that mean a .msi for a pure Python package built by
Python 2.6 won't work on any other version?
History
Date User Action Args
2009-02-19 04:16:09bethardsetrecipients: + bethard, tarek
2009-02-19 04:16:09bethardsetmessageid: <1235016969.03.0.818386696301.issue5311@psf.upfronthosting.co.za>
2009-02-19 04:16:05bethardlinkissue5311 messages
2009-02-19 04:16:05bethardcreate