Re: [python-committers] Cheryl Sabella promoted as core dev

Congrats, Cheryl. Thank you for all your contributions so far. Glad to have you on the team. ᐧ On Tue, Feb 19, 2019 at 9:19 AM Victor Stinner wrote: > Hi, > > I opened a vote during 1 week to promote Cheryl Sabella. She got the > excellent score of 21 “+1” vs 0 “-1” with very encouraging commen

Re: [python-committers] Duplicate ("triplicate"?) Github notifications on Roundup

Know issue: https://github.com/python/bugs.python.org/issues/12#issuecomment-450681871 On Sun, Feb 3, 2019, 6:47 AM Antoine Pitrou > Hello, > > For some time now, Github notifications on Roundup when a PR is open > arrive three times instead of one. Is this a known issue? > > Regards > > Antoine

Re: [python-committers] REMINDER: governance vote is closing by end of this week

You have about 15 hours 12 minutes left to vote, if you haven't already. On Wed, Dec 12, 2018, 1:44 AM Łukasz Langa You have time until December 16th AoE to rank proposals and cast your > ballot. More information in PEP 8001. > > Note: reading the candidate PEPs will take you a while. Don't wait

[python-committers] Blurb-it is now available

Blurb-it is now available. For details, please see my post on discourse https://discuss.python.org/t/blurb-it-is-now-available/528 ᐧ ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committer

Re: [python-committers] A plea to stop last-minute changes to governance PEPs

As a reminder, PEP 8001 states: "November 16th, 2018 to November 30th, 2018 is the official governance PEP review period. We discourage the PEP authors from making major substantive changes during this period, although it is expected that minor tweaks may occur, as the result of this discussion p

Re: [python-committers] Timeline to vote for a governance PEP

> > Shouldn't people who were not involved in the individual creation > processes at least get two weeks to review the final work > to make up their mind before entering a voting period ? > It seems like we're completely skipping the review phase of the > regular PEP process and going straight from

Re: [python-committers] IMPORTANT: Missing Email Addresses for Governance Election Voter Roll

Bump. Some emails still missing, and we need them if you intend to vote in the upcoming CPython general election: Nov 16, 2018. Please provide your email address ASAP and before Nov 16, 2018. See this issue for more details. https://github.com/python/voters/issues/1 ᐧ On Tue, Nov 6, 2018 at 5:

Re: [python-committers] 1 week to Oct 1

Really sorry folks, but I also would like to request an extension, by one week to Oct 8. It's not because I've been slacking; I've started a five-page document (only Barry has seen it), but I still need his help before it can be ready for the public. In addition, I'm facing personal health issue. I

Re: [python-committers] Council / board (Was: 1 week to Oct 1)

My proposal is taking into consideration The PSF's mission and diversity statement. I will not remove the diversity clause from PEP 8011. To save us all trouble of discussing this particular issue, for those of you who disagree completely, and have other ideas about how you'd like Python to be gov

Re: [python-committers] Council / board (Was: 1 week to Oct 1)

> * Mariatta proposed to require to have a least one woman in that > council. > Why stop at women? My actual wording was: "not all white men", which actually means quite different from "must include one woman". I don't appreciate you jumping straight to accusing me for discrimination. Assume po

[python-committers] 1 week to Oct 1

It is now 7 days until October 1, the deadline for coming up with Python Governance PEPs. Some still relevant links: - https://www.python.org/dev/peps/pep-8000/ Python Language Governance Proposal Overview - https://www.python.org/dev/peps/pep-8001 Python Governance Voting Process - https://www.p

Re: [python-committers] I have blocked someone from the Python org

Thanks for handling it, Brett. That kind of behavior is not something we need to allow or tolerate in this community. I'm fine with banning. Mariatta ᐧ On Thu, Sep 13, 2018 at 9:18 AM Brett Cannon wrote: > Someone left > https://github.com/python/cpython/pull/9195#issuecomment-420646466 which

Re: [python-committers] Automerge bot deployed

