Changes by Senthil Kumaran sent...@uthcode.com:
--
nosy: -orsenthil
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10318
___
___
Python-bugs-list
Éric Araujo mer...@netwok.org added the comment:
Can I removed the shebangs in the 3.3 stdlib or do I need to go through with
the PEP 8 patch on python-dev first?
--
versions: -Python 2.7, Python 3.2
___
Python tracker rep...@bugs.python.org
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10318
___
Nick Coghlan ncogh...@gmail.com added the comment:
I created #13475 to discuss the idea of a command line option to override
sys.path[0] initialisation.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10318
Éric Araujo mer...@netwok.org added the comment:
Hmm, my initial reaction is that that specific wording is stronger than I had
in mind -
there's nothing really wrong with having a shebang line and execute bit set
on a top level
module and symlinking it from /usr/bin.
Okay. (On that
Nick Coghlan ncogh...@gmail.com added the comment:
Hmm, interesting mailing list post - I hadn't thought about how the
auto-initialisation of sys.path[0] aligns with the Windows vs Unix difference
in PATH handling (i.e. whether or not the current directory is considered to be
on PATH), with
Éric Araujo mer...@netwok.org added the comment:
Patch to PEP 8 attached.
--
Added file: http://bugs.python.org/file23755/pep8-shebangs.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10318
Nick Coghlan ncogh...@gmail.com added the comment:
Hmm, my initial reaction is that that specific wording is stronger than I had
in mind - there's nothing really wrong with having a shebang line and execute
bit set on a top level module and symlinking it from /usr/bin. The problem is
that
Éric Araujo mer...@netwok.org added the comment:
The patches I’ve discussed and committed were actually peripheral. The
original bug reported here is that shebangs shouldn’t use “/usr/bin/env python”
with an altinstall installation, as in that case you’re not creating a python
(or python3)
Jesús Cea Avión j...@jcea.es added the comment:
+1 to c.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10318
___
___
Python-bugs-list mailing
Nick Coghlan ncogh...@gmail.com added the comment:
+1 to 'c', but it should come with an update to PEP 8 to say don't do that.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10318
___
Ezio Melotti ezio.melo...@gmail.com added the comment:
Éric, what's the status of this?
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10318
___
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset 65d5ecefd50d by Éric Araujo in branch '3.2':
Fix missing or wrong shebangs and missing executable bits for scripts (#10318)
http://hg.python.org/cpython/rev/65d5ecefd50d
New changeset 5467abaaf5eb by Éric Araujo in
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset 7fb0abf928e0 by Éric Araujo in branch '2.7':
Fix missing or shebangs and executable bits for scripts (#10318)
http://hg.python.org/cpython/rev/7fb0abf928e0
--
___
Python
Éric Araujo mer...@netwok.org added the comment:
This 3.2 patch updates UNIX rights and shebangs in Tools/scripts.
I also edited mailerdaemon, which used a string exception.
--
versions: -Python 3.1
Added file: http://bugs.python.org/file22584/tools-scripts.diff
Éric Araujo mer...@netwok.org added the comment:
There are a lot of examples that use a bare “python”; changing all of
those would cause merging pains.
I’ve changed my mind. Given the python/python2/python3 drama with
distributions, I now think that we should use “python3” in the 3.x docs.
Éric Araujo mer...@netwok.org added the comment:
Attached patch fixes shebangs to use python3 in py3k.
There are a lot of examples that use a bare “python”; changing all of those
would cause merging pains.
--
___
Python tracker
Changes by Éric Araujo mer...@netwok.org:
--
keywords: +patch
Added file: http://bugs.python.org/file19850/env-python3.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10318
___
Alexander Belopolsky belopol...@users.sourceforge.net added the comment:
-#!/usr/bin/env python
+#!/usr/bin/env python3
# -*- coding: UTF-8 -*-
Not strictly related to this issue, but do we want to recommend
redundant encoding cookie in the docs?
--
Éric Araujo mer...@netwok.org added the comment:
Good call. +1 on removing them.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10318
___
___
Changes by Jesús Cea Avión j...@jcea.es:
--
nosy: +jcea
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10318
___
___
Python-bugs-list mailing list
Alexander Belopolsky belopol...@users.sourceforge.net added the comment:
I would like to add my +1 to Eric's msg120485 above. What I really find
puzzling is why some scripts in Tools/ have hashbangs, but don't have execute
permission.
Tools/scripts/cleanfuture.py
Tools/scripts/combinerefs.py
Changes by Senthil Kumaran orsent...@gmail.com:
--
nosy: +orsenthil
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10318
___
___
Python-bugs-list
Eric Smith e...@trueblade.com added the comment:
Is there any reason for the test files to have a shebang line at all? I think
those should be removed, which would cut the problem in half.
Also, given -m, I'm not sure any of the files in the stdlib should have a
shebang line. Is there really
R. David Murray rdmur...@bitdance.com added the comment:
Benjamin did some cleanup in this area in at least py3k, so he might have some
thoughts, making him nosy.
--
nosy: +benjamin.peterson, r.david.murray
___
Python tracker rep...@bugs.python.org
Nick Coghlan ncogh...@gmail.com added the comment:
Removing shebang lines from svn completely and only *adding* them during
installation steps as appropriate may be an interesting approach. (I noted that
my grep of my local build found only correct references to python3.2 in the
built scripts
Nick Coghlan ncogh...@gmail.com added the comment:
For the record, my list is from an svn checkout of r86191
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10318
___
Nick Coghlan ncogh...@gmail.com added the comment:
A few more deeper in the py3k source tree:
Doc/tools/docutils/_string_template_compat.py
Doc/tools/docutils/readers/python/pynodes.py
Doc/tools/sphinx/pycode/pgen2/token.py
Lib/lib2to3/tests/data/different_encoding.py
Adding Georg, since this
Changes by Nick Coghlan ncogh...@gmail.com:
--
assignee: d...@python -
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10318
___
___
Georg Brandl ge...@python.org added the comment:
You can ignore those under Doc/tools; they are neither part of the distribution
and nor installed.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10318
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +eric.araujo
versions: +Python 3.1
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10318
___
___
Ned Deily n...@acm.org added the comment:
I agree with Eric's comment about why have shebang lines at all for files in
the standard library. There isn't any use case or recommendation for ever
putting /path/to/lib/pythonx.x or its subdirectories directly on a shell search
path is there?
WRT
New submission from Allan McRae al...@archlinux.org:
The following files are incorrectly installed with a #!/usr/bin/env python
shebang when using make altinstall:
usr/lib/python2.7/base64.py
usr/lib/python2.7/bsddb/dbshelve.py
usr/lib/python2.7/bsddb/test/test_dbtables.py
33 matches
Mail list logo
