On 07/25/2013 06:03 PM, Lennart Regebro wrote:
On Thu, Jul 25, 2013 at 1:53 PM, Laurent Gautier wrote:
My meaning was the use of 2to3's machinery (and fire a message if a
translation occurs) not 2to3 itself, obviously.
I don't understand what you mean is the difference.
//Lennart
bullet-poi
On Thu, Jul 25, 2013 at 10:25:26PM +1000, Nick Coghlan wrote:
> On 25 July 2013 20:38, Toshio Kuratomi wrote:
> >
> > On Jul 24, 2013 6:37 AM, "Brett Cannon" wrote:
> >> The key, though, is adding python2 and getting your code to use that
> >> binary specifically so that shifting the default nam
On Thu, Jul 25, 2013 at 1:53 PM, Laurent Gautier wrote:
> My meaning was the use of 2to3's machinery (and fire a message if a
> translation occurs) not 2to3 itself, obviously.
I don't understand what you mean is the difference.
//Lennart
___
Python-Dev
On 25 July 2013 10:06, Nick Coghlan wrote:
>
> On 25 Jul 2013 05:30, "Toshio Kuratomi" wrote:
>>
>> On Wed, Jul 24, 2013 at 12:42:09PM -0400, Barry Warsaw wrote:
>> > On Jul 25, 2013, at 01:41 AM, Nick Coghlan wrote:
>> >
>> > >How's this for an updated wording in the abstract:
>> > >
>> > > * f
On 25 July 2013 20:38, Toshio Kuratomi wrote:
>
> On Jul 24, 2013 6:37 AM, "Brett Cannon" wrote:
>> The key, though, is adding python2 and getting your code to use that
>> binary specifically so that shifting the default name is more of a
>> convenience than something which might break existing
On 07/25/2013 01:19 PM, Lennart Regebro wrote:
On Thu, Jul 25, 2013 at 12:41 PM, Laurent Gautier wrote:
- a user is running a python script (he expects to be working), and is using
the default /usr/bin/python (formerly Python 2, now Python 3). If the
program fails because of obvious Python 2-on
On Thu, Jul 25, 2013 at 12:41 PM, Laurent Gautier wrote:
> - a user is running a python script (he expects to be working), and is using
> the default /usr/bin/python (formerly Python 2, now Python 3). If the
> program fails because of obvious Python 2-only idioms, reporting this rather
> that the
On 07/25/2013 11:45 AM, Maciej Fijalkowski wrote:
On Wed, Jul 24, 2013 at 7:22 PM, Laurent Gautier wrote:
On 07/24/2013 06:30 PM, Chris Angelico wrote:
On Thu, Jul 25, 2013 at 2:21 AM, Laurent Gautier
wrote:
- errors that are typical of "Python 2 script running with Python
3"-specific are pr
On Jul 24, 2013 6:37 AM, "Brett Cannon" wrote:
> The key, though, is adding python2 and getting your code to use that
binary specifically so that shifting the default name is more of a
convenience than something which might break existing code not ready for
the switch.
>
Applicable to this, does
On Wed, Jul 24, 2013 at 7:22 PM, Laurent Gautier wrote:
> On 07/24/2013 06:30 PM, Chris Angelico wrote:
>>
>> On Thu, Jul 25, 2013 at 2:21 AM, Laurent Gautier
>> wrote:
>>>
>>> - errors that are typical of "Python 2 script running with Python
>>> 3"-specific are probably limited (e.g., use of uni
- Original Message -
> Am 24.07.13 11:12, schrieb Bohuslav Kabrda:
> > - Should we point /usr/bin/python to Python 3 when we make the move?
>
> This should depend on the answer to this question:
> - for how long have you been providing /usr/bin/python2 binaries?
>
Huh, I don't know exact
- Original Message -
> On Wed, Jul 24, 2013 at 11:12 AM, Bohuslav Kabrda wrote:
> > - Should we point /usr/bin/python to Python 3 when we make the move?
>
> No.
>
> > - What should user get after using "yum install python"?
>
> Will a base install include Python 3? If it does, I think y
On 25 Jul 2013 05:30, "Toshio Kuratomi" wrote:
>
> On Wed, Jul 24, 2013 at 12:42:09PM -0400, Barry Warsaw wrote:
> > On Jul 25, 2013, at 01:41 AM, Nick Coghlan wrote:
> >
> > >How's this for an updated wording in the abstract:
> > >
> > > * for the time being, all distributions should ensure that
Chris Angelico wrote:
print "Hello, world!"
SyntaxError: invalid syntax
Is it safe
to presume that it's more likely a syntax error will come from an
interpreter version mismatch than a code bug?
Maybe look at sys.args[0], and if it ends in "python" with
no version number, add something to the
On Wed, Jul 24, 2013 at 7:22 PM, Laurent Gautier wrote:
> The wrapper in /usr/bin/python:
> - could use what is in 2to3. I think that most of the cases are solved
> there.
Only the most trivial cases are solved completely by 2to3, and the
error messages you would get would be hard to understand,
On Wed, Jul 24, 2013 at 12:42:09PM -0400, Barry Warsaw wrote:
> On Jul 25, 2013, at 01:41 AM, Nick Coghlan wrote:
>
> >How's this for an updated wording in the abstract:
> >
> > * for the time being, all distributions should ensure that python
> >refers to the same target as python2
> > * howeve
Gustavo Carneiro, 24.07.2013 19:16:
> On Wed, Jul 24, 2013 at 6:04 PM, Terry Reedy wrote:
>> On 7/24/2013 5:12 AM, Bohuslav Kabrda wrote:
>>> Hi all, in recent days, there has been a discussion on fedora-devel
>>> (see thread [1]) about moving to Python 3 as a default.
>>
>> Not being a current *ni
On 07/24/2013 06:30 PM, Chris Angelico wrote:
On Thu, Jul 25, 2013 at 2:21 AM, Laurent Gautier wrote:
- errors that are typical of "Python 2 script running with Python
3"-specific are probably limited (e.g., use of unicode, use of xrange,
etc...)
The most common, in interactive scripts at lea
On Wed, Jul 24, 2013 at 6:04 PM, Terry Reedy wrote:
> On 7/24/2013 5:12 AM, Bohuslav Kabrda wrote:
>
>> Hi all, in recent days, there has been a discussion on fedora-devel
>> (see thread [1]) about moving to Python 3 as a default.
>>
>
> Default-shift is a known natural language phenomenon.
> htt
On 7/24/2013 5:12 AM, Bohuslav Kabrda wrote:
Hi all, in recent days, there has been a discussion on fedora-devel
(see thread [1]) about moving to Python 3 as a default.
Default-shift is a known natural language phenomenon.
https://en.wikipedia.org/wiki/Retronym
It is inevitably messy in the mid
On Jul 25, 2013, at 01:41 AM, Nick Coghlan wrote:
>How's this for an updated wording in the abstract:
>
> * for the time being, all distributions should ensure that python
>refers to the same target as python2
> * however, users should be aware that python refers to python3 on at
>least Arch Lin
On Jul 24, 2013, at 08:26 AM, Toshio Kuratomi wrote:
> I think bkabrda is looking for some clarification on PEP-394. My
>reading and participation in the previous discussions lead me to believe
>that while PEP-394 wants to be diplomatic, the message it wants to get
>across is:
>
>1) warn distrib
On Wed, Jul 24, 2013 at 10:56 AM, Lennart Regebro wrote:
> On Wed, Jul 24, 2013 at 3:54 PM, Lennart Regebro wrote:
>> On Wed, Jul 24, 2013 at 11:12 AM, Bohuslav Kabrda wrote:
>>> - Should we point /usr/bin/python to Python 3 when we make the move?
>>
>> No.
>
> To be more explicit. I think it's
On Thu, Jul 25, 2013 at 2:21 AM, Laurent Gautier wrote:
> - errors that are typical of "Python 2 script running with Python
> 3"-specific are probably limited (e.g., use of unicode, use of xrange,
> etc...)
>
The most common, in interactive scripts at least, is likely to be:
>>> print "Hello, wo
Am 24.07.13 17:56, schrieb Lennart Regebro:> On Wed, Jul 24, 2013 at
3:54 PM, Lennart Regebro wrote:
>> On Wed, Jul 24, 2013 at 11:12 AM, Bohuslav Kabrda
wrote:
>>> - Should we point /usr/bin/python to Python 3 when we make the move?
>>
>> No.
>
> To be more explicit. I think it's perfectly fine
On 07/24/2013 05:56 PM, Lennart Regebro wrote:
On Wed, Jul 24, 2013 at 3:54 PM, Lennart Regebro wrote:
On Wed, Jul 24, 2013 at 11:12 AM, Bohuslav Kabrda wrote:
- Should we point /usr/bin/python to Python 3 when we make the move?
No.
To be more explicit. I think it's perfectly fine to not pr
On Jul 24, 2013, at 05:12 AM, Bohuslav Kabrda wrote:
>in recent days, there has been a discussion on fedora-devel (see thread [1])
>about moving to Python 3 as a default.
I've been lurking via Gmane. :)
>- Should we point /usr/bin/python to Python 3 when we make the move?
Over in Debian (inheri
On Wed, Jul 24, 2013 at 3:54 PM, Lennart Regebro wrote:
> On Wed, Jul 24, 2013 at 11:12 AM, Bohuslav Kabrda wrote:
>> - Should we point /usr/bin/python to Python 3 when we make the move?
>
> No.
To be more explicit. I think it's perfectly fine to not provide a
/usr/bin/python at all, but I think
On 25 July 2013 01:41, Nick Coghlan wrote:
> How's this for an updated wording in the abstract:
>
> * for the time being, all distributions should ensure that python
> refers to the same target as python2
> * however, users should be aware that python refers to python3 on at
> least Arch Linux
On 25 July 2013 01:26, Toshio Kuratomi wrote:
> On Wed, Jul 24, 2013 at 09:34:11AM -0400, Brett Cannon wrote:
>> A similar discussion broke out when Arch Linux switched python to point to
>> python3. This led to http://www.python.org/dev/peps/pep-0394/ which says have
>> python2/python3, and have
Note: I'm the opposite number to bkabrda in the discussion on the Fedora
Lists about how quickly we should be breaking end-user expectations of what
"python" means.
On Wed, Jul 24, 2013 at 09:34:11AM -0400, Brett Cannon wrote:
>
>
>
> On Wed, Jul 24, 2013 at 5:12 AM, Bohuslav Kabrda wrote:
>
Am 24.07.13 11:12, schrieb Bohuslav Kabrda:
> - Should we point /usr/bin/python to Python 3 when we make the move?
This should depend on the answer to this question:
- for how long have you been providing /usr/bin/python2 binaries?
Users "should" have been explicit in declaring scripts as
/usr/bi
Haven't been over to yum land in a while, but usually they stabilize the
distro in synergy to the python version. Ubuntu came with 2.7, and I just
use sudo-apt get install, for 3.2(or a gui package manager), and then can
use 3.2 with using the command python3.2 in command line, or you can
compile f
On Wed, Jul 24, 2013 at 11:12 AM, Bohuslav Kabrda wrote:
> - Should we point /usr/bin/python to Python 3 when we make the move?
No.
> - What should user get after using "yum install python"?
Will a base install include Python 3? If it does, I think yum install
python should mean python3, and he
On Wed, Jul 24, 2013 at 5:12 AM, Bohuslav Kabrda wrote:
> Hi all,
> in recent days, there has been a discussion on fedora-devel (see thread
> [1]) about moving to Python 3 as a default.
> I'd really love to hear opinions on the matter from the upstream, mainly
> regarding these two points (that a
On Wed, Jul 24, 2013 at 12:36 PM, Paul Moore wrote:
> On 24 July 2013 10:12, Bohuslav Kabrda wrote:
>>
>> - What should user get after using "yum install python"?
>> There are basically few ways of coping with this:
>> 1) Just keep doing what we do, eventually far in the future drop "python"
>> p
On 24 July 2013 10:12, Bohuslav Kabrda wrote:
> - What should user get after using "yum install python"?
> There are basically few ways of coping with this:
> 1) Just keep doing what we do, eventually far in the future drop "python"
> package and never provide it again (= go on only with python3/
On Wed, Jul 24, 2013 at 11:12 AM, Bohuslav Kabrda wrote:
> - What should user get after using "yum install python"?
> There are basically few ways of coping with this:
> 1) Just keep doing what we do, eventually far in the future drop "python"
> package and never provide it again (= go on only wi
On Wed, Jul 24, 2013 at 7:12 PM, Bohuslav Kabrda wrote:
> - What should user get after using "yum install python"?
> There are basically few ways of coping with this:
> 1) Just keep doing what we do, eventually far in the future drop "python"
> package and never provide it again (= go on only wit
39 matches
Mail list logo
