On 23 September 2014 10:20, Larry Hastings la...@hastings.org wrote:
On 09/19/2014 03:31 PM, Barry Warsaw wrote:
I think we need a Python 3.5 Release Schedule PEP.
Just checked it in as PEP 478. It should show up here in a few minutes:
http://legacy.python.org/dev/peps/pep-0478/
Thanks.
On 23 September 2014 19:46, Nick Coghlan ncogh...@gmail.com wrote:
Under consideration (in addition to the items already listed in the PEP):
PEP 432 (simplifying the startup sequence)
PEP 475 (retry system calls failing with EINTR)
Improved Windows console Unicode support (see
To all who contributed to Mac OS X improvements:
Thank you!
I downloaded and installed last night on Mavericks 10.9. It was quick,
straightforward, and completed in seconds. For contrast, I talked
several new users at an Intro to Python workshop this past weekend how
to install 3.4.1; it
Larry Hastings wrote:
On 09/19/2014 03:31 PM, Barry Warsaw wrote:
I think we need a Python 3.5 Release Schedule PEP.
Just checked it in as PEP 478. It should show up here in a few minutes:
http://legacy.python.org/dev/peps/pep-0478/
Key facts:
. Beta 1 is May 24th 2015, about a month
In article 54217c0d.90...@willingconsulting.com,
Carol Willing willi...@willingconsulting.com wrote:
[...] The new 3.4.2rc1 installer is a *big* improvement.
Thanks for the feedback, Carol. Let us know via bugs.python.org of any
issues you see. BTW, the new installer format will be coming to
On 24 September 2014 03:05, Steve Dower steve.do...@microsoft.com wrote:
Larry Hastings wrote:
On 09/19/2014 03:31 PM, Barry Warsaw wrote:
I think we need a Python 3.5 Release Schedule PEP.
Just checked it in as PEP 478. It should show up here in a few minutes:
On Sep 23, 2014, at 9:48 PM, Nick Coghlan ncogh...@gmail.com wrote:
On 24 September 2014 03:05, Steve Dower steve.do...@microsoft.com
mailto:steve.do...@microsoft.com wrote:
Larry Hastings wrote:
On 09/19/2014 03:31 PM, Barry Warsaw wrote:
I think we need a Python 3.5 Release Schedule
On Sep 23, 2014, at 10:14 PM, Steve Dower steve.do...@microsoft.com wrote:
This new compiler has the incredibly awesome feature of being forwards
compatible
right? Like in 10 years stuff compiled with a newer compiler will still work?
That's the promise at least :)
All the macros
This new compiler has the incredibly awesome feature of being forwards
compatible
right? Like in 10 years stuff compiled with a newer compiler will still work?
That's the promise at least :)
All the macros that leaked implementation details (like file descriptors) are
now isolated so if they
On 23/09/2014 18:05, Steve Dower wrote:
I'm also considering/experimenting with installing into Program
Files by default, but I suspect that isn't going to work out yet.
I'd like to see that go forward: I think it's increasingly difficult to
justify Python's position at c:\pythonxx. But it
10 matches
Mail list logo