Update to the automerge bot: It will not merge unless there is "CLA signed" label, and no "DO-NOT-MERGE" label. Again, please edit the PR title and description before adding the `🤖 automerge` label. The PR title and description will be used as the squashed commit message. Mariattaᐧ ᐧ ___

[python-committers] Automerge bot deployed

I've deployed the bot to automerge CPython pull request on the master branch. One benefit of this is you don't need to worry about replacing "#" into "GH-". To get the bot to automerge: - first edit the PR title and description, to be the commit message you want to use. - approve the PR (so it wi

[python-committers] 3 weeks to Oct 1

Friendly reminder that it is now 3 weeks until October 1, the deadline for coming up with Python Governance PEPs. Barry has started several Governance PEPs: - https://www.python.org/dev/peps/pep-8000/ Python Language Governance Proposal Overview - https://www.python.org/dev/peps/pep-8001 Python G

Re: [python-committers] Organizing an informational PEP on project governance options (was Re: Transfer of power)

Hi Nathaniel, I know you mentioned my name earlier, and thanks for thinking of me. But I'm really sorry, I just don't have the bandwidth to help out with this right now. Not sure if you've made any progress yet. Since the intention is to collect information of the various governance models out th

Re: [python-committers] Push rights for new Jython contributors

Your question is regarding push access to hg.python.org/jython, right? Seems like according to Jython's devguide , you'll need to send the SSH key to hgaccou...@python.org. But it also seems to be the same email address we used when adding committers

Re: [python-committers] Reminder of BDFL succession timeline + CFP

Thanks all for voicing your concerns and all the feedback. So far I hear people opposing the strict deadline because they're afraid it means we'll be making rush decisions for the sake of meeting deadlines. Well here are my reasonings of why I'm setting deadlines and timelines: We all know it, di

Re: [python-committers] List of all core developers

3:44 PM M.-A. Lemburg wrote: > > On 01.08.2018 23:28, Mariatta Wijaya wrote: > > > See also an open issue to revamp the Developer log: > > > https://github.com/python/devguide/issues/390 > > > > > > Someone has also said that they're working on tracking d

Re: [python-committers] Reminder of BDFL succession timeline + CFP

on before 2019, 2020, 2021, 2022, .. ? Mariatta On Wed, Aug 1, 2018 at 4:06 PM Yury Selivanov wrote: > On Wed, Aug 1, 2018 at 6:44 PM Mariatta Wijaya > wrote: > > > > > > Thank you for the responses and concerns. > > > > I do want to keep this discussion o

Re: [python-committers] Reminder of BDFL succession timeline + CFP

Thank you for the responses and concerns. I do want to keep this discussion open and ongoing, and I still think that we do need a set deadline on things. Currently any undecided PEP is stalled, and no one can pronounce on them. And we probably won't/can't promote any new core devs until we have ne

Re: [python-committers] List of all core developers

See also an open issue to revamp the Developer log: https://github.com/python/devguide/issues/390 Someone has also said that they're working on tracking down the dormant core devs, but now I can't find that email. Mariatta On Wed, Aug 1, 2018 at 2:15 PM M.-A. Lemburg wrote: > It's become fair

Re: [python-committers] Reminder of BDFL succession timeline + CFP

Thanks! AoE timezone works for me. In that case, let's use AoE instead of UTC. Mariatta On Wed, Aug 1, 2018 at 1:36 PM Thomas Wouters wrote: > > > On Wed, Aug 1, 2018 at 12:42 PM Mariatta Wijaya > wrote: > >> 2. Are people ok UTC timezone? >> > >

[python-committers] Reminder of BDFL succession timeline + CFP

Since this is like a CFP I figured we should clarify what's expected the proposal, and I also wanted to be more detailed in the timeline. *Oct 1 00:00:00 UTC:* Deadline of coming up with proposals of governance model. To be included in the proposal: - explanation and reasoning of the governance m

Re: [python-committers] Mentoring Office Hours - the idea, and a question

fixed weekly schedule works for me, but others might have more flexible schedule. Mariatta On Thu, Jun 14, 2018 at 4:58 PM Mariatta Wijaya wrote: > Thanks for starting this, Brian. > > As such, it needs a person/persons/list to contact should something arise >> in this cont

Re: [python-committers] Proposal: an explicit, time-limited moratorium on finalizing any governance decisions

As quick refresher, my proposed timeline is: Oct 1: Deadline for people to come up with proposals of governance model, candidates, and how to vote Dec 1: Deadline to choose a governance model, (and if possible, we choose the new leader(s) too) Jan 1: Deadline to choose the new leader(s), if not al

Re: [python-committers] Proposal: an explicit, time-limited moratorium on finalizing any governance decisions

On Thu, Jul 19, 2018 at 8:59 AM Brett Cannon wrote: > > I had Carol's same worry that while it's great to have a "no sooner than" > date, we also can't let this drag on and we have no "settle by" date, else > we risk losing the faith of the community in our ability to come together > and make dec

Re: [python-committers] Proposal: an explicit, time-limited moratorium on finalizing any governance decisions

+1 On Wed, Jul 18, 2018, 8:54 PM Ethan Furman wrote: > On 07/18/2018 08:45 PM, Łukasz Langa wrote:> > >> On Jul 18, 2018, at 9:36 PM, Nathaniel Smith wrote: > >> > >> I propose: no governance decisions finalized before October > >> 1, 2018. > > > > +1 but it's okay and expected that disc

Re: [python-committers] An alternative governance model

Next available is PEP lucky number 13 🙂 Mariatta On Wed, Jul 18, 2018 at 4:14 PM Barry Warsaw wrote: > On Jul 18, 2018, at 16:06, Fred Drake wrote: > > > PEP 2 is (currently) the "Procedure for Adding New Modules". Though > > superseded, recycling the PEP number seems out of character with t

Re: [python-committers] An alternative governance model

Let's be clear that we're not yet at the stage where we can vote for anything, let alone how to vote. Barry made one proposal, that's all. Last week someone suggested doing research of other governance models. We should still do that before we even start voting on anything. Mariatta On Wed, Ju

Re: [python-committers] Language moratorium

> > There is a de facto moratorium for the time being until a new governance > model is chosen. Let's not formalize anything beyond that. I agree. Mariatta On Wed, Jul 18, 2018 at 9:24 AM Łukasz Langa wrote: > There is a de facto moratorium for the time being until a new governance > model i

Re: [python-committers] Transfer of power

Guido, Thank you for all you've done for Python. It is well deserved break. I'm sad, but I like to see this as an opportunity to further improve Python and this community. My first instinct is to suggest: instead of one successor, we will have several people as the new "leaders", perhaps a co-BD

Re: [python-committers] A different way to focus discussions

PEP 572 wasn't ready for python-dev when it was moved there, > and I'm still recovering from the resulting brawl). > > On Wed, Jul 11, 2018 at 10:31 AM, Ethan Furman wrote: > >> On 07/11/2018 09:25 AM, Mariatta Wijaya wrote: >> >> Sorry to bring up this old top

