Re: [Python-ideas] Proposal to change Python version release cycle

On 04/11/2017 13:29, Antoine Pitrou wrote: > > Hello Wolfgang, > > On Sat, 4 Nov 2017 12:25:57 +0100 (CET) > tds...@mailbox.org wrote: >> Hello, >> >> one of my long standing ideas to improve Python is to adjust the >> release cycle and version number handling. In short, to simplify it. > >

Re: [Python-ideas] Moving typing out of the stdlib in Python 3.7?

On 5 November 2017 at 06:22, Guido van Rossum wrote: > On Sat, Nov 4, 2017 at 7:05 AM, Nick Coghlan wrote: >> >> Perhaps typing could switch to being a bundled module, such that it >> had its own version, independent of the Python standard library >>

Re: [Python-ideas] Proposal to change Python version release cycle

On 5 November 2017 at 01:29, Wolfgang wrote: > On 04.11.2017 16:01, Nick Coghlan wrote: >> We're currently more likely to go the other direction, and stick with >> the 3.x numbering for an extended period (potentially reaching 3.10, >> 3.11, 3.12, etc), so that the ongoing

Re: [Python-ideas] Moving typing out of the stdlib in Python 3.7?

On Sat, Nov 4, 2017 at 7:05 AM, Nick Coghlan wrote: > Perhaps typing could switch to being a bundled module, such that it > had its own version, independent of the Python standard library > version, but was still present by default in new installations? > This is beginning

Re: [Python-ideas] Proposal to change Python version release cycle

On Sat, Nov 4, 2017 at 10:44 AM, M.-A. Lemburg wrote: > Just to clarify: Python 2.0 was called 2.0 because the BeOpen marketing > department thought it was good idea, not because there were major > incompatible changes going into that release. > Alternative history question: if

Re: [Python-ideas] Proposal to change Python version release cycle

Just to clarify: Python 2.0 was called 2.0 because the BeOpen marketing department thought it was good idea, not because there were major incompatible changes going into that release. Porting code from Python 1.5.2 to 2.0 was relatively straight forward and not much different from other minor

Re: [Python-ideas] Moving typing out of the stdlib in Python 3.7?

I could see the typing module staying but: - typing_extension (or the new official external module) append types in the typing module; - if typing_extension is not installed or too old and missing some types, any missing type being accessed returns some kind of mock object that avoid crashing; -

Re: [Python-ideas] Proposal to change Python version release cycle

On Sun, Nov 5, 2017 at 2:29 AM, Wolfgang wrote: > A good point but two digits minor version numbers have the possibility > to break a lot code. There is a lot of stuff out where a single digit > major version is assumed. Even the official Python build for windows > with

Re: [Python-ideas] Proposal to change Python version release cycle

On 04.11.2017 16:44, M.-A. Lemburg wrote: Just to clarify: Python 2.0 was called 2.0 because the BeOpen marketing department thought it was good idea, not because there were major incompatible changes going into that release. Porting code from Python 1.5.2 to 2.0 was relatively straight forward

Re: [Python-ideas] Proposal to change Python version release cycle

Hi Nick, On 04.11.2017 16:01, Nick Coghlan wrote: On 5 November 2017 at 00:40, Wolfgang wrote: On 04.11.2017 14:29, Antoine Pitrou wrote: Hello Wolfgang, On Sat, 4 Nov 2017 12:25:57 +0100 (CET) tds...@mailbox.org wrote: Hello, one of my long standing ideas to

Re: [Python-ideas] Proposal to change Python version release cycle

