Modifying the system path isn't ideal, but I think it's all we have short writing our own library loader ( extending ctypes.LibraryLoader?).
On Mon, Dec 10, 2012 at 7:54 AM, Howard Butler <hobu....@gmail.com> wrote: > > On Dec 8, 2012, at 11:29 AM, Sean Gillies <sean.gill...@gmail.com> wrote: > >> Can anybody take a look at this change to setup.py? >> >> https://github.com/sgillies/shapely/commit/755f0673de10ca1faa29b1b751d38b1dd8c9378b >> https://github.com/Toblerity/Shapely/issues/37 > > Shapely putting its .pyd files in the DLLs directory was started because > Python didn't have any other directories that had been put on the PATH, and > it was bad form to mangle the PATH directly yourself upon import. Is it ok to > mangle the PATH on import to point to your .pyd in an egg now? > > Rtree does the same, and should probably be fixed up accordingly as well. > > Howard > > _______________________________________________ > Community mailing list > Community@lists.gispython.org > http://lists.gispython.org/mailman/listinfo/community -- Sean Gillies _______________________________________________ Community mailing list Community@lists.gispython.org http://lists.gispython.org/mailman/listinfo/community
