[issue2385] run_setup can fail if the setup script uses __file__

Changes by Tarek Ziadé : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue2385] run_setup can fail if the setup script uses __file__

Fred L. Drake, Jr. <[EMAIL PROTECTED]> added the comment: It's also arguable that not providing __file__ was a bug, in which case that should be backported to Python 2.5.x. __ Tracker <[EMAIL PROTECTED]> _

[issue2385] run_setup can fail if the setup script uses __file__

Changes by Fred L. Drake, Jr. <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file9936/run_script-restores-cwd.patch __ Tracker <[EMAIL PROTECTED]> __ ___

[issue2385] run_setup can fail if the setup script uses __file__

Fred L. Drake, Jr. <[EMAIL PROTECTED]> added the comment: Updated patch to add restoring the current directory after running the setup.py script in run_script. Added file: http://bugs.python.org/file9937/run_script-restores-cwd.patch __ Tracker <[EMAIL PROTECTED]

[issue2385] run_setup can fail if the setup script uses __file__

Tarek Ziadé <[EMAIL PROTECTED]> added the comment: right, I misused os.curdir, I wanted the current working directory. (getcwd()) Thanks for correcting it and making it a separate patch __ Tracker <[EMAIL PROTECTED]> ___

[issue2385] run_setup can fail if the setup script uses __file__

Fred L. Drake, Jr. <[EMAIL PROTECTED]> added the comment: Of course, my previous commit did what I said it should not in #1 above: it changed the current directory to the directory in which the setup.py script lived (which made __file__ wrong). Fixed in revision 62147, including test that checks

[issue2385] run_setup can fail if the setup script uses __file__

Fred L. Drake, Jr. <[EMAIL PROTECTED]> added the comment: Here's a patch that restores the current directory after running the script. The distutils-sig should probably determine if that's the right thing to do. Includes test. Added file: http://bugs.python.org/file9936/run_script-restores-cwd

[issue2385] run_setup can fail if the setup script uses __file__

Fred L. Drake, Jr. <[EMAIL PROTECTED]> added the comment: I don't think these are the right thing to do. 1. Your run_setup() changes add a os.chdir(), but then uses the path to the script as passed in; this assumes that the provided path is absolute, which is not a good assumption. That i

[issue2385] run_setup can fail if the setup script uses __file__

Changes by Tarek Ziadé <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file9724/distutils.core.patch __ Tracker <[EMAIL PROTECTED]> __ ___ Pyt

[issue2385] run_setup can fail if the setup script uses __file__

Tarek Ziadé <[EMAIL PROTECTED]> added the comment: new patch that adds __main__ and __file__, and make a chdir, so the function is called in a realistic way. this patch also adds test_core.py for this change. Added file: http://bugs.python.org/file9811/2008-03-28-distutils.core.patch _

[issue2385] run_setup can fail if the setup script uses __file__

New submission from Tarek Ziadé <[EMAIL PROTECTED]>: When calling run_setup, the execfile does not set the __file__ global variable, that is often used in setup.py modules (for instance to load a text file from the package to be used in the long_description) This patch adds this global variable