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 a.badger
Recipients a.badger, vstinner
Date 2008-10-15.02:00:23
SpamBayes Score 2.3031954e-10
Marked as misclassified No
Message-id <1224036025.1.0.407986827426.issue4126@psf.upfronthosting.co.za>
In-reply-to
Content
Yep :-)  I am against throwing away valid data just because we can't
interpret it automatically.  Environment variables in Unix hold bytes. 
Those bytes are usually ASCii characters, however, they do not have to
be.  This is a case of being on the border between python and the
outside world so we need to be able to pass in bytes if the user
requests it.

Let's say that you have a local directory of: /home/\xff/username/bin in
your PATH environment variable and a command named my_app.sh in there. 
At the shell you can happily run myapp.sh and it will do it's thing. 
Now you open your python shell and do:
    subprocess.call(['myapp.sh'])

and it doesn't work.  This is non-intuitive behaviour for people who are
used to how the shell works.  All this patch will do is take away the
work around of subprocess.call(['bash', 'myapp.sh'])

"""
I tested Python 2.5: b is also removed, but Python 2.6 keeps the 
variable b.
"""
I just tested python-2.5.1 and b is kept, not removed.
History
Date User Action Args
2008-10-15 02:00:25a.badgersetrecipients: + a.badger, vstinner
2008-10-15 02:00:25a.badgersetmessageid: <1224036025.1.0.407986827426.issue4126@psf.upfronthosting.co.za>
2008-10-15 02:00:24a.badgerlinkissue4126 messages
2008-10-15 02:00:23a.badgercreate