New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
platform.architecture() fails if python is lanched via its symbolic link (cygwin) #48012
Comments
I created symbolic link to python.exe as dummy.exe on cygwin. $ ./dummy
Python 2.6b3+ (trunk:66166M, Sep 3 2008, 06:43:59)
[GCC 3.4.4 (cygming special, gdc 0.12, using dmd 0.125)] on cygwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import platform
>>> platform._follow_symlinks("dummy.exe")
'/home/WhiteRabbit/python-dev/trunk/dummy.exe/python.exe'
>>> Is this _follow_symlinks's intended behavior? If no, I hope attached |
|
This sliped out of my mind. :-( [bpo-3719]
os.path.realpath is new feature in Python2.2, so probably this cannot be |
The problem shows up on other platforms as well. $ /usr/bin/python -c "import platform; print platform.architecture()"
('64bit', '')
$ /usr/bin/python2.4 -c "import platform; print platform.architecture()"
('64bit', 'ELF') And the patch corrects this. |
Thanks, fixed in r66213(trunk), r66214(release-maint25), r66216(py3k). |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: