[Python-Dev] test_sax and test_random fail on Python 3.6.2rc1 on Windows
Hi, The end-of-line hell is not over, test_sax and test_random tests are still failing if you install Python 3.6.2rc1 on Windows: http://bugs.python.org/issue27425#msg296519 These tests rely on files in Lib/test/. The end-of-line of these files is controlled by .gitattributes, but it seems like the Windows installer changed the end-of-line or the file were not correctly created on the Git clone (.gitattributes ignored)? In my Git checkout on Windows, Lib/test/xmltestdata/test.xml.out and Lib/test/randv2_32.pck use UNIX end-of-line (\n). While it's possible to fix test_sax to translate the end-of-line, I would prefer to not have to modify test_random which opens a pickle binary file (Lib/test/randv2_32.pck). So, can someone look how the Windows installer stores and then installs these files? Victor ___ 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] test_sax and test_random fail on Python 3.6.2rc1 on Windows
I’m looking. Nobody in any of their reports has actually said what the line endings *are* in they install yet (I assume \n), and I haven’t had a chance to check yet. Do we have a minimum git version requirement? Maybe I need to update my build machine. Top-posted from my Windows phone From: Victor Stinner Sent: Wednesday, June 21, 2017 2:27 To: Python Dev; Steve Dower Subject: test_sax and test_random fail on Python 3.6.2rc1 on Windows Hi, The end-of-line hell is not over, test_sax and test_random tests are still failing if you install Python 3.6.2rc1 on Windows: http://bugs.python.org/issue27425#msg296519 These tests rely on files in Lib/test/. The end-of-line of these files is controlled by .gitattributes, but it seems like the Windows installer changed the end-of-line or the file were not correctly created on the Git clone (.gitattributes ignored)? In my Git checkout on Windows, Lib/test/xmltestdata/test.xml.out and Lib/test/randv2_32.pck use UNIX end-of-line (\n). While it's possible to fix test_sax to translate the end-of-line, I would prefer to not have to modify test_random which opens a pickle binary file (Lib/test/randv2_32.pck). So, can someone look how the Windows installer stores and then installs these files? Victor ___ 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] test_sax and test_random fail on Python 3.6.2rc1 on Windows
2017-06-21 16:10 GMT+02:00 Steve Dower : > Do we have a minimum git version requirement? Maybe I need to update my > build machine. After we added .gitattributes, we had to force a fresh Git checkout on buildbots. Otherwise, they kept the old and wrong end of line. Maybe try to move my checkout and create a new checkout? Victor ___ 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] test_sax and test_random fail on Python 3.6.2rc1 on Windows
The last release from the same checkout was fine. I’m more inclined to think something went wrong with the pull from Ned’s fork and checking out his tag. (Or the fact that it took me three goes to get to that point – my least favourite part of the git migration is git...) When I get to work I’ll clean it up and try again to see if it repros or was a random occurrence. Top-posted from my Windows phone From: Victor Stinner Sent: Wednesday, June 21, 2017 7:23 To: Steve Dower Cc: Python Dev Subject: Re: test_sax and test_random fail on Python 3.6.2rc1 on Windows 2017-06-21 16:10 GMT+02:00 Steve Dower : > Do we have a minimum git version requirement? Maybe I need to update my > build machine. After we added .gitattributes, we had to force a fresh Git checkout on buildbots. Otherwise, they kept the old and wrong end of line. Maybe try to move my checkout and create a new checkout? Victor ___ 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] test_sax and test_random fail on Python 3.6.2rc1 on Windows
Thank you Steve for looking at this issue and to work on our Windows installer :-) Victor 2017-06-21 16:31 GMT+02:00 Steve Dower : > The last release from the same checkout was fine. I’m more inclined to think > something went wrong with the pull from Ned’s fork and checking out his tag. > (Or the fact that it took me three goes to get to that point – my least > favourite part of the git migration is git...) > > > > When I get to work I’ll clean it up and try again to see if it repros or was > a random occurrence. > > > > Top-posted from my Windows phone > > > > From: Victor Stinner > Sent: Wednesday, June 21, 2017 7:23 > To: Steve Dower > Cc: Python Dev > Subject: Re: test_sax and test_random fail on Python 3.6.2rc1 on Windows > > > > 2017-06-21 16:10 GMT+02:00 Steve Dower : > >> Do we have a minimum git version requirement? Maybe I need to update my > >> build machine. > > > > After we added .gitattributes, we had to force a fresh Git checkout on > > buildbots. Otherwise, they kept the old and wrong end of line. Maybe > > try to move my checkout and create a new checkout? > > > > Victor > > ___ 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] test_sax and test_random fail on Python 3.6.2rc1 on Windows
On 21Jun2017 0736, Victor Stinner wrote: Thank you Steve for looking at this issue and to work on our Windows installer :-) No worries. So we didn't ship 3.6.2rc1 with LF line endings instead of CRLF - those are fine. These issues are due to .gitattributes changing for test data files, but those files didn't change and so the line endings in my repo didn't get updated. I've posted more details and recommendations at http://bugs.python.org/issue30716. Thanks, Steve ___ 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
[Python-Dev] https://devguide.python.org now exists
While the redirect for https://docs.python.org/devguide does not exist yet, the infrastructure team has been nice enough to set up https://devguide.python.org for us so that the devguide is served from Read the Docs. This not only will (eventually) let the infrastructure team have one less custom piece of doc infrastructure to maintain, but it means updates to the devguide will be live instantly. Plus the URL is a lot easier to remember. :) So a win-win for everyone! ___ 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
[Python-Dev] Proposed release schedule for Python 3.5.4
It's time to start planning the next 3.5 release, 3.5.4. Note that this will be the last 3.5 "bugfix" release; after 3.5.4, the 3.5 branch will only be open for security fixes. 3.5.4 will also be the last release of 3.5 with binary installers. I propose to tag and release 3.5.4 on these dates: 3.5.4rc1 tag Sat July 22 2017 release Sun July 23 2017 3.5.4 final tag Sun Aug 6 2017 release Mon Aug 7 2017 Thus rc1 would be tagged in just over four weeks. As for 3.4-- Lately I've been releasing new versions of 3.5 and 3.4 at the same time. But I'm not sure it's worth the effort to release another 3.4 right now. There have only been two (2) checkins into the 3.4 branch since 3.4.6 was released back in January: f37b0cb230069481609b0bb06891b5dd26320504 bpo-25008: Deprecate smtpd and point to aiosmtpd fa53dbdec818b0f2a0e22ca12a49d83ec948fc91 Issues #27850 and #27766: Remove 3DES from ssl default cipher list and add ChaCha20 Poly1305. The first was a documentation-only change which is already live on docs.python.org. The second changes the _DEFAULT_CIPHERS and _RESTRICTED_SERVER_CIPHERS constants in Lib/ssl.py. A reasonable change, but minor. I'm not convinced it's worth spending the time of many people in the community at large to update 3.4 just for this. If you have any feedback / concerns about this schedule, or if you think it's important that I release 3.4.7 with these minor changes, please reply here. If I don't hear anything back in a day or two I'll go ahead and make this the official schedule. Your friendly neighborhood release manager, //arry/ ___ 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] https://devguide.python.org now exists
FYI we're aware of the internal link problem and I've notified the infrastructure team about it (looks like some URL rewrite rule is misconfigured 😞). On Wed, Jun 21, 2017, 18:14 Brett Cannon, wrote: > While the redirect for https://docs.python.org/devguide does not exist > yet, the infrastructure team has been nice enough to set up > https://devguide.python.org for us so that the devguide is served from > Read the Docs. This not only will (eventually) let the infrastructure team > have one less custom piece of doc infrastructure to maintain, but it means > updates to the devguide will be live instantly. Plus the URL is a lot > easier to remember. :) > > So a win-win for everyone! > ___ 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-committers] Proposed release schedule for Python 3.5.4
2017-06-22 5:58 GMT+03:00 Larry Hastings : > There have only been two (2) checkins into the 3.4 branch since 3.4.6 was > released back in January: > > f37b0cb230069481609b0bb06891b5dd26320504 > bpo-25008: Deprecate smtpd and point to aiosmtpd > > fa53dbdec818b0f2a0e22ca12a49d83ec948fc91 > Issues #27850 and #27766: Remove 3DES from ssl > default cipher list and add ChaCha20 Poly1305. Please look also at issue30484. The PR is blocked, seems only the RM can merge it. Maybe this is a cause of small number of changes in 3.4 since moving to GitHub? https://bugs.python.org/issue30484 There were several security issues fixed recent times. Perhaps the fixes should be backported to 3.4? ___ 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
