Re: [Python-Dev] [RELEASE] Python 3.4.2 is now available

2014-10-08 Thread Geoffrey Spear
It looks like the Download dropdown on python.org has a blank button
(when accessed from Windows) has an empty button that's supposed to be
for the 3.4.2 release by just links back to the current page; the 2.7
button is working fine.

On Wed, Oct 8, 2014 at 4:57 AM, Larry Hastings  wrote:
>
>
> On behalf of the Python development community and the Python 3.4 release
> team, I'm pleased to announce the availability of Python 3.4.2.   Python
> 3.4.2 has many bugfixes and other small improvements over 3.4.1.  One new
> feature for Mac OS X users: the OS X installers are now distributed as
> signed installer package files compatible with the OS X Gatekeeper security
> feature.
>
> You can download it here:
>
> https://www.python.org/download/releases/3.4.2
>
>
> May the road rise up to meet you,
>
>
> /arry
>
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/geoffspear%40gmail.com
>
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Backporting ensurepip to 2.7, Which commands to install?

2014-10-22 Thread Geoffrey Spear
On Wed, Oct 22, 2014 at 6:15 AM, Pekka Klärck  wrote:
> [Replying to a mail that was sent before I joined this list. Quoting,
> headers, etc. aren't exactly right.]
>
> Nick Coghlan wrote:
>>On 4 October 2014 10:51, Donald Stufft  wrote:
>>> Whoops, I misred.
>>>
>>> So to be clear, you think:
>>>
>>> install -> pip, pip2, pip2.7
>>> altinstall -> pip2.7
>>
>> To spell out the assumption I didn't make clear when helping with the
>> backport PEP, the difference comes from PEP 394, which specifies the
>> following behaviour when installing Python itself:
>>
>> Python 2.7: python, python2, python2.7
>> Python 3.4: python3, python3.4
>>
>> That maps to ensurepip as:
>>
>> Python 2.7: pip, pip2, pip2.7
>> Python 3.4: pip3, pip3.4
>
> I just installed Python 3.4.2 on Windows and noticed that its Scripts
> directory has these files out-of-the-box:
>
> easy_install.exe
> easy_install-3.4.exe.
> pip.exe
> pip3.exe
> pip3.4.exe
>
> Based on Nick's explanation above, having pip.exe there looks like bug
> in the installer and could easily cause a conflict with other pip
> installations. I don't understand why easy_install is included there
> in the first place, but easy_install.exe can obviously cause a similar
> conflict.

Nick's explanation is based on PEP 394, which explicitly does not
apply to Windows. The Windows Python executables are called
"python.exe" and "pythonw.exe"; no "3" has ever been part of the name
and it's not surprising that there's a matching "pip.exe". The
pip3.exe and pip3.4.exe being installed are actually the anomalies
here, but I wouldn't call them a bug.
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] [RELEASED] Python 3.4.3 is now available

2015-02-27 Thread Geoffrey Spear
The download button (for Windows anyway) on the python.org Download
dropdown menu is broken; there's a small gray square where the 3.4.3 button
should be, with the 2.7.9 one working fine.

On Wed, Feb 25, 2015 at 8:07 AM, Larry Hastings  wrote:

>
>
>  On behalf of the Python development community and the Python 3.4 release
> team, I'm pleased to announce the availability of Python 3.4.3.   Python
> 3.4.3 has many bugfixes and other small improvements over 3.4.2.
>
> You can find it here:
>
> https://www.python.org/downloads/release/python-343/
>
>
> The release slipped by two or three days, depending on what time zone
> you're in.  This is my fault--I apologize for the inconvenience.
>
> Cheers,
>
>
> */arry*
>
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/geoffspear%40gmail.com
>
>
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] issue with itertools leads the crash

2014-04-09 Thread Geoffrey Spear
On Wed, Apr 9, 2014 at 1:53 PM, MRAB  wrote:
> On 2014-04-09 14:26, Mark Lawrence wrote:
>>
>> On 08/04/2014 17:30, MRAB wrote:
>>>
>>> On 2014-04-08 16:31, Brett Cannon wrote:
>>>
>>> Something for Python 3.5, maybe? :-)
>>>
>>> It's not going to happen in Python 2.7; that's the end of the Python 2
>>> series, and it's getting security fixes only.
>>
>>
>> According to http://legacy.python.org/dev/peps/pep-0373/ the final
>> release of 2.7 is scheduled to be 2.7.9 in May 2015.  Did you mean to
>> say that 2.7 isn't getting new features?
>>
> Err, probably... :-(

Of course, this raises the question of whether making slice assignment
not go into an infinite loop when the programmer asks it to is a
bugfix or a new feature.

Calling:

list(itertools.cycle([0]))

exhibits the same behavior for the same reason, and I don't think
anyone would call that a bug in Python.
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] PEP 8 misnaming

2012-03-14 Thread Geoffrey Spear
On Wed, Mar 14, 2012 at 7:21 AM, Facundo Batista
 wrote:
> Hello!
>
> In the "Maximum Line Length" section of PEP 8 it says:
>
>    "The preferred place to break around a binary operator is *after*
> the operator, not before it."
>
> And after that is an example (trimmed here):
>
>            if (width == 0 and height == 0 and
>                color == 'red' and emphasis == 'strong' or
>                highlight > 100):
>                raise ValueError("sorry, you lose")
>
> In the example the line is broken after the 'and' or 'or' *keywords*,
> not after the '==' *operator* (which is the nice way of doing it).
>
> Maybe the sentence above is misleading?

'and' and 'or' are both binary logical operators. The fact that they
are keywords is irrelevant; the sentence isn't misleading.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com