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 andybuckley
Recipients andybuckley, doko, nas, nascheme, rpetrov
Date 2009-02-16.16:19:36
SpamBayes Score 4.21053e-07
Marked as misclassified No
Message-id <1234801246.39.0.0878978539545.issue4151@psf.upfronthosting.co.za>
In-reply-to
Content
I'm having trouble with this as well :(  It's pretty much a blocker for
integrating distutils-based extension builds with an autotools library
build, because the "make distcheck" target explicitly does the build in
a subtree of the source directory, and write-protects the srcdir during
the build.

Effectively the source is referred to in my setup.py as living in
"../../pyext", which translates into distutils attempting to build the
extension in "build/temp.linux-i686-2.5/../../pyext/", which is the
write-protected source dir. This would work okay if the directory path
to the source file were ignored when constructing the output path: would
the proposed patch(es) fix this?
History
Date User Action Args
2009-02-16 16:20:46andybuckleysetrecipients: + andybuckley, nascheme, doko, nas, rpetrov
2009-02-16 16:20:46andybuckleysetmessageid: <1234801246.39.0.0878978539545.issue4151@psf.upfronthosting.co.za>
2009-02-16 16:19:37andybuckleylinkissue4151 messages
2009-02-16 16:19:36andybuckleycreate