Re: [python-committers] A different way to focus discussions

Sorry to bring up this old topic. I'm trying to decide how to handle discussions for PEP 581, and I'm open to try out new things :) Are we all still content with posting to python-dev? I was thinking in addition to a thread in python-dev, I want to allow discussions to take place in zulip, under a

Re: [python-committers] Mentoring Office Hours - the idea, and a question

Thanks for starting this, Brian. As such, it needs a person/persons/list to contact should something arise > in this context that needs to be handled. What/who should that be? * Suggestion 2: Create some new list with a few key people on it. > * Suggestion 3: List some direct names. Who? I pe

Re: [python-committers] Turning off AppVeyor as required

> > miss-islington currently ignores VSTS status No it does not yet ignore VSTS status. If VSTS status failed, it will not automerge. Mariatta ᐧ ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/p

Re: [python-committers] Comments on moving issues to GitHub

> > "Old and languishing issues should just be closed / ignored" > I disagree with doing this blindly, and I would be mightily annoyed if > someone did so with IDLE issues and hide valuable ideas and code. Since you are IDLE's maintainer, I'll also be annoyed if other people except yourself (or o

Re: [python-committers] Comments on moving issues to GitHub

Yup, the "mystery" was just for fun 😛 There is no secret. I've been thinking that we should start using GitHub issues instead of the b.p.o. I realized not everyone was able to get to the language summit, and I fully intended to update python-committers with this idea. I just haven't been reading t

Re: [python-committers] Proposing Mark Shannon to be a core developer

Part of the new core dev initiation should be watching this talk, titled "What is a Python Core Developer?" https://youtu.be/hhj7eb6TrtI On Tue, May 15, 2018, 11:35 AM Guido van Rossum wrote: > Let's stop the email barrage, Mark is in. Can someone tell Mark what to do? > > __

Re: [python-committers] Orphaned backports

To help with this, miss-islington will now assign the PR where backport had failed to the core dev who merged the original PR. Mariatta On Tue, Apr 24, 2018 at 8:57 AM, Brett Cannon wrote: > > > On Tue, 24 Apr 2018 at 02:59 Serhiy Storchaka wrote: > >> 23.04.18 19:47, Brett Cannon пише: >> >>

Re: [python-committers] Wanting to merge my first PR under github - a bit of advice

Some steps were written here: https://devguide.python.org/gitbootcamp/#accepting-and-merging-a-pull-request And the section right after explains the backport. I guess it needs reorganizing. Top posted from my phone while literally on a beach. On Wed, Mar 21, 2018, 7:57 AM Paul Moore wrote: >

Re: [python-committers] Save the date: Core developer sprints

Thanks for organizing! I should be able to attend for the whole week this time :) Looking forward to it. Mariatta Wijaya ᐧ ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code

