CC'ing Python-Ideas. Follow-ups to Python-Ideas please.
On Thu, Oct 29, 2015 at 09:22:15PM -0400, Terry Reedy wrote:
> Leaving IDLE aside, the reason '' is added to sys.path is so that people
> can import their own modules. This is very useful. Shadowing is the
> result of putting it at the
I'm unable to submit any file to any issue, neither via web-form nor via
e-mail. Checked with different browsers from different computers.
Meta-tracker doesn't work too.
http://psf.upfronthosting.co.za/roundup/meta/issue575
___
Python-Dev mailing
In a message of Sun, 01 Nov 2015 08:29:32 +0200, Serhiy Storchaka writes:
>I'm unable to submit any file to any issue, neither via web-form nor via
>e-mail. Checked with different browsers from different computers.
>Meta-tracker doesn't work too.
>
On 1 Nov 2015, at 10:30 a.m., Chris Angelico wrote:
>
> PEP 478 [1] doesn't currently have any info on a planned 3.5.1 release
> (and actually, it has 3.5.0 Final listed as a future release). About
> when is it likely to happen? The one thing I'm hanging out for is an
>
On Sun, Nov 1, 2015 at 9:55 PM, Phil Thompson
wrote:
> On 1 Nov 2015, at 10:30 a.m., Chris Angelico wrote:
>>
>> PEP 478 [1] doesn't currently have any info on a planned 3.5.1 release
>> (and actually, it has 3.5.0 Final listed as a future release).
PEP 478 [1] doesn't currently have any info on a planned 3.5.1 release
(and actually, it has 3.5.0 Final listed as a future release). About
when is it likely to happen? The one thing I'm hanging out for is an
installer patch on Windows that detects XP and immediately aborts with
a convenient
The installer and the contained contents are currently tied together, making it
fairly difficult to mix and match versions.
When 3.5.1 happens is up to Larry, but I'm feeling like the initial rush of bug
reports has died down and we should be considering the remaining open ones in
the context
"The initial rush of bug reports I see has not gone down. It's been in steady
increase."
To clarify, I meant unique bugs. When my job is to fix them, more reports of
the same bug are not important to me, especially once they've been fixed but
not released.
I do understand that someone has to
In a message of Sun, 01 Nov 2015 08:23:48 -0800, Steve Dower writes:
>"The initial rush of bug reports I see has not gone down. It's been in steady
>increase."
>
>To clarify, I meant unique bugs. When my job is to fix them, more reports of
>the same bug are not important to me, especially once
On 11/01/2015 09:10 AM, Laura Creighton wrote:
Put that on python.org as soon as possible.
even if you need to bump the python 3.5 numbering.
you get 3.5.1 for this, and this alone and everybody else gets to
wait for 3.5.2 and when Larry feels this is a good idea.
Well, let me say this. I
On 01.11.15 08:29, Serhiy Storchaka wrote:
I'm unable to submit any file to any issue, neither via web-form nor via
e-mail. Checked with different browsers from different computers.
Meta-tracker doesn't work too.
http://psf.upfronthosting.co.za/roundup/meta/issue575
Sorry for the noise. The
In a message of Sun, 01 Nov 2015 05:52:40 -0800, Steve Dower writes:
>The installer and the contained contents are currently tied together, making
>it fairly difficult to mix and match versions.
>
>When 3.5.1 happens is up to Larry, but I'm feeling like the initial rush of
>bug reports has died
In a message of Sun, 01 Nov 2015 10:51:05 -0800, Larry Hastings writes:
>
>
>On 11/01/2015 09:10 AM, Laura Creighton wrote:
>> Put that on python.org as soon as possible.
>> even if you need to bump the python 3.5 numbering.
>> you get 3.5.1 for this, and this alone and everybody else gets to
>>
On Mon, Nov 2, 2015 at 5:51 AM, Larry Hastings wrote:
> If I didn't have any release blockers, I'd schedule 3.5.1 for sometime
> around three weeks from now. And FYI I want to release 3.4.4 about two
> weeks after that.
>
Thanks Larry! That'd be awesome. If there's testing
On Sun, Nov 1, 2015 at 4:42 PM, Benjamin Peterson
wrote:
> Happy November, everyone. It’s nearly time for the next semi-annual
> instalment of the 2.7 series. I’m planning to release a 2.7.11 release
> candidate on November 21st and 2.7.11 final on December 5.
>
> More than
Happy November, everyone. It’s nearly time for the next semi-annual
instalment of the 2.7 series. I’m planning to release a 2.7.11 release
candidate on November 21st and 2.7.11 final on December 5.
More than half-done releasing 2.7-ly yours,
Benjamin
On Fri, Oct 23, 2015 at 3:23 AM, Victor Stinner
wrote:
> Note: I propose "noopt" because we already have "optimization level 0"
> which still uses optimizations, it's the default mode. It's different
> than gcc -O0 which really disables all optimizations. I already
17 matches
Mail list logo