Re: [Python-Dev] Fwd: PEP 467: Minor API improvements for bytes & bytearray

2014-08-18 Thread Chris Barker
On Mon, Aug 18, 2014 at 1:06 PM, Terry Reedy wrote: > The byte scalar is an int in range(256). Bytes is an array of such. > then why the complaint about iterating over bytes producing ints? Ye,s a byte owuld be pretty much teh same as an int, but it would have restrictions - useful ones. numpy

Re: [Python-Dev] os.walk() is going to be *fast* with scandir

2014-08-18 Thread Robert Collins
Indeed - my suggestion is applicable to people using the library -Rob On 10 Aug 2014 18:21, "Larry Hastings" wrote: > On 08/09/2014 10:40 PM, Robert Collins wrote: > > A small tip from my bzr days - cd into the directory before scanning it > > > I doubt that's permissible for a library function

Re: [Python-Dev] https:bugs.python.org -- Untrusted Connection (Firefox)

2014-08-18 Thread Oleg Broytman
On Mon, Aug 18, 2014 at 03:26:48PM -0500, Ian Cordasco wrote: > On Mon, Aug 18, 2014 at 3:22 PM, Benjamin Peterson > wrote: > > It uses a CACert certificate, which your system probably doesn't trust. > > > > On Mon, Aug 18, 2014, at 13:12, Terry Reedy wrote: > >> Firefox does not want to connec

Re: [Python-Dev] https:bugs.python.org -- Untrusted Connection (Firefox)

2014-08-18 Thread Ian Cordasco
On Mon, Aug 18, 2014 at 3:22 PM, Benjamin Peterson wrote: > It uses a CACert certificate, which your system probably doesn't trust. > > On Mon, Aug 18, 2014, at 13:12, Terry Reedy wrote: >> Firefox does not want to connect to https:bugs.python.org. Plain >> bugs.python.org works fine. Has the cert

Re: [Python-Dev] https:bugs.python.org -- Untrusted Connection (Firefox)

2014-08-18 Thread Benjamin Peterson
It uses a CACert certificate, which your system probably doesn't trust. On Mon, Aug 18, 2014, at 13:12, Terry Reedy wrote: > Firefox does not want to connect to https:bugs.python.org. Plain > bugs.python.org works fine. Has the certificate expired? > > -- > Terry Jan Reedy > >

Re: [Python-Dev] https:bugs.python.org -- Untrusted Connection (Firefox)

2014-08-18 Thread Oleg Broytman
On Mon, Aug 18, 2014 at 04:12:22PM -0400, Terry Reedy wrote: > Firefox does not want to connect to https:bugs.python.org. Works for me (FF 31). Oleg. -- Oleg Broytmanhttp://phdru.name/p...@phdru.name Programmers don't die, they just GOSUB without RETUR

[Python-Dev] https:bugs.python.org -- Untrusted Connection (Firefox)

2014-08-18 Thread Terry Reedy
Firefox does not want to connect to https:bugs.python.org. Plain bugs.python.org works fine. Has the certificate expired? -- Terry Jan Reedy ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscr

Re: [Python-Dev] Fwd: PEP 467: Minor API improvements for bytes & bytearray

2014-08-18 Thread Terry Reedy
On 8/18/2014 12:04 PM, Chris Barker wrote: On Sun, Aug 17, 2014 at 2:41 PM, Barry Warsaw mailto:ba...@python.org>> wrote: I think the biggest API "problem" is that default iteration returns integers instead of bytes. That's a real pain. what is really needed for this NOT to be a p

Re: [Python-Dev] Fwd: PEP 467: Minor API improvements for bytes & bytearray

2014-08-18 Thread Chris Barker
On Sun, Aug 17, 2014 at 2:41 PM, Barry Warsaw wrote: > I think the biggest API "problem" is that default iteration returns > integers > instead of bytes. That's a real pain. > what is really needed for this NOT to be a pain is a byte scalar. numpy has a scalar type for every type it supports -

Re: [Python-Dev] PEP 4000 to explicitly declare we won't be doing a Py3k style compatibility break again?

2014-08-18 Thread Antoine Pitrou
Le 18/08/2014 13:22, Mark Dickinson a écrit : [Moderately off-topic] On Sun, Aug 17, 2014 at 3:39 AM, Steven D'Aprano mailto:st...@pearwood.info>> wrote: I used to refer to Python 4000 as the hypothetical compatibility break version. Now I refer to Python 5000. I personally think it s

Re: [Python-Dev] PEP 4000 to explicitly declare we won't be doing a Py3k style compatibility break again?

2014-08-18 Thread Mark Dickinson
[Moderately off-topic] On Sun, Aug 17, 2014 at 3:39 AM, Steven D'Aprano wrote: > I used to refer to Python 4000 as the hypothetical compatibility break > version. Now I refer to Python 5000. > I personally think it should be Python 500, or Py5M. When we come to create the mercurial branch,

[Python-Dev] Review needed for patch for issue #12067

2014-08-18 Thread Andreas Maier
Hello, a patch for issue #12067 (targeting Py 3.5) is available since a few weeks and is ready for review. From my perspective, it is ready for commit. Could the community please review the patch? https://bugs.python.org/issue12067 Thanks, Andy ___

Re: [Python-Dev] Fwd: PEP 467: Minor API improvements for bytes & bytearray

2014-08-18 Thread Barry Warsaw
On Aug 17, 2014, at 09:48 PM, Donald Stufft wrote: >from __future__ import bytesdoneright? :D Synonymous to: bytes = bytesdoneright or maybe from bytesdoneright import bytes :) -Barry ___ Python-Dev mailing list Python-Dev@python.org https://mail.p

Re: [Python-Dev] PEP 4000 to explicitly declare we won't be doing a Py3k style compatibility break again?

2014-08-18 Thread Barry Warsaw
On Aug 17, 2014, at 06:02 PM, Guido van Rossum wrote: >I'm unsure about what's the single biggest pain moving to Python 3. In the >past I would have said that it's for sure the bytes/str split (which both >the biggest pain and the biggest payoff). > >But if I look carefully into the soul of teams

Re: [Python-Dev] PEP 467: Minor API improvements for bytes & bytearray

2014-08-18 Thread Barry Warsaw
On Aug 17, 2014, at 09:39 PM, Antoine Pitrou wrote: >> need for a special case for a single byte. We already have a perfectly >> good spelling: >> NUL = bytes([0]) > >That is actually a very cumbersome spelling. Why should I first create a >one-element list in order to create a one-byte bytes