Re: [python-committers] Issues with hundreds of commits being opened and closed -- what's going on?

alid. Ignore it" ? Mariatta Wijaya ᐧ ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Auto-merge the backport PR with one core dev approval and all passing CI

This is now done! miss-islington has been promoted as committer ;) If you approve the PR and all CI passed, miss-islington will merge it. Example: https://github.com/python/cpython/pull/5547#event-1468940344 Enjoy! Mariatta Wijaya ᐧ ___ python

Re: [python-committers] cherry picking, miss islington, and generated files

e expected to be different for each PR. So, maybe we trust the CI a little bit more now when it comes to checking if regenerated files are needed :) Mariatta Wijaya ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] cherry picking, miss islington, and generated files

Maybe we should just do a diff if https://github.com/python/ cpython/pull/5498 and https://github.com/python/cpython/pull/5503 <https://github.com/python/cpython/pull/5503/files> are identical.. Mariatta Wijaya ___ python-committers mailing list

Re: [python-committers] Auto-merge the backport PR with one core dev approval and all passing CI

On Mon, Feb 5, 2018 at 9:28 AM, Senthil Kumaran wrote: > I like to seek one clarification. > > I know git has author as well as committer. I am assuming that even if > miss-islington backports the PR, the author'ship of the patch is still > preserved. > > Is that correct? > > > Thanks, Senthil. C

[python-committers] Auto-merge the backport PR with one core dev approval and all passing CI

about all that? Thanks. Mariatta Wijaya ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] cherry picking, miss islington, and generated files

> > We already have Travis checking 'make regen-all' and 'make clinic' > (assuming it's working correctly). The CI in https://github.com/python/cpython/pull/5498 were all passing, but I think we expected it to fail? In the end Barry regenerated th

Re: [python-committers] cherry picking, miss islington, and generated files

Thanks :) I found the related thread in core mentorship mailing list: https://mail.python.org/mm3/archives/list/core-mentors...@python.org/thread/CNK7EWWZTDIRID7MTWLTWXU4H7IH3UIE/ Guido and Victor answered, I guess I got distracted with other things and forgot to do any sort of follow up :P If I

