➜

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 jdemeyer
Recipients brett.cannon, eric.snow, erik.bray, jdemeyer, ncoghlan, paul.moore, petr.viktorin, sth
Date 2018-08-04.17:39:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1533404389.7.0.56676864532.issue32797@psf.upfronthosting.co.za>
In-reply-to
Content 
> Then instead of adding the source directory to sys.path

What's wrong with that? Installing the .pyx sources together with the .so compiled modules makes a lot of sense to me: it is very analogous to installing the .py sources together with the .pyc byte-compiled files. In https://bugs.python.org/issue32797#msg315965 Paul Moore disagreed with that analogy, but I don't quite understand why.

And if ${prefix}/lib/pythonX.Y/site-packages/PKGNAME is not a good place to store the installed sources, where would you want to install them otherwise?

> (which was only working because the legacy import system never implemented PEP 302 properly)

Not sure what you mean here...
History
Date User Action Args
2018-08-04 17:39:49jdemeyersetrecipients: + jdemeyer, brett.cannon, paul.moore, ncoghlan, petr.viktorin, erik.bray, eric.snow, sth
2018-08-04 17:39:49jdemeyersetmessageid: <1533404389.7.0.56676864532.issue32797@psf.upfronthosting.co.za>
2018-08-04 17:39:49jdemeyerlinkissue32797 messages
2018-08-04 17:39:49jdemeyercreate