Re: [Python-Dev] UTF-8 Mode now also enabled by the POSIX locale
On Tue, 28 Aug 2018 at 23:02, Victor Stinner wrote: > > Hi, > > While working on test_utf8_mode on AIX (bpo-34347) and HP-UX > (bpo-34403), I noticed that FreeBSD doesn't work properly with the > POSIX locale (bpo-34527). I also noticed that my implementation of my > PEP 540 "UTF-8 Mode" doesn't respect the PEP: the UTF-8 Mode should be > enabled by the POSIX locale, not only by the C locale. > > I just modified Python 3.7 and master (future 3.8) to enable UTF-8 > Mode if the LC_CTYPE locale is "POSIX": > https://bugs.python.org/issue34527 > > I also fixed FreeBSD to support the "POSIX" locale as well (3.6, 3.7 > and master branches). > > Note: The C locale coercion (PEP 538) is only enabled if the LC_CTYPE > locale is "C". https://bugs.python.org/issue30672 is the open issue noting that it should also handle the case where POSIX isn't a simple alias for the C locale the way it is in glibc. Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] AIX and python tests
On Mon, 6 Aug 2018 at 07:03, Michael wrote: > > As I have time, I'll dig into these. > > I have a couple of PR already 'out there', which I hope someone will be > looking at when/as he/she/they have time. My time will also be intermittent. > > My next test - and I hope not too difficult - would be the test_utf8. The > test: > > FAIL: test_cmd_line (test.test_utf8_mode.UTF8ModeTests) > > fails - and I am wondering if it is as simple as AIX default mode is ISO8559-1 > and the test looks to be comparing UTF8 with the locale_default. > If that is the case, obviously this test will never succeed - asis. > > Am I understanding the test properly. > If yes, then I'll see what I can come up with for a patch to the test for AIX. > If no, I'll need some hand holding to help me understand the test UTF-8 mode relates to PEP 540, and the intent is that the default C/POSIX locale should either be coerced to a UTF-8 based one (by the PEP 538 mechanism), or else UTF-8 mode will activate, and CPython will set its *own* encoding to UTF-8, and ignore the locale one. We did need to make the PEP 538 tests AIX-aware [1] so they knew what to expect as the default encoding when locale coercion was disabled, so it's possible some further special casing will be needed in the UTF-8 mode tests as well. Cheers, Nick. [1] https://github.com/python/cpython/blob/master/Lib/test/test_c_locale_coercion.py#L40 -- Nick Coghlan | [email protected] | Brisbane, Australia ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Python 2.7 EOL date
Thanks all for clarifying! -Collin On Sat, Aug 25, 2018 at 2:50 PM Benjamin Peterson wrote: > I was operating under the optimistic assumption whatever the precise time > of 2.7's official demise would only be an amusing piece of trivia for a > world of happy Python 3 users. > > It's still to early to promise exact release dates; that will depend on > the day-to-day schedules of the release manager and binary builders circa > January 2020. A conservative assumption is that no 2.7 changes that land > after December 31 2019 will ever be released. > > We could make the last release of 2.7 in July 2020. But what does that buy > anyone? > > On Thu, Aug 23, 2018, at 11:53, Collin Anderson wrote: > > Hi All, > > > > Sorry if this has been mentioned before, but I noticed the Python 2.7 EOL > > date was recently set to Jan 1st, 2020. > > > > My understanding was Python releases get 5 years of support from their > > initial release, and Python 2.7 was extended an additional 5 years. > > > > Python 2.7 was originally released on 2010-07-03, and with an original > EOL > > of 2015-07-03. Extended 5 years, shouldn't the EOL be 2020-07-03? > > > > Also, this statement is a little unclear to me: > > > > > Specifically, 2.7 will receive bugfix support until January 1, 2020. > All > > 2.7 development work will cease in 2020. > > > > This statement makes it sound like bugfixes end on Jan 1st, but seems to > > leave open the possibility that security fixes could continue through the > > year. > > > > Thanks! > > Collin > > ___ > > Python-Dev mailing list > > [email protected] > > https://mail.python.org/mailman/listinfo/python-dev > > Unsubscribe: > > https://mail.python.org/mailman/options/python-dev/benjamin%40python.org > ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
