Re: [python-committers] Date for the Language Summit?

Date is listed here. More info will be added here too. https://us.pycon.org/2019/events/language-summit/ Process will be slightly different this year. Sorry, I'm busy with PyCascades this week. Next time I'll have more time to devote to this. On Thu, Feb 21, 2019, 5:21 AM Mariatta wrote: > D

[python-committers] Reminder: Python Language Summit 2019 Signup

Just another reminder that sign up is still open for Python Language Summit (until March 21st, 2019) TL;DR: When: Wednesday, May 1, 2019, 10am–4pm Where: Huntington Convention Center, Cleveland, Ohio Apply: Attendance sign up form (before March 21, 2019)

[python-committers] Re: Fwd: Python-checkins post from webhook-mai...@python.org requires approval

This seems to be a mailman feature. Would the suggested workaround below work? https://support.tigertech.net/mailman-implicit-destination Looking at the webhook mailer repo, there doesn't seem to be any recent code change to it, other than allowing the 3.8 branch. On Sun, Jun 9, 2019, 8:56 AM

Re: [python-committers] miss-islington backport pipeline is stalled?

I'm seeing more of this today, just heads up in case you see miss-islington not working. Seems like this is a known issue with celery + kombu  https://github.com/celery/kombu/issues/1019 ᐧ On Wed, May 8, 2019 at 10:02 AM Mariatta wrote: > There was an error from Redis. I th

Re: [python-committers] miss-islington backport pipeline is stalled?

There was an error from Redis. I think this is the first time I've seen it, so I don't have any resolution on how to fix it right now.  I will look into handling the error and have miss-islington leave a comment in the PR when there is such error. log: at=info method=POST path="/"

Re: [python-committers] Azure build operations

Maybe worth implementing a `retest` command so our bots can retrigger the tests without closing PR. Jenkins has this command. ᐧ On Tue, May 21, 2019 at 8:40 PM Steve Dower wrote: > Close/reopen is still the easiest way, unfortunately. I've been bugging > the team to improve this, but other

Re: [python-committers] Merge with spurious CI failures?

If you can't merge from GitHub UI then you won't be able to do it from GitHub command line (it respects the same branch protection policy) I don't think we should merge if tests are still failing. Perhaps the test should be adjusted to handle this spurious errors? Can it be marked as "allowed

Re: [python-committers] miss-islington backport pipeline is stalled?

unhandled exceptions? > > Alex > > On Wed, May 8, 2019 at 1:02 PM Mariatta wrote: > >> There was an error from Redis. I think this is the first time I've seen >> it, so I don't have any resolution on how to fix it right now.  >> I will look into handling the error

[python-committers] Re: Cleaning up the historical list of core developers

> > Let's say someone made all of their commits from 2015-07-04 to 2015-10-04 > (and when I say "commits" I mean committing or authoring in git terms). > That means they committed over a span of less than 3 months over the entire > history of the cpython repo and that the last commit was more than

[python-committers] Announcing the new Python triage team on GitHub

We have a new Python triage team on GitHub to help improve our workflow. GitHub has a nice table that shows what a triager can or cannot do in general: https://help.github.com/en/articles/repository-permission-levels-for-an-organization#repository-access-for-each-permission-level More specific

[python-committers] PEP 581/588 RFC: Collecting feedback about GitHub Issues

(cross posting to python-committers, python-dev, core-workflow) PEP 581: Using GitHub Issues has been accepted by the steering council, but PEP 588: GitHub Issues Migration plan is still in progress. I'd like to hear from core developers as well as heavy b.p.o users, the following: 1. what

[python-committers] Re: PEP 581/588 RFC: Collecting feedback about GitHub Issues

Sorry, but please leave comments in the GitHub issue, one feature request per comment. This will allow people to give +1 reaction to your request https://github.com/python/core-workflow/issues/359 On Thu, Sep 12, 2019, 2:30 AM Steve Dower wrote: > On 11Sep2019 1117, Steven D'Aprano wrote: > >

