Re: [Python-Dev] Exact date of Python 2 EOL?

: On Thu, 2017-03-23 at 21:08 -0300, Joao S. O. Bueno wrote: > In Python 2, 2/8 is just 0. 27/7 is 3 in Python 2, and between 3.8 and 3.9 in Python 3 (which is probably about where 3.x will be).  -[]z. ___ Python-Dev mailing list Python-Dev@python.org

Re: [Python-Dev] Exact date of Python 2 EOL?

Le 23 mars 2017 19:56, "Terry Reedy" a écrit : > https://docs.python.org/devguide/#status-of-python-branches > says January 1st, 2020 Can we pick an official date? > The devguide list is effectively the official list. No one should plan on getting anything from pydev after

Re: [Python-Dev] Exact date of Python 2 EOL?

On 23 March 2017 at 19:47, Barry Warsaw wrote: > On Mar 23, 2017, at 08:02 PM, MRAB wrote: > >>If you see 2/8, is that 2 August or February 8? > > I think that's 0.25 which doesn't look like a date to me . ISO 8601 > dates please: 2020-02-08 is unambiguous. In Python 2, 2/8 is

Re: [Python-Dev] Exact date of Python 2 EOL?

On Mar 23, 2017, at 08:02 PM, MRAB wrote: >If you see 2/8, is that 2 August or February 8? I think that's 0.25 which doesn't look like a date to me . ISO 8601 dates please: 2020-02-08 is unambiguous. -Barry ___ Python-Dev mailing list

Re: [Python-Dev] 3.5 unittest does not support namespace packages for discovering

On 23 March 2017 at 20:41, Ned Batchelder wrote: >>> If unittests searches normal directly, it may walk deep into very >>> large tree containing >>> millions of directories. I don't like it. > >> That is a risk, OTOH I think the failure to do what folk expect is a >>

Re: [Python-Dev] Exact date of Python 2 EOL?

On Thu, 23 Mar 2017 09:41:11 +0100 Victor Stinner wrote: > Hi, > > I looked at the "Status of Python branches" to check if it was up to > date. It's the case, thanks :-) But it recalled me that no exact date > was decided for the official end of line of the the Python 2

Re: [Python-Dev] 3.5 unittest does not support namespace packages for discovering

On 3/23/17 3:14 PM, Robert Collins wrote: > On 24 March 2017 at 04:59, INADA Naoki wrote: >> And this issue is relating to it too: http://bugs.python.org/issue29716 >> >> In short, "namespace package" is for make it possible to `pip install >> foo_bar foo_baz`, >> when

Re: [Python-Dev] Exact date of Python 2 EOL?

On 2017-03-23 16:37, Brian Curtin wrote: On Thu, Mar 23, 2017 at 12:19 PM, Barry Warsaw wrote: On Mar 23, 2017, at 09:41 AM, Victor Stinner wrote: Can we pick an official date? Benjamin should pick the date and update PEP 373. Not to start a bikeshed (calendarshed?),

Re: [Python-Dev] 3.5 unittest does not support namespace packages for discovering

On 24 March 2017 at 04:59, INADA Naoki wrote: > And this issue is relating to it too: http://bugs.python.org/issue29716 > > In short, "namespace package" is for make it possible to `pip install > foo_bar foo_baz`, > when foo_bar provides `foo.bar` and foo_baz provides

Re: [Python-Dev] Exact date of Python 2 EOL?

On 3/23/2017 4:41 AM, Victor Stinner wrote: Hi, I looked at the "Status of Python branches" to check if it was up to date. It's the case, thanks :-) But it recalled me that no exact date was decided for the official end of line of the the Python 2 branch (2.7 EOL). >

Re: [Python-Dev] Exact date of Python 2 EOL?

On Mar 23, 2017, at 04:41, Victor Stinner wrote: > By the way, maybe we can also start to list vendors (Linux vendors?) > who plan to offer commercial extended support? IMO, we should definitely not list 2.7 vendor and their plans on a python.org web page. One, it

Re: [Python-Dev] Exact date of Python 2 EOL?

On 23Mar2017 0937, Brian Curtin wrote: On Thu, Mar 23, 2017 at 12:19 PM, Barry Warsaw wrote: On Mar 23, 2017, at 09:41 AM, Victor Stinner wrote: Can we pick an official date? Benjamin should pick the date and update PEP 373. Not to start a bikeshed (calendarshed?), but

Re: [Python-Dev] Exact date of Python 2 EOL?

On Thu, Mar 23, 2017 at 12:19 PM, Barry Warsaw wrote: > On Mar 23, 2017, at 09:41 AM, Victor Stinner wrote: > >>Can we pick an official date? > > Benjamin should pick the date and update PEP 373. Not to start a bikeshed (calendarshed?), but how about 8 February 2020, or 2/8 as

Re: [Python-Dev] Exact date of Python 2 EOL?

On Mar 23, 2017, at 09:41 AM, Victor Stinner wrote: >Can we pick an official date? Benjamin should pick the date and update PEP 373. >Ubuntu 12.04 reached its end of life after 5 years, but it seems like >Canonical also starts to offer extended support to customers:

Re: [Python-Dev] Exact date of Python 2 EOL?

By the way, maybe we can also start to list vendors (Linux vendors?) who plan to offer commercial extended ... Delurking ever so briefly... Might be worthwhile to list published vendor EOL dates no matter if they are before or after the 2020 EOL date. Different Linux distros have different

Re: [Python-Dev] 3.5 unittest does not support namespace packages for discovering

And this issue is relating to it too: http://bugs.python.org/issue29716 In short, "namespace package" is for make it possible to `pip install foo_bar foo_baz`, when foo_bar provides `foo.bar` and foo_baz provides `foo.baz` package. (foo is namespace package). If unittests searches normal

[Python-Dev] 3.5 unittest does not support namespace packages for discovering

Hello. I have following layout: \---tests | test_module.py | __init__.py When I launch "python.exe" -m unittest discover -t . -s tests" it works perfectly. But when I remove " __init__.py" it says Start directory is not importable: "tests'" ``loader.py``: if start_dir !=

[Python-Dev] Exact date of Python 2 EOL?

Hi, I looked at the "Status of Python branches" to check if it was up to date. It's the case, thanks :-) But it recalled me that no exact date was decided for the official end of line of the the Python 2 branch (2.7 EOL). https://docs.python.org/devguide/#status-of-python-branches says January