[Martin v. Löwis, 2011-03-02]
I think a PEP would help, but in this case I would request that before
the PEP gets written (it can be a really short one!) somebody actually
go out and get consensus from a number of important distros. Besides
Barry, do we have any representatives of distros
-On [20110302 01:17], Martin v. Löwis (mar...@v.loewis.de) wrote:
Matthias Klose represents Debian, Dave Malcolm represents Redhat,
and Dirkjan Ochtman represents Gentoo.
With FreeBSD's ports if you install a Python port it will install a
pythonX.Y in /usr/local/bin, depending on what
On Mon, 28 Feb 2011 23:03:50 +0100
brett.cannon python-check...@python.org wrote:
+
+if sys.platform == 'win32':
+print(See the devguide's Getting Set Up guide for building under
Windows)
Actually, you can also build from the command line under Windows:
using Tools/buildbot/build.bat or
On 01/03/2011 21:19, Kerrick Staley wrote:
Hello,
There is a need for the default Python2 install to place a symlink at
/usr/bin/python2 that points to /usr/bin/python, or for the
documentation to recommend that packagers ensure that python2 is
defined. Also, all documentation should be
On Tue, 1 Mar 2011 20:43:27 -0800
Guido van Rossum gu...@python.org wrote:
But I wouldn't be surprised if some people had regrets about the way
the community works (I can recall at least one such case) and it would
be useful to learn from those occasions, if they'll let us. And the
numbers
Hello,
On Tue, 01 Mar 2011 19:25:00 -0800
Westley Martínez aniko...@gmail.com wrote:
If I got a message like that in my mailbox I would be rather annoyed,
mark it as spam, and be less likely to contribute again.
Yes, I think that's a risk. Do you think of a wording that could
alleviate such
SVN is very bad instrument to contribute or follow an issue patches.
And, of course, very long lifecycle of the most issues greatly reduces
enthusisasm.
On Wed, Mar 2, 2011 at 2:08 PM, Antoine Pitrou solip...@pitrou.net wrote:
Hello,
On Tue, 01 Mar 2011 19:25:00 -0800
Westley Martínez
On Wed, 2 Mar 2011 14:29:18 +0200
Andrew Svetlov andrew.svet...@gmail.com wrote:
SVN is very bad instrument to contribute or follow an issue patches.
Will Mercurial make things more attractive?
And, of course, very long lifecycle of the most issues greatly reduces
enthusisasm.
True. I
On Wed, Mar 2, 2011 at 10:01, Piotr Ożarowski pi...@debian.org wrote:
I co-maintain with Matthias a package that provides /usr/bin/python
symlink in Debian and I can confirm that it will always point to Python
2.X. We also do not plan to add /usr/bin/python2 symlink (and I guess
only accepted
On Wed, Mar 2, 2011 at 2:39 PM, Antoine Pitrou solip...@pitrou.net wrote:
Will Mercurial make things more attractive?
Definitely yes! I welcome upcoming migration.
And, of course, very long lifecycle of the most issues greatly reduces
enthusisasm.
True. I believe we are improving that, but
[Sandro Tosi, 2011-03-02]
On Wed, Mar 2, 2011 at 10:01, Piotr Ożarowski pi...@debian.org wrote:
I co-maintain with Matthias a package that provides /usr/bin/python
symlink in Debian and I can confirm that it will always point to Python
2.X. We also do not plan to add /usr/bin/python2
On 2 March 2011 12:07, Antoine Pitrou solip...@pitrou.net wrote:
But I wonder if there are other social or technical factors, such as
the community being too intimidating or not welcoming enough.
Actually, if some python-dev readers have something to say about that,
they are welcome :)
From
The following is going to sound bitter...
I was fired with enthusiasm for working on Python after the sprints at
EuroPython last year. I submitted 3 (I think) patches for pulldom - a test
suite (it has 0% code coverage at present), documentation for the module
(there isn't any at present), and a
On Wed, Mar 2, 2011 at 13:56, Piotr Ożarowski pi...@debian.org wrote:
[Sandro Tosi, 2011-03-02]
On Wed, Mar 2, 2011 at 10:01, Piotr Ożarowski pi...@debian.org wrote:
I co-maintain with Matthias a package that provides /usr/bin/python
symlink in Debian and I can confirm that it will always
On Wed, Mar 2, 2011 at 6:54 AM, Antoine Pitrou solip...@pitrou.net wrote:
A remark: Having all clones created under a dedicated namespace (say
sandbox) could make the hg.python.org listing clearer, since all user
clones would be grouped.
Sure, we can change the enforced convention depending
[Sandro Tosi, 2011-03-02]
On Wed, Mar 2, 2011 at 13:56, Piotr Ożarowski pi...@debian.org wrote:
[Sandro Tosi, 2011-03-02]
On Wed, Mar 2, 2011 at 10:01, Piotr Ożarowski pi...@debian.org wrote:
I co-maintain with Matthias a package that provides /usr/bin/python
symlink in Debian and I can
On Mar 2, 2011, at 8:23 AM, Sandro Tosi wrote:
On Wed, Mar 2, 2011 at 13:56, Piotr Ożarowski pi...@debian.org wrote:
[Sandro Tosi, 2011-03-02]
On Wed, Mar 2, 2011 at 10:01, Piotr Ożarowski pi...@debian.org wrote:
I co-maintain with Matthias a package that provides /usr/bin/python
symlink in
Hello,
Defensive programming will force you to do things like :
import sys
if sys.version[0] == '2':
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
On 03/03/11 00:03, Piotr Ożarowski wrote:
[Sandro Tosi, 2011-03-02]
On Wed, Mar 2, 2011 at 13:56, Piotr Ożarowskipi...@debian.org wrote:
[Sandro Tosi, 2011-03-02]
On Wed, Mar 2, 2011 at 10:01, Piotr Ożarowskipi...@debian.org wrote:
I co-maintain with Matthias a package that provides
On 02/03/2011 14:04, James Y Knight wrote:
On Mar 2, 2011, at 8:23 AM, Sandro Tosi wrote:
On Wed, Mar 2, 2011 at 13:56, Piotr Ożarowskipi...@debian.org wrote:
[Sandro Tosi, 2011-03-02]
On Wed, Mar 2, 2011 at 10:01, Piotr Ożarowskipi...@debian.org wrote:
I co-maintain with Matthias a
[Allan McRae, 2011-03-02]
But is that not the whole point of adding the /usr/bin/python2 symlink.
That way a developer can explicitly use a /usr/bin/python2 or
/usr/bin/python3 shebang and have it portable everywhere. At the moment,
Debian seems to be the major hold-up on that actually
On 03/03/11 00:29, Piotr Ożarowski wrote:
[Allan McRae, 2011-03-02]
But is that not the whole point of adding the /usr/bin/python2 symlink.
That way a developer can explicitly use a /usr/bin/python2 or
/usr/bin/python3 shebang and have it portable everywhere. At the moment,
Debian seems to be
On Wed, 2011-03-02 at 13:08 +0100, Antoine Pitrou wrote:
Hello,
On Tue, 01 Mar 2011 19:25:00 -0800
Westley Martínez aniko...@gmail.com wrote:
If I got a message like that in my mailbox I would be rather annoyed,
mark it as spam, and be less likely to contribute again.
Yes, I think
On Wed, Mar 2, 2011 at 7:07 AM, Antoine Pitrou solip...@pitrou.net wrote:
On Tue, 1 Mar 2011 20:43:27 -0800
Guido van Rossum gu...@python.org wrote:
But I wouldn't be surprised if some people had regrets about the way
the community works (I can recall at least one such case) and it would
be
On Wed, Mar 2, 2011 at 10:00 AM, Jesse Noller jnol...@gmail.com wrote:
On Wed, Mar 2, 2011 at 7:07 AM, Antoine Pitrou solip...@pitrou.net wrote:
On Tue, 1 Mar 2011 20:43:27 -0800
Guido van Rossum gu...@python.org wrote:
But I wouldn't be surprised if some people had regrets about the way
the
On Mar 2, 2011, at 9:54 AM, Allan McRae wrote:
That way in ?? years when python-3.x is the python and python-2.x is
obsolete, and it is decided that /usr/bin/python will be python-3.x (which I
believe is the only logical outcome),
But that's not the only logical outcome. A perfectly logical
[Allan McRae, 2011-03-02]
Having made the packages using python-2.x code from an entire
distribution point at /usr/bin/python2, I have a fair idea of how much
work is involved...
* is every Arch package that uses Python 2.X already working with
/usr/bin/python and why not? ;-)
* how many
It seems that there are two kinds of developers (ok, it's over-generalized)
:
1- the ones that have a problem with python and file bugs into the issue
trackers : they don't try to search for solutions, they want core-developers
to check and correct their bugs. The motivation for these developers
On Wed, Mar 2, 2011 at 11:10 PM, Mark Smith
mark.sm...@practicalpoetry.co.uk wrote:
The following is going to sound bitter...
I was fired with enthusiasm for working on Python after the sprints at
EuroPython last year. I submitted 3 (I think) patches for pulldom - a test
suite (it has 0% code
On Thu, Mar 3, 2011 at 1:46 AM, Nick Coghlan ncogh...@gmail.com wrote:
I know there's a patch that has been sitting on the tracker for ages
that gave the mimetools module some love
s/mimetools/mimetypes/
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
/tangent
Does this discussion remind anyone else of the bash/dash switch for
/usr/bin/sh in Ubuntu?
The distro itself coped fine, but 3rd party shell scripts that used
bash extensions were a whole different story.
(No, I'm not sure what lessons, if any, we can draw from that. It just
struck me
On Wed, 02 Mar 2011 13:10:04 +, Mark Smith
mark.sm...@practicalpoetry.co.uk wrote:
The following is going to sound bitter...
I was fired with enthusiasm for working on Python after the sprints at
EuroPython last year. I submitted 3 (I think) patches for pulldom - a test
suite (it has 0%
On Wed, 02 Mar 2011 10:13:59 -0500, James Y Knight f...@fuhm.net wrote:
On Mar 2, 2011, at 9:54 AM, Allan McRae wrote:
That way in ?? years when python-3.x is the python and python-2.x
is obsolete, and it is decided that /usr/bin/python will be
python-3.x (which I believe is the only
On Mar 02, 2011, at 03:29 PM, Piotr Ożarowski wrote:
[Allan McRae, 2011-03-02]
But is that not the whole point of adding the /usr/bin/python2 symlink.
That way a developer can explicitly use a /usr/bin/python2 or
/usr/bin/python3 shebang and have it portable everywhere. At the moment,
On Wed, Mar 2, 2011 at 4:56 AM, Piotr Ożarowski pi...@debian.org wrote:
[Sandro Tosi, 2011-03-02]
On Wed, Mar 2, 2011 at 10:01, Piotr Ożarowski pi...@debian.org wrote:
I co-maintain with Matthias a package that provides /usr/bin/python
symlink in Debian and I can confirm that it will always
Jérôme Radix wrote:
Hello,
Defensive programming will force you to do things like :
import sys
if sys.version[0] == '2':
Really? Do you already do this?
if sys.version '2.2':
result = apply(func, arguments)
else:
result = func(*arguments)
And if so, have you tested it in Python
On Mar 2, 2011, at 12:14 PM, Barry Warsaw wrote:
I don't have a problem with adding such a symlink, and I think it should be
done by Informational PEP, not Standards Track PEP. Since there will be no
Python 2.8, our own build system shouldn't ever be changed to add such a link,
but we can
On Mar 2, 2011, at 11:42 AM, R. David Murray wrote:
Well, I personally won't use a distribution that makes this choice.
For whatever that's worth :)
This ***shouldn't*** be a choice distros have to make. There should be a
standard upstream recommended way to install python, and that's also
James Y Knight wrote:
I suspect he's saying it'd be better if the time didn't come (if so,
I'd agree). Python3 *is* unfortunately a new and incompatible
programming language, it makes sense for it to have it have its own
interpreter name.
Oh come on, there's like three incompatibilities
On Mar 02, 2011, at 02:49 PM, James Y Knight wrote:
On Mar 2, 2011, at 12:14 PM, Barry Warsaw wrote:
I don't have a problem with adding such a symlink, and I think it should be
done by Informational PEP, not Standards Track PEP. Since there will be no
Python 2.8, our own build system
Steven D'Aprano wrote:
Jérôme Radix wrote:
Hello,
Defensive programming will force you to do things like :
import sys
if sys.version[0] == '2':
Really? Do you already do this?
if sys.version '2.2':
result = apply(func, arguments)
else:
result = func(*arguments)
And if so, have
Am 02.03.2011 20:49, schrieb James Y Knight:
On Mar 2, 2011, at 12:14 PM, Barry Warsaw wrote:
I don't have a problem with adding such a symlink, and I think it
should be done by Informational PEP, not Standards Track PEP.
Since there will be no Python 2.8, our own build system shouldn't
ever
On Mar 2, 2011, at 5:04 PM, Martin v. Löwis wrote:
Am 02.03.2011 20:49, schrieb James Y Knight:
On Mar 2, 2011, at 12:14 PM, Barry Warsaw wrote:
I don't have a problem with adding such a symlink, and I think it
should be done by Informational PEP, not Standards Track PEP.
Since there will
No, I don't do it now. But taking like granted the fact that 2.x python will
be dead in 5 years and that /usr/bin/python will point to python3 is, imho,
a little too optimistic. Thus, as time passes, python scripts will have to
guess if they are running through python3 or python2 because the two
Am 02.03.2011 23:36, schrieb Jérôme Radix:
No, I don't do it now. But taking like granted the fact that 2.x python
will be dead in 5 years and that /usr/bin/python will point to python3
is, imho, a little too optimistic.
I don't think Steven said, or assumed, a scope of 5 years - more like
a
On Wed, 2011-03-02 at 16:20 +0100, Piotr Ożarowski wrote:
[Allan McRae, 2011-03-02]
Having made the packages using python-2.x code from an entire
distribution point at /usr/bin/python2, I have a fair idea of how much
work is involved...
* is every Arch package that uses Python 2.X
On Wed, Mar 2, 2011 at 3:00 PM, Martin v. Löwis mar...@v.loewis.de wrote:
Am 02.03.2011 23:36, schrieb Jérôme Radix:
No, I don't do it now. But taking like granted the fact that 2.x python
will be dead in 5 years and that /usr/bin/python will point to python3
is, imho, a little too optimistic.
The point is that there never has to be an agreement about the python
command, as long as all distros support python2/python3 and all scripts use
it (I think that the distinction should continue to be made if/when python2
becomes uncommon, otherwise we'll hit the same issue with python4). We don't
On Mar 2, 2011, at 7:01 PM, Kerrick Staley wrote:
As an aside, this whole thing started when I tried installing ROS, only to
find that it made assumptions about /usr/bin/python, which points to python3
on my Arch Linux system.
Yep, exactly that kind of problem is why I think it's an
49 matches
Mail list logo