[python-committers] Re: Possible bug in voting system ? (was: Re: Reminder to vote for the 2020 Steering Council)

Thanks Brett. Re: notifying and sending email to people who were marked as inactive by the script. We can send automated email via Zapier. Let me know how I can help with this part. On Wed, Dec 11, 2019 at 11:20 AM Brett Cannon wrote: > I want to make two quick points and then I'm bowing out

[python-committers] Re: getting old branches/releases

On Tue, Feb 11, 2020 at 3:49 PM Ethan Furman wrote: > > I'm trying to get the 3.3 and 3.4 branches so I can check my libraries > compatibility with older versions, but I do not see those branches as being > available: > > How can I get those? > > > 3.3 and 3.4 existed before the migration from

[python-committers] Re: getting old branches/releases

Great! Perhaps we should have this info in devguide. https://github.com/python/devguide/issues/572 Welcoming PR. ___ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org

[python-committers] Re: bpo email problems - Is there someone in the infra boat?

I think this is same issue as https://github.com/python/bugs.python.org/issues/38 To get in touch with infrastructure team, you can write to infrastructure-staff at python dot org On Fri, Feb 28, 2020 at 10:44 AM Antoine Pitrou wrote: > > (note - apparently the psf.org domain doesn't belong to

[python-committers] Python Language Summit at PyCon 2020

o note this year: 1) We plan to start 1 hour earlier (9AM) 2) The room will have U-shaped table layout Thanks! Mariatta & Łukasz ___ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-com

[python-committers] Re: [Python-Dev] Python Language Summit at PyCon 2020

rg/2020/events/language-summit/;. > > Either the link could be changed to " > https://us.pycon.org/2020/events/languagesummit/; or " > https://us.pycon.org/2020/events/language-summit/; could be configured to > redirect towards the correct page. > > On Tue, Jan 28,

[python-committers] Re: Python Language Summit at PyCon 2020

. Among them were maintainers and representatives from BeeWare, CircuitPython, PSF board member, PyCharm, etc. Full details at: https://us.pycon.org/2020/events/languagesummit/ On Tue, Jan 28, 2020 at 1:07 PM Mariatta wrote: > (cross posting to python-committers and python-dev) > >

[python-committers] Re: Language Summit

Antonio Cuni has published his slides: https://speakerdeck.com/antocuni/hpy-a-future-proof-way-of-extending-python On Wed, Apr 15, 2020 at 5:46 PM joannah nanjekye wrote: > > I am reliant on summaries and anyone attending posting details. > Everyone please share your slides if you have any

[python-committers] Re: Language Summit

On Thu, Apr 16, 2020 at 1:10 AM Stefan Behnel wrote: > Gregory P. Smith schrieb am 15.04.20 um 23:33: > > FWIW, I found it surprising to learn that there even was an online > language > > summit happening (yesterday). I hadn't heard about that being planned at > > all. > > > > Just because I

[python-committers] Core Workflow change: new commit to previously approved PR now requires re-review