Re: [python-committers] cherry picking, miss islington, and generated files

Sure, I sort of asked this in the past: what are the generated files, how to identify them, is there a pattern? I need to dig up that thread and find out if anyone answered. It's been a while :) Usually there would be conflict in backport though. It was suggested that cherry-picker can regenerate

Re: [python-committers] [IMPORTANT] post 3.7.0b1 development now open

branch first. So master -> 3.7, then master -> 3.6, and master -> 2.7. It does not backport from 3.7 -> 3.6. When doing it manually yourself, you should be able to backport from master -> 3.6 first and then master -> 3.7, it doe

Re: [python-committers] I created the "needs backport to 3.7" labelon GitHub

; > Top-posted from my Windows phone > > > > *From: *Alex Gaynor > *Sent: *Thursday, February 1, 2018 10:44 > *To: *Mariatta Wijaya > *Cc: *core-workflow ; python-committers > > *Subject: *Re: [python-committers] I created the "needs backport to 3.7" > la

Re: [python-committers] I created the "needs backport to 3.7" label on GitHub

I'm not sure. Maybe the release managers know? There is PEP 101.. On Jan 31, 2018 6:43 PM, "Alex Gaynor" wrote: > Is there documentation somewhere on "how to create a release branch" that > we should add "creating a label" step to? > > Alex >

[python-committers] I created the "needs backport to 3.7" label on GitHub

I noticed that there is a 3.7 branch now. So you can use this label if you want miss-islington to backport a PR to 3.7. ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Cond

Re: [python-committers] [core-workflow] Adding "Co-authored-by" in commit message.

No prob :) I've also updated cherry_picker and miss-islington, so now `Co-authored-by` is added automatically in backport PRs. Mariatta Wijaya On Mon, Jan 29, 2018 at 5:37 PM, Eric Snow wrote: > On Mon, Jan 29, 2018 at 4:32 PM, Mariatta Wijaya > wrote: > > I suggest we

[python-committers] Adding "Co-authored-by" in commit message.

r will add the "Co-authored-by:" automatically. Mariatta Wijaya ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] trivial tag on GitHub?

> So when the original PR didn't have a news entry, what should I have seen > to alert me to that? If a news entry is missing from the PR, the CI check at the bottom of the PR will fail. You should see the following: bedevere/news -- No news entry in Misc/NEWS.d/next/ or "skip news" label found

Re: [python-committers] AppVeyor is now required to pass on PRs

lly > once CI tests pass ;-) You should have filed a feature request! :D To make it happen, I'll need miss-islington be promoted and given write access to CPython. Currently miss-islington can't merge. [1] https://mail.python.org/pipermail/python-dev/2018-Janu

Re: [python-committers] AppVeyor is now required to pass on PRs

l be useful to do that on other PRs too. (yes I'm aware GitLab does this but we are on GitHub) Mariatta Wijaya ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Condu

Re: [python-committers] Mentoring Julien Palard (core), Cheryl Sabella (bug) and Sanyam Khurana (bug)

I think questions about triaging can be asked in the regular core-mentorship as those are useful for all contributors and core devs. On Dec 9, 2017 10:23 AM, "Carol Willing" wrote: > > > On Dec 9, 2017, at 11:58 AM, Brett Cannon wrote: > > I have a subscription request to python-committers from

Re: [python-committers] Sanyam Khurana has been promoted to get bug triage permission

Congrats Sanyam! Thanks for your continued contributions :) Mariatta Wijaya On Wed, Dec 6, 2017 at 3:25 PM, Senthil Kumaran wrote: > Congratulations, and Welcome Sanyam!. > > Thank you, and keep up with your good work. > > > > On Wed, Dec 6, 2017 at 1:43 PM, Victor Stin

Re: [python-committers] Promote Julien Palard as core developer

Agree. +1! Mariatta Wijaya On Thu, Dec 7, 2017 at 8:29 AM, Ethan Furman wrote: > On 12/06/2017 04:48 PM, Victor Stinner wrote: > > I propose to promote Julien Palard as a core developer. >> > > I know that Julien doesn't have the typical profile of core >> devel

