Hi,
Python 3.5 entered security fix only mode. Should we now remove the
"needs backport to 3.5" label? Other security only branches don't have
this label neither (3.3 and 3.4).
Victor
Hello fellow committers!
I'm organizing another core sprint this year to make Python 3.7 the best release possible.
WHY:
1. Community. The sprints at the end of PyCon are great but they mostly get the same people in the room year after year. Many of the most active contributors never attend conferences. My goal with this sprint is to bring together many core devs who rarely if ever meet!
2. Focus. When we have sprints at the end of a conference, many of us are pretty tired and less productive than we could have been without the late dinners, endless hallway sessions, and so on. Some of the sprinters are preoccupied with tutoring newcomers. This sprint won't be after a major conference, and it's only for seasoned CPython core devs--so get to work!
3. Communication. There are tremendous benefits to getting everyone together in one big room. Conversations that drag on on python-dev can be solved quickly in person. Even contentious debates become faster, easier, and more civil. And meeting face-to-face helps us all feel more connected to our community.
WHY THE BAY AREA: We have a large population of core contributors here. Also, I can arrange for Facebook to provide us a "war room" for the whole week, with full access to the campus during the sprints. That includes free food for breakfast, lunch, dinner, and snacks, compatible with almost any dietary restrictions.
WHY EARLY SEPTEMBER: It's almost impossible to find a time that doesn't overlap with a PyCon. This week worked well last year so we're redoing it that way. Monday September 4 is Labor Day in the US, which may make it easier for employees of US companies to attend, as they'd only be taking off four days instead of five.
HOW LONG: A full week Monday, Sep 4 to Friday, Sep 8 evening. You can check into your hotel the day before the sprint (Sunday, Sep 3) and check out the day after (Saturday, Sep 9).
HOW BIG: No fewer than 10, no more than 20. More than 20 people would be great but it'd be hard for me to organize a sprint that big.
WHO PAYS: The venue, hotels, and food are provided by Facebook. I'm working on getting flight reimbursements. Last year they were provided by the Python Software Foundation. Anybody is free to waive their reimbursement.
PLEASE REPLY: If you're interested in attending and have the commit bit on GitHub's python/cpython, fill out this Google Form:
https://goo.gl/forms/MzrNtRe0NAmzvGwF2 <https://goo.gl/forms/MzrNtRe0NAmzvGwF2>
DISCLAIMER: I'd like to be able to host everybody. However, if I receive more than 20 applications, this is not going to be possible. In this case, the following will happen:
1. I will look at your current level of involvement in CPython development. This includes metrics like commits / PRs, activity on the bug tracker and python-dev, special role (release manager, infrastructure dev, etc.).
2. I will look at your sprint plan and ability to participate in the entire sprint (per answers to the questions above).
3. I will gather all this data and leave the final decision to our Benevolent Dictator (who is also attending the sprint). This is one of those occasions where having a dictator is useful.
DON'T WAIT: September is closer than you think! Please let me know as soon as possible so we can start setting up the event. I'm going to close the sign-up form on June 23rd.
Organizational-ly yours,
Ł
Vice-Minister of Silly Sprints
I don't know if this is specific to my pull request but on PR #2558 I'm seeing:
fatal: Invalid symmetric difference expression 49f6449ef4b81537c19b82329caaf60596c516c2...7b634956246bc6112a16ba11ff9f721342e750e6
<>Only docs were updated, stopping build process.
The build is subsequently marked as green. This is invalid, there were code changes in the pull request.
- Ł
Yeah, looks like that was it. Thanks.
Paul
On 20 August 2017 at 22:23, Zachary Ware <zachary.ware(a)gmail.com> wrote:
> Being added to the team caused me to be 'watching' the repo again, even
> though I'd previously 'unwatched'. Paul, you may need to unwatch again as
> well.
>
> --
> Zach
> (On a phone)
>
> On Aug 20, 2017 09:28, "Steve Dower" <steve.dower(a)python.org> wrote:
>>
>> We created a Windows team on github and signed it up for notifications of
>> changes to PC, PCBuild and the installer folders. If the notifications are
>> for files in those folders, that’ll be it. (Though I haven’t noticed any
>> similar increase, so it may be something else.)
>>
>>
>>
>> Feel free to remove yourself from the team if it looks like that’ll help.
>>
>>
>>
>> Top-posted from my Windows phone
>>
>>
>>
>> From: Paul Moore
>> Sent: Sunday, August 20, 2017 6:08
>> To: python-committers
>> Subject: [python-committers] Flood of Github review mails?
>>
>>
>>
>> I've just recently (within the last week I guess) started getting a
>>
>> large number of additional mails from github. For example, I'm getting
>>
>> notifications on https://github.com/python/cpython/pull/3066 which I
>>
>> haven't commented on or been mentioned in, nor am I nosy on the
>>
>> underlying bug.
>>
>>
>>
>> What's changed to cause this to start happening, and how do I make it
>>
>> stop? I've nowhere near enough time to review all the mails I'm now
>>
>> getting, and I'd rather avoid them so I don't miss notifications that
>>
>> I *do* need to see :-(
>>
>>
>>
>> Thanks,
>>
>> Paul
>>
>> _______________________________________________
>>
>> python-committers mailing list
>>
>> python-committers(a)python.org
>>
>> https://mail.python.org/mailman/listinfo/python-committers
>>
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>>
>>
>>
>>
>> _______________________________________________
>> python-committers mailing list
>> python-committers(a)python.org
>> https://mail.python.org/mailman/listinfo/python-committers
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>>
>
I've just recently (within the last week I guess) started getting a
large number of additional mails from github. For example, I'm getting
notifications on https://github.com/python/cpython/pull/3066 which I
haven't commented on or been mentioned in, nor am I nosy on the
underlying bug.
What's changed to cause this to start happening, and how do I make it
stop? I've nowhere near enough time to review all the mails I'm now
getting, and I'd rather avoid them so I don't miss notifications that
I *do* need to see :-(
Thanks,
Paul
Last year I took the month of October off from volunteering on Python to
prevent burn-out and to just take some time to reflect. It turned out to be
a great decision as I came out of the break feeling much better about
volunteering to work on Python and what I needed to do to stay grounded (it
has even led to a new talk topic that I will be testing out at JupyterCon
and talking about for the next 12 months whenever I speak at conferences on
how to try and re-adjust everyone's view of open source to prevent
burn-out and frustration for everyone involved).
Since I was so happy with the result last year I'm repeating it again this
year, but in September (it overlaps with my vacation so it actually scales
back the amount of absolute time I take off). Just like last year this
means I'm only looking at critical Python emails weekly and completely
ignoring non-critical ones until the month is out. I will continue to work
on Python in September, but only on work time and not personal time so it
will be highly constrained to pretty much only working hours on Fridays
when I typically do my paid open source thanks to Microsoft.
The reason I'm making this announcement now is I know this coincides with
the core sprint next month so if anyone has anything they want to ask me
before that, now is the time. Workflow stuff should all have a bus factor
greater than 1, so if you can think of something that doesn't then please
let me know so I can fix it.
Hello,
One of my PR builds got an AppVeyor failure in test_asyncgen
and I really doubt it is due to the PR itself:
https://ci.appveyor.com/project/python/cpython/build/3.7.0a0.5366#L682
======================================================================
FAIL: test_async_gen_asyncio_gc_aclose_09 (test.test_asyncgen.AsyncGenAsyncioTest)
----------------------------------------------------------------------
Traceback (most recent call last):
File "C:\projects\cpython\lib\test\test_asyncgen.py", line 627, in test_async_gen_asyncio_gc_aclose_09
self.assertEqual(DONE, 1)
AssertionError: 0 != 1
Regards
Antoine.
Now that all branches support blurb, I have added a status check for a news
entry. If a PR doesn't require a news entry then simply set the "skip news"
label and the status check will then pass. When there is no news entry the
Details link of the failing status check points to the appropriate part of
the devguide so hopefully some contributors will self-discover the need for
a news entry and create the appropriate file without being prompted for it.
I'm going to wait a little while -- probably end of the week -- to verify I
didn't botch the code before I make this a required status check like with
the issue number check (I've already had to push out an emergency fix once
already today so it has validated that waiting is good :) .
And with this I am taking a break from coding new workflow tooling for a
little while and switching to feature work for Python 3.7. :)
On behalf of the Python development community and the Python 3.4 release
team, I'm pleased to announce the availability of Python 3.4.7.
Python 3.4 is now in "security fixes only" mode. This is the final
stage of support for Python 3.4. Python 3.4 now only receives security
fixes, not bug fixes, and Python 3.4 releases are source code only--no
more official binary installers will be produced.
You can find Python 3.4.7 here:
https://www.python.org/downloads/release/python-347/
Happy Pythoning,
//arry/