X-post to python-committers, python-dev, and core-workflow mailing list I have just deployed a change to bedevere-bot to address the security concern related to automerging.( https://github.com/python/core-workflow/issues/325) Previously, if core dev has approved the PR and applied the

[python-committers] Re: Python Language Summit 2020 blog posts

The rest of Python Language Summit articles are now out: Property-Based Testing for Python Builtins and the Standard Library, Zac Hatfield-Dodds: https://pyfound.blogspot.com/2020/05/property-based-testing-for-python.html Core Workflow Updates, Mariatta Wijaya: https://pyfound.blogspot.com/2020

[python-committers] Python Language Summit 2020 blog posts

brary, Zac Hatfield-Dodds Core Workflow Updates, Mariatta Wijaya CPython on Mobile Platforms, Russell Keith-Magee Few more lightning talks from Eric Holscher and Zac Hatfield-Dodds Enjoy! ___ python-committers mailing list -- python-committers@

[python-committers] Re: Python Language Summit 2020 blog posts

> > Few more lightning talks from Eric Holscher and Zac Hatfield-Dodds > > ... and Jim Baker ___ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org

[python-committers] Re: RSVP: 2020 Python Core Dev Sprint

As an update, I've created https://python-core-sprint-2020.readthedocs.io/ with some details about the schedule, participants, and sprint projects, to give you a better idea of what to expect during the sprint. If you're planning to participate, please fill in this form:

[python-committers] Re: Thank you Larry Hastings!

Thank you, Larry! On Mon, Oct 5, 2020, 11:39 AM Barry Warsaw wrote: > They say being a Python Release Manager is a thankless job, so the Python > Secret Underground (PSU), which emphatically does not exist, hereby > officially doesn’t thank Larry for his years of diligent service as the >

[python-committers] Re: Welcome Brandt Bucher to the team!

Welcome to the team, Brandt! Will you be joining the core sprint next month? Signup form: https://forms.gle/84NkyYt5g616fs1r5 Details: https://python-core-sprint-2020.readthedocs.io/ ___ python-committers mailing list -- python-committers@python.org To

[python-committers] Save the date: Virtual Core Dev Sprint Oct 19-23, 2020

u would plan to participate from wherever you are! - Mariatta ___ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org https://mail.python.org/mailman3/lists/python-committer

[python-committers] Re: Save the date: Virtual Core Dev Sprint Oct 19-23, 2020

As an update, I've created the python/core-sprint <https://github.com/python/core-sprint>repo to give you all visibility of what we're up to. You can open an issue there if you have any suggestions or questions about the sprint. On Thu, Aug 6, 2020 at 9:06 PM Mariatta wrote: > Pl

[python-committers] Re: GitHub pull requests

> > is it closed automatically ? What is "it"? The PR itself? yes the PR becomes closed if it is merged. ___ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org

[python-committers] Re: GitHub pull requests

If you want the associated bpo ticket to be closed when the PR is merged, you have to add the commit message saying "closes " (Note that we should document this: https://github.com/python/devguide/issues/502) If you want the the associated GitHub Issue to be closed, it is similar, you have to

[python-committers] Re: GitHub pull requests

> > Is there a way to do this if you have automerge set? I don't see a way to > control the commit message in that case, but I could easily be missing > something. Yes, you need to edit the PR description. Automerge will take the PR description as the commit message.

[python-committers] Re: Notification of a three-month ban from Python core development

> > What's the point of sending this to everyone? Why wasn't this sent as a > quote? I'm not in the coc workgroup or steering council, but I think a copy was sent for transparency. I personally think it is important that we know that there was an incident, the incident was reviewed, and action

[python-committers] Re: dependabot gone bonkers?

t; https://github.com/gvanrossum/cpython/blob/master/.github/dependabot.yml > > I still think this is a bug (or missing feature) in dependabot. Please +1 > that issue! > > On Tue, Dec 1, 2020 at 7:52 AM Mariatta wrote: > >> Maybe a recent change in dependabot. This open ticket s

[python-committers] Re: Voter Roll for 2020 Steering Council Election (2021 term)

I think the PEP page hasn't been built yet to reflect the latest change. Though you can see the raw text here: https://github.com/python/peps/blob/master/pep-8102.rst On Mon, Nov 30, 2020 at 10:56 AM Ethan Furman wrote: > On 11/30/20 10:38 AM, Ernest W. Durbin III wrote: > > > All core devs

[python-committers] Re: dependabot gone bonkers?

Maybe a recent change in dependabot. This open ticket seems related https://github.com/dependabot/dependabot-core/issues/2804 On Tue., Dec. 1, 2020, 7:36 a.m. Guido van Rossum, wrote: > I got this too on two forks of cpython. It smells like a dependabot > mistake. > > On Tue, Dec 1, 2020 at

[python-committers] Re: PRs for 3.9

I've deployed a fix in miss-islington ( https://github.com/python/miss-islington/pull/421/files) so this should be working again now. I've retriggered backports to several PRs that were stuck. On Sat, Dec 12, 2020 at 12:21 PM Brandt Bucher wrote: > I saw a (seemingly) related issue with the

[python-committers] Re: bedevere/issue-number and bedevere/news: waiting for status to be reported

I tried removing the labels and adding them back. I didn't see any error logged in heroku. The app is running, yet the webhooks appeared to be delivered successfully, returning 200 status. Perhaps there's a problem from GitHub side. I'm on my phone right now and not able to further investigate

[python-committers] Re: Fwd: [Python-checkins] Adding "stale" GitHub Action (GH-21247)

tors would > be great, but using mindless automated rules will not get us there. In > any case, auto-closing after 35 days strikes me as madness. > > As it turns out, Mariatta changed the original 5 days in the PR to -1, > meaning never, but forgot to change the message. > > &

[python-committers] Re: Welcome Batuhan Taskaya to the team!

Welcome and congrats, Batuhan! Happy to have you on board! On Mon, Nov 9, 2020, 2:02 PM Brett Cannon wrote: > > ___ > python-committers mailing list -- python-committers@python.org > To unsubscribe send an email to python-committers-le...@python.org

[python-committers] New Python Triage members: Irit Katriel and Andre Delfino

This week, we granted bug triage permissions to two new members: Irit Katriel[1] and Andre Delfino[2]. Irit has been active commenting on issues on the bug tracker and has helped move the issues along. She is also actively participating in our sprint this week. Andre already has the Developer

[python-committers] Re: Roundup to GitHub Issues migration

FWIW, GitHub announced new powerful Issues today. > https://github.com/features/issues > I have asked GitHub to enable it for the Python org. > ___ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to

[python-committers] Re: Please make sure you're following good security practices with your GitHub account

Thanks for sharing your experience, and I think it's important for us core developers to be careful and vigilant about this. I was wondering if we should add under the "core developers responsibility" section (https://devguide.python.org/coredev/#responsibilities), about securing their GitHub

[python-committers] Jelle Zijlstra is now a member of Python Triage team

Hello, Wanted to share that I've granted the Python Triage membership to Jelle Zijlstra on Monday https://github.com/python/core-workflow/issues/401 Jelle already has the bug triage permissions on bpo, and additionally is already maintainer of python/typing, python/mypy, psf/black,

[python-committers] Re: Commits are no longer noted in bro issues

Is the bpo message posted by the CPython emailer webhook service? If so, I might be able to see logs on Heroku. On Wed., May 12, 2021, 8:15 a.m. Zachary Ware, wrote: > On Wed, May 12, 2021 at 9:23 AM Guido van Rossum wrote: > > (Could it have to do with the master->main move?) > > I think this

[python-committers] Re: core-dev chat

I'm hesitant to start yet another communication channel without considering all the maintenance work that it entails. It's not just about "let's spin up the server" but we should think about who will moderate and administer it. Since we have tried various platforms in the past, and some just

[python-committers] Re: How can I ignore email notifications on commits mentioning my GitHub handle on CPython forks?

> P.S. If anyone with communications channels to Github is planning to lobby > for changes, I'd prefer a way to say, "Never notify me of @ messages in > commit messages" followed by a special CC: address for easy filtering, > followed by "Please don't notify me a second time when an identical

[python-committers] Re: PyCon US passes for core devs

This is great! Thank you! On Wed., Mar. 17, 2021, 8:23 a.m. Ewa Jodlowska, wrote: > Hi! > > As some of you may have seen, PyCon US > launched registration. We have dedicated passes set aside for core devs as > part of our financial aid program. > > If you are

[python-committers] Re: Python Language Summit 2021 Signups Are Now Open

Last call for signing up for Python Language Summit. The forms will automatically be closed at 6 AM Vancouver time tomorrow. Currently we have 82 sign ups and 22 topic proposals. Details: https://us.pycon.org/2021/summits/language/ Sign up stats: https://mariatta.ca/language_summit_data/

[python-committers] Re: Python Language Summit 2021 Signups Are Now Open

is the time. Details: https://us.pycon.org/2021/summits/language/ Sign up stats: https://mariatta.ca/language_summit_data/ On Wed, Mar 3, 2021 at 12:31 PM Mariatta wrote: > Sign up to Python Language Summit is still open for about 3 more weeks. > > So far we received 32 sign ups, from 18

[python-committers] Re: Python Language Summit 2021 Signups Are Now Open

attendee timezones. >- Where: Online via Zoom (link will be sent via email to attendees) > - Co-chairs: Mariatta Wijaya & Łukasz Langa >- Blogger: Joanna Jablonski >- Sign up to attend *and actively participate*: >https://forms.gle/cgmGnmQMDhD2mhHY8 (closes after March 2

[python-committers] Re: Opting-in for Hacktoberfest

On Fri, Oct 8, 2021 at 1:08 AM Chris Withers wrote: > > Don't get me wrong though: I think Hacktoberfest is a terrible idea in > that focusses on short-term fly-by contributing rather than fostering > the long term commitments that all open source projects desperately need. > > I understand the

[python-committers] Re: Opting-in for Hacktoberfest

On Thu., Oct. 7, 2021, 12:35 a.m. Chris Withers, wrote: > Oh, well, that would explain the sudden influx of low value/quality PRs > including people pinging me directly by email.. > > huge -1 from me, please can we opt out of this? > We are opted-out right now so none of the PRs are eligible

[python-committers] Re: Do I qualify for a x...@python.org email

Hi Joannah, Yes you can request the email address by writing to postmas...@python.org On Sat., Oct. 2, 2021, 10:02 a.m. Joannah Nanjekye, < nanjekyejoan...@gmail.com> wrote: > Am migrating slowly away from using my Gmail address which I use for > CPython correspondence and development. > > I

[python-committers] Opting-in for Hacktoberfest

Hello, I would like to propose that we opt-in the CPython project for Hacktoberfest this year, by adding the hacktoberfest topic on the GitHub repository. https://hacktoberfest.digitalocean.com/ Hacktoberfest is an annual event organized by Digital Ocean, now in the 8th year, where aspiring

[python-committers] Hugo van Kemenade is now a member of the Python Triage Team

Happy new year everyone. Just letting you know that Hugo van Kemenade (@hugovk on bpo and GitHub) is the newest member of the Python Triage team. I've seen Hugo's activity in various places: CPython, DevGuide, PEPs and the core-workflow. He has 19 merged PRs and has been actively helping to

[python-committers] Python Language Summit at PyCon 2022 in Salt Lake City

s Blog. *Is this event recorded? Can I watch the livestream?* No, there will be no recording and no livestream available. If you'd like to participate in discussions, please sign up to attend. If you'd like to listen in, please wait for Alex's blog posts after the summit. Thank you, Mariatta,

[python-committers] Re: Python Language Summit at PyCon 2022 in Salt Lake City

tation proposals yet. (less than 5) >From the signups, it seems like attendees are interested in discussing topics like: Cinder, Faster CPython, and various PEPs. So if you've been thinking about submitting a proposal, please do it soon! Thank you, Mariatta, Łukasz,

[python-committers] Re: Python Language Summit at PyCon 2022 in Salt Lake City

: in person during PyCon US, Salt Palace Convention Center, room TBD Sign up to attend: https://forms.gle/CS8B6wJdcaN3rtWV8 (closes March 25 th, 2022 AoE) Sign up to discuss a topic: https://forms.gle/LAFE6TTYi15jL5RaA (closes March 25th, 2022 AoE) On Mon, Mar 21, 2022 at 9:14 AM Mariatta wrote

[python-committers] Announcing the Python Language Summit 2022 blog posts

The blog posts about presentations and discussions from Python Language Summit 2022 are now up for your enjoyment. Main article: https://pyfound.blogspot.com/2022/05/the-2022-python-language-summit_01678898482.html - Python without the GIL

[python-committers] Vote to promote Hugo van Kemenade

Hello, I have just opened the poll to grant core dev priviliges to Hugo van Kemenade. Please see details at: https://discuss.python.org/t/vote-to-promote-hugo-van-kemenade/20990 Thanks. ___ python-committers mailing list -- python-committers@python.org

[python-committers] New team member intro

, 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/

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

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

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] [Core-mentorship] Regarding reviewing test cases written for tabnanny module

ou 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 <tjre...@udel.edu> wrote: > On 4/11/2017 1:21 PM, Donald Stufft wrote: > >> >> O

Re: [python-committers] Deprecation Policy PEP Thread

up anything. Mariatta Wijaya On Sun, Apr 9, 2017 at 9:20 PM, Terry Reedy <tjre...@udel.edu> 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. >> >> -

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, Donald S

[python-committers] cherry_picker.py updated

/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/listinfo

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

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 out :) I've cherry-picked quite a number of commits with

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

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

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

