I believe so as well. It's more of a distutils issue than a setuptools issue - since there are no extension modules, it doesn't realize that the egg needs to be platform specific. The -p option is used to specify the platform name but it seems to only take effect if the distribution is non-pure. And I'm not sure if there's a way to trick it into believing it's non-pure.
Might as well just rename them by hand, I guess. Since you have the 64-bit DLLs, could you provide 64-bit eggs as well? Looks like you've just got one architecture there, and without the suffix it's not obvious which. On Tue, Nov 9, 2010 at 2:33 PM, Jaakko Salli <[email protected]> wrote: > On 9.11.2010 20:57, Sean Gillies wrote: >> Jaakko, will these need to be 'py2.x-win32.egg' files so that *nix >> users don't get them by mistake? >> > > As Ken mentioned, yes, most likely. I really do not know much > about setuptools, easy install or eggs. Those files are just raw > output of setup.py bdist_egg. > > Jaakko > _______________________________________________ > Community mailing list > [email protected] > http://lists.gispython.org/mailman/listinfo/community > _______________________________________________ Community mailing list [email protected] http://lists.gispython.org/mailman/listinfo/community
