Why not quoting the whole sentence?
Victor
Le 19 sept. 2014 03:31, Ben Hoyt benh...@gmail.com a écrit :
I was emailing someone today about implementing something (for PEP
471, as it happens) and wanted to link to the Zen of Python [1] and
note a particular clause (in this case If the
Hi,
as Fedora is getting closer to having python3 as a default, I'm being more and
more asked by Fedora users/contributors what'll /usr/bin/python invoke when
we achieve this (Fedora 22 hopefully). So I was rereading PEP 394 and I think I
need a small clarification regarding two points in the
On Sep 19, 2014, at 3:31 AM, Bohuslav Kabrda bkab...@redhat.com wrote:
Hi,
as Fedora is getting closer to having python3 as a default, I'm being more
and more asked by Fedora users/contributors what'll /usr/bin/python invoke
when we achieve this (Fedora 22 hopefully). So I was rereading
On Fri, Sep 19, 2014 at 04:44:26AM -0400, Donald Stufft wrote:
On Sep 19, 2014, at 3:31 AM, Bohuslav Kabrda bkab...@redhat.com wrote:
Hi, as Fedora is getting closer to having python3 as a default, I'm
being more and more asked by Fedora users/contributors what'll
/usr/bin/python
On 19 Sep 2014 17:38, Bohuslav Kabrda bkab...@redhat.com wrote:
- Similarly, the more general python command should be installed
whenever any version of Python is installed and should invoke the same
version of Python as either python2 or python3.
The important word in the second point is, I
- Original Message -
On 19 Sep 2014 17:38, Bohuslav Kabrda bkab...@redhat.com wrote:
- Similarly, the more general python command should be installed whenever
any version of Python is installed and should invoke the same version of
Python as either python2 or python3.
The
There are many python2 only scripts with #!/usr/bin/python or
#!/usr/bin/env python shebang in the world.
I think Ubuntu and Fedora's strategy is better for now.
On Fri, Sep 19, 2014 at 7:12 PM, Bohuslav Kabrda bkab...@redhat.com wrote:
On 19 Sep 2014
On Sep 19, 2014, at 03:31 AM, Bohuslav Kabrda wrote:
as Fedora is getting closer to having python3 as a default, I'm being more
and more asked by Fedora users/contributors what'll /usr/bin/python invoke
when we achieve this (Fedora 22 hopefully). So I was rereading PEP 394 and I
think I need a
On Sep 19, 2014, at 10:16 AM, Barry Warsaw ba...@python.org wrote:
If the user wants to invoke Python 3, it's not hard to type 'python3' and I
think that's the message we should be spreading. That already seems pretty
ingrained in user habits afaict.
My biggest problem with ``python3``,
Hi Larry,
I think we need a Python 3.5 Release Schedule PEP.
Cheers,
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
On Sep 19, 2014, at 10:23 AM, Donald Stufft wrote:
My biggest problem with ``python3``, is what happens after 3.9.
FWIW, 3.9 by my rough calculation is 7 years away.
I know Guido doesn’t particularly like two digit version numbers and it’s
been suggested on this list that instead of 3.10 we’re
On Fri, Sep 19, 2014 at 10:41:58AM -0400, Barry Warsaw wrote:
On Sep 19, 2014, at 10:23 AM, Donald Stufft wrote:
My biggest problem with ``python3``, is what happens after 3.9.
FWIW, 3.9 by my rough calculation is 7 years away.
That makes it 2021, one year after Python 2.7 free support
On Fri, 19 Sep 2014 10:16:20 -0400, Barry Warsaw ba...@python.org wrote:
The way I look at it is that /usr/bin/python is user interface.
Distributions are completely free to choose whichever Python they want for
system scripts, and it's great to see that Fedora is well on their way to
making
python should always be the same as python2.
On Fri, Sep 19, 2014 at 8:03 AM, Steven D'Aprano st...@pearwood.info
wrote:
On Fri, Sep 19, 2014 at 10:41:58AM -0400, Barry Warsaw wrote:
On Sep 19, 2014, at 10:23 AM, Donald Stufft wrote:
My biggest problem with ``python3``, is what happens
Donald Stufft don...@stufft.io:
My biggest problem with ``python3``, is what happens after 3.9. I know
Guido doesn’t particularly like two digit version numbers and it’s
been suggested on this list that instead of 3.10 we’re likely to move
directly into 4.0 regardless of if it’s a “big”
On Fri, 19 Sep 2014 08:20:48 -0700
Guido van Rossum gu...@python.org wrote:
python should always be the same as python2.
Always as in eternally?
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
On Sep 19, 2014 8:36 AM, Antoine Pitrou solip...@pitrou.net wrote:
On Fri, 19 Sep 2014 08:20:48 -0700
Guido van Rossum gu...@python.org wrote:
python should always be the same as python2.
Always as in eternally?
Until I say so. Which will happen in the distant future.
ACTIVITY SUMMARY (2014-09-12 - 2014-09-19)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open4662 (+10)
closed 29544 (+35)
total 34206 (+45)
Open issues
On Sep 19, 2014, at 08:40 AM, Guido van Rossum wrote:
Until I say so. Which will happen in the distant future.
I'm gonna hid your time machine keys so you didn't find them.
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
Hi all,
I've just updated the PEP to reflect the API suggestions from Nick, and the
fact that the necessary changes to urllib were landed.
I think this is ready for pronouncement, Guido?
Cheers,
Alex
___
Python-Dev mailing list
Python-Dev@python.org
Yep. I plan to write it on Monday, at the PyCon UK sprints, right after
3.4.2rc1 goes out. FWIW it'll be 3.4 + 18 months.
//arry/
On 09/19/2014 03:31 PM, Barry Warsaw wrote:
Hi Larry,
I think we need a Python 3.5 Release Schedule PEP.
Cheers,
-Barry
The PEP doesn't specify any of the API changes for Python 2.7. I feel it is
necessary for the PEP to show a few typical code snippets using urllib in
Python 2.7 and how one would modify these in order to disable the cert
checking.
There are also a few typos; especially this paragraph puzzled me:
Pushed a new version which I believe adresses all of these. I added an
example of opting-out with urllib.urlopen, let me know if there's any other
APIs you think I should show an example with.
On Fri, Sep 19, 2014 at 3:06 PM, Guido van Rossum gu...@python.org wrote:
The PEP doesn't specify any
On 20 September 2014 00:23, Donald Stufft don...@stufft.io wrote:
On Sep 19, 2014, at 10:16 AM, Barry Warsaw ba...@python.org wrote:
If the user wants to invoke Python 3, it's not hard to type 'python3' and I
think that's the message we should be spreading. That already seems pretty
On 20 September 2014 08:34, Alex Gaynor alex.gay...@gmail.com wrote:
Pushed a new version which I believe adresses all of these. I added an
example of opting-out with urllib.urlopen, let me know if there's any other
APIs you think I should show an example with.
It would be worth explicitly
+1 on Nick's suggestion. (Might also mention that this is the reason why
both functions should exist and have compatible signatures.)
Also please, please, please add explicit mention of Python 2.7, 3.4 and 3.5
in the Abstract (for example in the 3rd paragraph of the abstract).
On Fri, Sep 19,
Donald Stufft wrote:
My biggest problem with ``python3``, is what happens after 3.9.
Python2 technically includes 1.x versions as well, so it
wouldn't be unprecedented for python3 to imply versions
beyond 3.x. It would be a bit confusing, though.
--
Greg
On Sep 19, 2014, at 8:02 PM, Greg Ewing greg.ew...@canterbury.ac.nz wrote:
Donald Stufft wrote:
My biggest problem with ``python3``, is what happens after 3.9.
Python2 technically includes 1.x versions as well, so it
wouldn't be unprecedented for python3 to imply versions
beyond 3.x.
Barry Warsaw wrote:
On Sep 19, 2014, at 08:40 AM, Guido van Rossum wrote:
Until I say so. Which will happen in the distant future.
I'm gonna hid your time machine keys so you didn't find them.
Hiding someone's time machine keys never works. Chances are
he's already taken a trip to the
29 matches
Mail list logo