Re: [python-committers] Cheryl Sabella was promoted to get bug triage permission

Not dumb question. But I don't think Cheryl is on this list. not yet ;) On Dec 6, 2017 10:25 AM, "Ethan Furman" wrote: > On 12/06/2017 09:43 AM, Victor Stinner wrote: > > Congrats Cheryl! >> > > Possibly a dumb question, but is Cheryl on this list? > > -- > > __

Re: [python-committers] Adding Ivan Levkivskyi as a core committer

Welcome to the team, Ivan! Mariatta Wijaya ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Cheryl Sabella was promoted to get bug triage permission

Congrats Cheryl!! Thanks for your continued contributions! On Dec 6, 2017 9:43 AM, "Victor Stinner" wrote: Hi, To recognize the good contributions of Cheryl Sabella, I gave her the bug triage permission on bugs.python.org. (In practice, Ezio gave her the permission.) In the past, such "promo

Re: [python-committers] Adding Ivan Levkivskyi as a core committer

Please add Ivan to the Developer Log in Dev Guide, and he should subscribe to python-committers mailing list :) On Dec 6, 2017 8:44 AM, "Guido van Rossum" wrote: I think I figured it out -- I invited him to the python org on GitHub. Anything else? __

Re: [python-committers] Requesting reviews

The windows team is notified because the PR includes changes to PCBuild/* Mariatta Wijaya On Fri, Oct 6, 2017 at 8:51 AM, Paul Moore wrote: > Hmm, as an example, #2858, which seems to be about the AST (which I'm > not familiar with). I don't particularly want to single this ou

Re: [python-committers] Hacktoberfest

One hacktoberfest issue closed! https://github.com/python/core-workflow/issues/164 Thanks to Berker who reviewed and merged their PR quickly :) Mariatta Wijaya On Thu, Sep 28, 2017 at 2:39 PM, Victor Stinner wrote: > Hi, > > 2017-09-28 18:21 GMT+02:00 Mariatta Wijaya : >

Re: [python-committers] Hacktoberfest

the 'help wanted' labels already (see above link) and this core workflow issue which is supposed to be straightforward https://github.com/python/core-workflow/issues/164 Mariatta Wijaya Mariatta Wijaya On Thu, Sep 28, 2017 at 10:04 AM, Antoine Pitrou wrote: > > Le 28/09/2017 à

[python-committers] Hacktoberfest

%3Aissue&type=Issues Mariatta Wijaya ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Can I get access to CPython's GitHub Webhook events?

t sure who in here can give me such access.. The webhook info is located in https://github.com/python/cpython/settings/hooks and to me this is a 404 right now. Thanks :) Mariatta Wijaya ___ python-committers mailing list python-committers@python

Re: [python-committers] Cherry picker bot deployed in CPython repo

also trigger the backport. Don't want PR to be backported by a bot? Close the backport PR made by Miss Islington and make your own backport PR. Thanks! Mariatta Wijaya On Tue, Sep 5, 2017 at 6:10 PM, Mariatta Wijaya wrote: > Hi, > > The che

[python-committers] Cherry picker bot deployed in CPython repo

The Holy Grail. miss-islington has not signed the CLA! = A core dev can ignore the warning and merge the PR anyway. Thanks! Mariatta Wijaya ___ python-committers mailing list python-committers@python.org https://mail

Re: [python-committers] UPDATE 1: Core sprint 2017 - Sep 4 - Sep 9, Menlo Park, California

) Looking forward to sprint with y'all in a few weeks. Thanks. Mariatta Wijaya ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] GitHub: remove the "needs backport to 3.5" label?

Just catching up with emails. +1 to removing the label. On Aug 11, 2017 12:04 PM, "Brett Cannon" wrote: > No one has said anything, so I will delete the label sometime today. > > On Wed, 9 Aug 2017 at 12:20 Brett Cannon wrote: > >> On Wed, 9 Aug 2017 at 01:55 Victor Stinner >> wrote: >> >>> H

Re: [python-committers] New workflow - some questions

e-up here: https://devguide.python.org/committing/#what-s-new- and-news-entries blurb readme: https://github.com/python/core-workflow/blob/ master/blurb/README.rst Mariatta Wijaya ___ python-committers mailing list python-committers@python.org https://

Re: [python-committers] My (positive) feedback on the new CPython workflow

ttps://github.com/python/cpython/pulls?utf8=%E2%9C%93&q=is% 3Apr%20is%3Aclosed%20is%3Aunmerged%20 I believe the reopening the PR straight-forward: click on the "Reopen pull request" button. Mariatta Wijaya On Tue, Jul 18, 2017 at 4:01 PM, Brett Cannon wrote: > > > On Tue

Re: [python-committers] link from github to bpo?

PR 2304 is merged. "View Details" still exists (scroll all the way down). When the PR is not yet merged (e.g. https://github.com/python/cpython/pull/2316), the UI looks different. Click 'Show all checks' to get the link back to bpo. Mariatta Wijaya On Wed, Jun 21, 2017

Re: [python-committers] link from github to bpo?

github.com/python/bedevere/issues/3 (I believe Brett is working on it :) ) Mariatta Wijaya On Wed, Jun 21, 2017 at 9:58 AM, Ethan Furman wrote: > My apologies if this has been discussed/answered before, but is there a > link from the github side to the bpo side? For example, I'

Re: [python-committers] Bedevere now automatically removes "needs backport to *" labels

I think it's because there was no 'needs backport to 3.4' label from PR 1849, so it doesn't make the comment about 3.4 backport PR. Mariatta Wijaya On Tue, Jun 20, 2017 at 7:17 AM, Victor Stinner wrote: > Does it allow catch for 3.3 and 3.4 branches? I got notifications

[python-committers] Windows License for a core dev

Hi, During the language summit I overheard that as a core developer, I can get free Windows License. Is this true? If so, how can I get one, and will it work with VirtualBox on mac? Thanks. Mariatta Wijaya ___ python-committers mailing list python

Re: [python-committers] Travis skipping the test build

I think this PR takes care of it. https://github.com/python/ cpython/pull/1879 On May 30, 2017 4:08 PM, "Brett Cannon" wrote: > At the moment Travis is not running the test build (it's actually not even > listing it as a build). You can look at master, 3.6, or 3.5 to see that > only the docs a

Re: [python-committers] Guide to pushing to submitters' repo?

The git pr alias in the devguide assumes that you have origin and upstream remote setup, where origin is your own CPython fork, and upstream is python/CPython repo On May 25, 2017 6:27 AM, "Antoine Pitrou" wrote: Le 25/05/2017 à 15:06, Nick Coghlan a écrit : > On 25 May 2017 at 18:01, Antoine

Re: [python-committers] Proposing Carol Willing to become a core developer

+1_000_000 On May 23, 2017 11:23 AM, "Brett Cannon" wrote: > While at the PyCon US sprints the idea came up of offering Carol Willing > developer privileges. Everyone at the table -- about 6 of us -- liked the > idea and Carol also said she would happy to become a core dev, so I'm > officially p

Re: [python-committers] Feedback on the new CPython workflow

what do you mean by tracking backports at bpo? We already have the `needs backport` status in bpo. Mariatta Wijaya On Wed, May 17, 2017 at 3:59 PM, R. David Murray wrote: > On Wed, 17 May 2017 11:35:29 -0700, Mariatta Wijaya < > mariatta.wij...@gmail.com> wrote: > > It'

Re: [python-committers] Feedback on the new CPython workflow

the bpo number. It's possible, but remember not all PRs have bpo-issue, eg those with trivial label. In that case, what should the backport branch be? So we might end up with two backport branch name patterns, eg `backport-bpo--` and `backport-sha1` for the trivial PRs ? Thanks :) Mar

Re: [python-committers] Sphinx 1.6.1 is causing Travis to fail

It passes now : https://github.com/python/cpython/pull/1612 Ok to merge? Mariatta Wijaya On Tue, May 16, 2017 at 10:31 AM, Brett Cannon wrote: > Looks like they added some new warnings that are causing the docs build to > fail (e.g. https://travis-ci.org/python/cpython/jobs/2329032

Re: [python-committers] Proposal for procedures regarding CoC actions

core-dev contributor report such behavior? Mariatta Wijaya On Thu, May 4, 2017 at 6:53 AM, Nick Coghlan wrote: > On 4 May 2017 at 06:10, Guido van Rossum wrote: > > Two ex-board members disagree. I have to side with Brian; the PSF board > > should have minimal say in how the dev

Re: [python-committers] Proposal for procedures regarding CoC actions

to make sure that we are taking some actions going forward. Mariatta Wijaya On Sun, Apr 2, 2017 at 8:04 PM, Nick Coghlan wrote: > On 3 April 2017 at 04:08, Brett Cannon wrote: > > On Sun, 2 Apr 2017 at 04:34 Paul Moore wrote: > >> As a result, the public perception of a "

[python-committers] cherry_picker.py updated

ython/core-workflow/issues/45 Lastly, I added --status option, which will just perform `git status` for the cpython directory. Thanks :) Mariatta Wijaya ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/lis

Re: [python-committers] [Core-mentorship] Regarding reviewing test cases written for tabnanny module

o, maybe you can try these instructions: http://cpython-devguide. readthedocs.io/gitbootcamp.html#editing-a-pull-request-prior-to-merging Mariatta Wijaya On Tue, Apr 11, 2017 at 11:30 AM, Terry Reedy wrote: > On 4/11/2017 1:21 PM, Donald Stufft wrote: > >> >> On

Re: [python-committers] [Core-mentorship] Regarding reviewing test cases written for tabnanny module

"View Changes" doesn't work when commits in PR were squashed, which seems to be the case in https://github.com/python/cpython/pull/851 I wonder if there is a way to unsquash the commits? Will it help with reviewing this PR? Mariatta Wijaya On Tue, Apr 11, 2017 at 2:55 AM, Donal

Re: [python-committers] Deprecation Policy PEP Thread

turn up anything. Mariatta Wijaya On Sun, Apr 9, 2017 at 9:20 PM, Terry Reedy wrote: > On 4/9/2017 3:09 PM, Senthil Kumaran wrote: > >> I was looking for our Deprecation Policy and stumbled on this thread >> from January 2016. >> >> - >> >>

[python-committers] cherry_picker.py is now in core-workflow repo

soon that adds a --dry-run option, which I look forward to :) Mariatta Wijaya ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] 4 weeks with the new workflow: what needs changing?

el%3A%22needs%20backport%20to%203.6%22%20is%3Amerged%20 Overall, I'm positive on the move. Thanks for continuing to shepherd > the migration, Brett! +1.Thanks! Mariatta Wijaya On Sat, Mar 11, 2017 at 8:05 AM, Donald Stufft wrote: > > On Mar 11, 2017, at 3:03 AM, Zachary Ware

Re: [python-committers] REMINDER: GitHub migration is scheduled for today

So exciting! Good luck and thanks for all the hard work! On Feb 10, 2017 7:56 AM, "Brett Cannon" wrote: > Assuming you can't commit to Mercurial anymore and the next email from me > will either be an introduction email to our new workflow or me apologizing > for something going horribly wrong.

Re: [python-committers] New team member intro

Thanks Senthil :) I'm in Vancouver, Canada. so it's Pacific Time / GMT - 8 Mariatta Wijaya On Mon, Jan 30, 2017 at 3:16 PM, Senthil Kumaran wrote: > Welcome again, Mariatta. Which timezone do you reside in? > > Good luck! > > > On Mon, Jan 30, 2017 at 3:10 PM, Mari

[python-committers] New team member intro

ymond, Guido, thank you again for taking me under your wing. Mariatta Wijaya ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/