On Sat, 4 Nov 2017 16:10:32 +0100 Wolfgang wrote: > > Another possibility is to change only the versioning > to major.minor instead of major.minor.patch. Then having > a simpler versioning scheme for other Python implementations > as only benefit (and the simplification to

Re: [Python-ideas] Proposal to change Python version release cycle

Hi Nick, On 04.11.2017 15:48, Nick Coghlan wrote: On 4 November 2017 at 23:29, Antoine Pitrou wrote: Hello Wolfgang, On Sat, 4 Nov 2017 12:25:57 +0100 (CET) tds...@mailbox.org wrote: Hello, one of my long standing ideas to improve Python is to adjust the release cycle

Re: [Python-ideas] Proposal to change Python version release cycle

On 5 November 2017 at 00:40, Wolfgang wrote: > > > On 04.11.2017 14:29, Antoine Pitrou wrote: >> >> >> Hello Wolfgang, >> >> On Sat, 4 Nov 2017 12:25:57 +0100 (CET) >> tds...@mailbox.org wrote: >>> >>> Hello, >>> >>> one of my long standing ideas to improve Python is to adjust

Re: [Python-ideas] Proposal to change Python version release cycle

On 4 November 2017 at 23:29, Antoine Pitrou wrote: > > Hello Wolfgang, > > On Sat, 4 Nov 2017 12:25:57 +0100 (CET) > tds...@mailbox.org wrote: >> Hello, >> >> one of my long standing ideas to improve Python is to adjust the >> release cycle and version number handling. In

Re: [Python-ideas] Proposal to change Python version release cycle

On 04.11.2017 14:29, Antoine Pitrou wrote: Hello Wolfgang, On Sat, 4 Nov 2017 12:25:57 +0100 (CET) tds...@mailbox.org wrote: Hello, one of my long standing ideas to improve Python is to adjust the release cycle and version number handling. In short, to simplify it. There has been ample

Re: [Python-ideas] install pip packages from Python prompt

On Saturday, November 4, 2017, Erik Bray wrote: > On Nov 4, 2017 08:31, "Stephen J. Turnbull" tsukuba.ac.jp > > > wrote: > > Erik Bray writes: > > > Nope. I totally get that

Re: [Python-ideas] Proposal to change Python version release cycle

Hello Wolfgang, On Sat, 4 Nov 2017 12:25:57 +0100 (CET) tds...@mailbox.org wrote: > Hello, > > one of my long standing ideas to improve Python is to adjust the > release cycle and version number handling. In short, to simplify it. There has been ample discussion in the past about changing our

Re: [Python-ideas] Proposal to change Python version release cycle

On Sat, Nov 4, 2017 at 11:00 PM, Wolfgang wrote: > > > On 04.11.2017 12:35, Chris Angelico wrote: >> >> On Sat, Nov 4, 2017 at 10:25 PM, wrote: >>> >>> I suggest to change this to increment the major version for every new >>> release >>> of the 1,5 year

Re: [Python-ideas] Proposal to change Python version release cycle

On 04.11.2017 12:35, Chris Angelico wrote: On Sat, Nov 4, 2017 at 10:25 PM, wrote: I suggest to change this to increment the major version for every new release of the 1,5 year cycle. And allow new Python standard library backward compatible changes for every minor

Re: [Python-ideas] Proposal to change Python version release cycle

On Sat, Nov 4, 2017 at 10:25 PM, wrote: > I suggest to change this to increment the major version for every new release > of the 1,5 year cycle. > And allow new Python standard library backward compatible changes for every > minor release cycle every 6 months. The usual

[Python-ideas] Proposal to change Python version release cycle

Hello, one of my long standing ideas to improve Python is to adjust the release cycle and version number handling. In short, to simplify it. This is the first draft of the idea: Proposal to change Python version release cycle === Goal

Re: [Python-ideas] install pip packages from Python prompt

On Nov 4, 2017 08:31, "Stephen J. Turnbull" < turnbull.stephen...@u.tsukuba.ac.jp> wrote: Erik Bray writes: > Nope. I totally get that they don’t know what a shell or command prompt > is. THEY. NEED. TO. LEARN. Just to be clear I did not write this. Someone replying to me did. I'm going

Re: [Python-ideas] install pip packages from Python prompt

Erik Bray writes: > Nope. I totally get that they don’t know what a shell or command prompt > is. THEY. NEED. TO. LEARN. I don't want to take a position on the proposal, and I agree that we should *strongly* encourage everyone to learn. But "THEY. NEED. TO. LEARN." is not obvious to me.