thon/cpython/pulls?utf8=%E2%9C%93=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 <br...@python.org> wrote: > > > On Tue,

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

are taking some actions going forward. Mariatta Wijaya On Sun, Apr 2, 2017 at 8:04 PM, Nick Coghlan <ncogh...@gmail.com> wrote: > On 3 April 2017 at 04:08, Brett Cannon <br...@python.org> wrote: > > On Sun, 2 Apr 2017 at 04:34 Paul Moore <p.f.mo...@gmail.com> wrote: &

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 :) Mariatta

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 <br...@python.org> wrote: > Looks like they added some new warnings that are causing the docs build to > fail (e.g. https://travis-ci.org/python/

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 at 1:21 PM

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 <victor.stin...@gmail.com> wrote: > Does it allow catch for 3.3 and 3.4 branch

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

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

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

[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] 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 <ncogh...@gmail.com> wrote: > On 4 May 2017 at 06:10, Guido van Rossum <gu...@python.org> wrote: > > Two ex-board members disagree. I have to side with Brian; the PSF

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 <p.f.mo...@gmail.com> wrote: > Hmm, as an example, #2858, which seems to be about the AST (which I'm > not familiar with). I don't particularly wa

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 <victor.stin...@gmail.com> wrote: > Hi, > > 2017-09-28 18:21 GMT

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

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.python.org/mai

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

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.org https

[python-committers] Hacktoberfest

"hacktoberfest" label and apply it to some of the open issues in the DevGuide and core-workflow repo. The purpose of the label is to make the repo discoverable, so it shows up as one of the participating projects: https://github.com/search?q=label%3Ahacktoberfest+state%3Aopen+type%3Aissue=Issues

Re: [python-committers] Hacktoberfest

dy (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 <anto...@python.org> wrote: > > Le 28/09/2017 à 18:58, Stefan Krah a éc

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

Agree. +1! Mariatta Wijaya On Thu, Dec 7, 2017 at 8:29 AM, Ethan Furman <et...@stoneleaf.us> 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

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 <sent...@uthcode.com> wrote: > Congratulations, and Welcome Sanyam!. > > Thank you, and keep up with your good work. > > > > On Wed, Dec 6, 2017

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

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

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] 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

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 <br...@python.org> wrote: > > > On Tue, 24 Apr 2018 at 02:59 Serhiy Storchaka <storch..

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] Comments on moving issues to GitHub

en reading the mailing list for sometime until today. For those who missed it, some resources: 1. My language summit slides ( https://speakerdeck.com/mariatta/mariattas-python-language-summit-2018-presentation ) There are 3 bonus slides at the end which I did not get to cover, because we were ru

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

for that > Perhaps for a project the size of Python we should have a dedicated Project manager. Mariatta ᐧ ___ 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

  1   2   >