Re: [Python-Dev] [python-committers] New workflow change: Welcome to blurb

2017-06-24 6:24 GMT+03:00 Larry Hastings : > One minor but ongoing problem we've had in CPython core development has been > the mess of updating Misc/NEWS. Day-to-day developers may have a conflict > if they lose a push race, which means a little editing. You'll have a > similar, if slightly wors

Re: [Python-Dev] Appveyor builds fail on Windows for 3.6 backports.

On 24 June 2017 at 06:14, Steve Dower wrote: > We could improve life for everyone even more if we built Tcl/Tk once per > update and made it a binary dependency. Nobody is updating our version of it > regularly anyway, and this would significantly improve build time in CI. I'm pretty sure the *ni

Re: [Python-Dev] New workflow change: Welcome to blurb

On 24 June 2017 at 14:01, Craig Rodrigues wrote: > On Fri, Jun 23, 2017 at 8:24 PM, Larry Hastings wrote: >> >> >> >> We've been talking about addressing this for years. Fixing this was one >> of the goals of the new workflow. And finally, as of right now, the future >> is here. Ladies and gen

Re: [Python-Dev] [python-committers] New workflow change: Welcome to blurb

On 24 June 2017 at 13:24, Larry Hastings wrote: > > > One minor but ongoing problem we've had in CPython core development has been > the mess of updating Misc/NEWS. Day-to-day developers may have a conflict > if they lose a push race, which means a little editing. You'll have a > similar, if sli

Re: [Python-Dev] New workflow change: Welcome to blurb

One quick heads up – the NEWS file is included in the docs build (if not in the html docs, certainly in the CHM for Windows releases). You may have to do some extra work to keep that from breaking when you remove it. We might also include it as plain text in the installers, I forget right now.

Re: [Python-Dev] New workflow change: Welcome to blurb

On Fri, Jun 23, 2017 at 8:24 PM, Larry Hastings wrote: > > > We've been talking about addressing this for years. Fixing this was one > of the goals of the new workflow. And finally, as of right now, the future > is here. Ladies and gentlemen, I present: blurb. > > https://github.com/python/cor

[Python-Dev] New workflow change: Welcome to blurb

One minor but ongoing problem we've had in CPython core development has been the mess of updating Misc/NEWS. Day-to-day developers may have a conflict if they lose a push race, which means a little editing. You'll have a similar, if slightly worse, problem when cherry-picking a fix between

Re: [Python-Dev] Appveyor builds fail on Windows for 3.6 backports.

On 6/23/2017 4:14 PM, Steve Dower wrote: We could improve life for everyone even more if we built Tcl/Tk once per update and made it a binary dependency. Nobody is updating our version of it regularly anyway, and this would significantly improve build time in CI. On Windows, I believe compili

Re: [Python-Dev] Appveyor builds fail on Windows for 3.6 backports.

We could improve life for everyone even more if we built Tcl/Tk once per update and made it a binary dependency. Nobody is updating our version of it regularly anyway, and this would significantly improve build time in CI. The externals script probably just needs some retry logic. Doesn’t look l

Re: [Python-Dev] Appveyor builds fail on Windows for 3.6 backports.

On 6/23/2017 2:24 PM, Zachary Ware wrote: On Fri, Jun 23, 2017 at 11:36 AM, Terry Reedy wrote: Example: appveyor passes for https://github.com/python/cpython/pull/2335#discussion_r123724857 Appveyor build fails for 3.6 backport https://github.com/python/cpython/pull/2359 https://ci.appveyor.co

Re: [Python-Dev] Appveyor builds fail on Windows for 3.6 backports.

On Fri, Jun 23, 2017 at 11:36 AM, Terry Reedy wrote: > Example: appveyor passes for > https://github.com/python/cpython/pull/2335#discussion_r123724857 > > Appveyor build fails for 3.6 backport > https://github.com/python/cpython/pull/2359 > https://ci.appveyor.com/project/python/cpython/build/3.6

Re: [Python-Dev] [Core-mentorship] C version of weakrefset.py.

On Thu, 22 Jun 2017 at 16:26 Bhavishya wrote: > Also I saw your conversation with "Brett Cannon" on lazy-loading some > modules at startup, and also doing so using ModuleProxy(also several > implementations that exist like importlib's Lazyloader >

[Python-Dev] Appveyor builds fail on Windows for 3.6 backports.

Example: appveyor passes for https://github.com/python/cpython/pull/2335#discussion_r123724857 Appveyor build fails for 3.6 backport https://github.com/python/cpython/pull/2359 https://ci.appveyor.com/project/python/cpython/build/3.6.1+.3673 The compile and build errors have nothing to do with th

[Python-Dev] Summary of Python tracker Issues

ACTIVITY SUMMARY (2017-06-16 - 2017-06-23) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open6026 ( -8) closed 36470 (+65) total 42496 (+57) Open issues wit

Re: [Python-Dev] PEP 544: Protocols - second round

What I try to do is a new workflow: - 'declare' types of method parameters by usage in a unit test. Therefore ensure the interface is obeyed inside.- publish the used types via hints to help callers of the method. -Do express all hints in test code. Do not insert any hints manually. Any type use

Re: [Python-Dev] [python-committers] Proposed release schedule for Python 3.5.4

2017-06-23 15:19 GMT+02:00 Larry Hastings : > Do you need write access to the branch in order to get Travis CI working? As soon as someone reviews my proposed 3.4 patches, no :-) I will work on a PR. Victor ___ Python-Dev mailing list Python-Dev@python.

Re: [Python-Dev] Proposed release schedule for Python 3.5.4

On 06/21/2017 07:58 PM, Larry Hastings wrote: 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 schedul

Re: [Python-Dev] [python-committers] Proposed release schedule for Python 3.5.4

On 06/23/2017 01:55 AM, Victor Stinner wrote: Larry: would you be ok to turn this protection off on the 3.4 branch? Or would you feel more confortable if only a few people would be allowed to push to the 3.4 branch, so add me a whitelist group or something like that? Actually I kind of like the

Re: [Python-Dev] [python-committers] Proposed release schedule for Python 3.5.4

2017-06-22 17:56 GMT+02:00 Brett Cannon : > On Thu, 22 Jun 2017 at 02:32 Larry Hastings wrote: >> Seriously, though, I was mostly hoping other people would handle the >> security stuff and just keep me informed. If I'm the only one permitted to >> accept PRs into 3.4 (and soon 3.5), okay, I can w