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?
>
>
__
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,
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:
>
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
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/
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
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/
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
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
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/
>
> 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
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
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
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
;
> 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
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
>
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
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
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/
> 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
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
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
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
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
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
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?
>
> --
>
>
__
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/
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
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?
__
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
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 :
>
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 à
%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/
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
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
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
)
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/
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
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://
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
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
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'
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
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
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
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
+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
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'
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
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
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
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 "
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
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
"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
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.
>>
>> -
>>
>>
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/
ip].
Right now, cherry-picking is very annoying but I'm not sure that
> merging would be much better with the PR requirement. I'm looking
> forward to automation!
I have a semi-automated command line script here:
https://github.com/mariatta/chic_a_cherry_picker
Please try it ou
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.
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
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/
101 - 161 of 161 matches
Mail list logo
