[Python-Dev] Re: Small lament...

Last I heard is that some core devs are forming the duo PEP Shop Boys. Their debut album will be titled "Please merge". On Sat, Apr 1, 2023, 11:22 AM Skip Montanaro wrote: > Just wanted to throw this out there... I lament the loss of waking up on > April 1st to see a creative April Fool's Day

[Python-Dev] Re: Switching to Discourse

On Thu, Jul 21, 2022 at 10:20 AM Samuel Colvin wrote: > > If discord is not finalised, we might also consider https://zulip.com/ > which rust uses and would (based on a > very quick look) appear to be more appropriate for python development's use > case? > > >

[Python-Dev] Re: Switching to Discourse

On Thu, Jul 21, 2022 at 10:05 AM Skip Montanaro wrote: > I have a perhaps stupid question. Is Discord the same as > discuss.python.org, just by another name? I find the similarity in > names a bit confusing. > > It's not the same. discuss.python.org is an instance of Discourse. Discord is

[Python-Dev] Re: Switching to Discourse

I think this is a great change, one I've been looking forward to myself. For authors of PEPs and discussion topics, Discourse provides better authoring experience, allowing for typo fixes and small edits. For moderators, Discourse also provides the toolings to make their jobs easier, which is

[Python-Dev] Announcing the Diátaxis Documentation Workshop

ps/17075#getting-in-touch-4>Getting in Touch If you have questions or concerns about the workshop, please post in the Docs Community forum <https://discuss.python.org/c/documentation/26> on Discourse. For private communications, please get in touch with one of the organizers: Mariatta, Ned Batch

[Python-Dev] 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-Dev] 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-Dev] 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-Dev] 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-Dev] CPython is participating in hacktoberfest (with caveat)

Hello, I'm happy to announce that CPython project is participating in hacktoberfest. I have just added the hacktoberfest topic to CPython's GitHub Repo ( https://github.com/python/cpython). Caveat: if we end up receiving too many spammy, invalid, and low-quality PRs which just adds burden to

[Python-Dev] Re: [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-Dev mailing list -- python-dev@python.org To unsubscribe send an email to

[Python-Dev] Re: Roundup to GitHub Issues migration

. On Wed, Jun 23, 2021 at 10:33 AM Barry Warsaw wrote: > > > Mariatta is the author of PEP 588 and I’m the delegate. Given how old > that PEP is and the fact that Ezio is managing the project elsewhere, I > think rejection is appropriate. However if we do that I think the PEP &g

[Python-Dev] Re: Can't sync cpython main to my fork

I also don't keep my fork in sync, and never needed to. I use the same workflow as Jelle. On Thu., May 6, 2021, 7:18 a.m. Jelle Zijlstra, wrote: > > > El jue, 6 may 2021 a las 6:58, Skip Montanaro () > escribió: > >> > Your main branch in GitHub has some commits they are not in >>

[Python-Dev] Announcing the CPython Docs Workgroup

linked above to understand the purpose, goals, group values, and guidelines of the Docs WG. We've been working to move the Docs Workgroup forward. We'll share more details at next month's Python Language Summit. For now, here's some high level information: - The initial workgroup members are: Carol, M

[Python-Dev] Re: On the migration from master to main

The branch has not been renamed. It will be renamed after the release of beta 1. There is a pending PR on DevGuide on how to change your existing local CPython repository to the new branch:

[Python-Dev] 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-Dev] 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-Dev] Re: Steering Council update for February

> > > The Steering Council discussed renaming the master branch to main > > and the consensus was that we should do that. > I did not that this was an issue. This will break 4 of my .bat files > (update repository and workspaces, build python.exes, run sphinx on > docs, run coverage.)

[Python-Dev] 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-Dev] Re: Please explain how to migrate when a function is removed, thanks ;-)

section in 3.10 and future whatsnew. > > On Thu, Jan 21, 2021 at 2:17 PM Mariatta wrote: > >> I agree that when we land a feature that introduces incompatible change >> like this, as part of the PR it should also include updating the >> documentation on how to mig

[Python-Dev] Re: Please explain how to migrate when a function is removed, thanks ;-)

I agree that when we land a feature that introduces incompatible change like this, as part of the PR it should also include updating the documentation on how to migrate. I would think that the feature should not be merged unless the doc has been updated too. Perhaps we should include this

[Python-Dev] Re: Python.org downloads page and javascript

Thanks for the report. Can you please open an issue in https://github.com/python/pythondotorg ? Thanks. On Thu, Nov 12, 2020, 5:18 AM Michael Felt wrote: > Hi, > > Not clear on where to report this - so I hope someone else sees the same > and can notify whoever needs to be notified. > > The

[Python-Dev] Re: [python-committers] 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-Dev] Re: PR checks hang because travis does not report back to github

This is a known issue and I have brought it up in GitHub OS Maintainers Feedback Group. It happens to other projects as well. Currently we have branch protection rule where even administrators couldnt merge the PR unless all the required checks passed. Perhaps we can relax the rule to allow

[Python-Dev] Ask a Core Dev Anything! (You can even ask Guido!)

Made you look! [image: :smile:] Hello Python community! Next month, from October 19-23, Python core developers will be participating in our annual weeklong core dev sprint. As part of the sprint, we will be hosting a Q session with participating Python core developers as a way for us to connect

[Python-Dev] Re: unable to create PR on github

Is this still problem? Which fork/branch did you did you want to create to the PR with? On Mon, Sep 21, 2020, 6:14 PM Ethan Furman wrote: > The green "create pull request" button is greyed out. > > I've tried reselecting the repos and branches, logging out and in, > navigating to that screen

[Python-Dev] Re: Python-checkins mailing list broken?

On Mon, Sep 14, 2020 at 12:49 PM Jeremy Kloth wrote: > It seems that python-checkins isn't receiving any new commits since > the 8th of September. A quick check of the github page shows activity > since then, as do the buildbots. > > Just a heads up. Does anyone know whether the

[Python-Dev] Re: [python-committers] 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-Dev] Re: Procedure for trivial PRs

> > when landed remove the > "need backport tags" you added... If done correctly, the "needs backport .." labels got removed automatically. We have detailed info here: https://devguide.python.org/committing/#backporting-changes-to-an-older-version a) is it ok to touch 3.9, as it's in rc1?

[Python-Dev] Re: Procedure for trivial PRs

On Thu, Aug 13, 2020 at 12:51 PM Facundo Batista wrote: > It's waiting for a "core review", which is a good thing (and by all > means welcomed). But as we're saturated of PRs, the fix is small, and > I'm a core developer myself... shall I wait for a review from another > core developer, or

[Python-Dev] 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-Dev] 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-Dev] Re: Python Language Summit 2020 blog posts

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

[Python-Dev] 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-Dev mailing list -- python-dev@python.org To unsubs

[Python-Dev] Re: new syntax

-1 from me. Seems unintuitive and I don't think it's all that obvious what intput/floatput would mean without first reading the docs. It adds maintenance burden while accomplishing little value. You might be able to just create your own third party library though. On Mon, Mar 2, 2020, 1:11 PM

[Python-Dev] Re: Merging PRs without CLA signed

don't remember if there's a magic comment that contributors can leave to get the bot to check again on its own, but the usual trigger for this is the submitter posting to say they've signed it, a core dev or triager seeing that and removing the "CLA Not Signed" label, There is no magic comment,

[Python-Dev] Re: Merging PRs without CLA signed

FWIW, I'm also one of the few core devs who won't merge a PR unless CLA is signed. Such PRs (and the backports) can't be automerged, creating manual work. I find the "triviality" is subjective. One line change in documentation is maybe trivial. One line change in the code is probably not as

[Python-Dev] 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-Dev] Re: vtk

vtk is a third party Python library. It's best to ask that you vtk's developers, not here. In this mailing list we focus on issues related to the development of core Python, not third party libraries. You might be able to find info about who maintains vtk library here https://pypi.org/project/vtk/

[Python-Dev] Re: 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-Dev] 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-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python

[Python-Dev] Re: Something wrong with the bug tracker?

I think this issue is being addressed here: https://github.com/python/bugs.python.org/issues/41 On Sun, Dec 22, 2019, 9:23 AM Ivan Pozdeev via Python-Dev < python-dev@python.org> wrote: > > On 22.12.2019 18:21, Martin (gzlist) via Python-Dev wrote: > > Logging in with openid using launchpad just

[Python-Dev] 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-Dev] Re: Announcing the new Python triage team on GitHub

> > That was my previous impression, but then I saw that Brett applied it > manually in this older PR to check if the author was still active: > https://github.com/python/cpython/pull/117#issuecomment-367187316. That was Brett's bot for backfilling the "awaiting ..." label to PRs created before

[Python-Dev] Re: Announcing the new Python triage team on GitHub

> > The capabilities of a triager mostly look good except for "closing PRs and > issues". This is a superpower that has traditionally been reserved for > more senior developers because it grants the ability to shut-down the work > of another aspiring contributor. Marking someone else's

[Python-Dev] 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-Dev] Re: Inline links in Misc/NEWS entries

> I would like to understand why some developers dislike including it, even when the reST syntax is provided. This has something to do with the use of blurb/blurb-it. Both tools specifically say "single paragraph with simple ReST markup". Further reading blurb's source code, it says the format

[Python-Dev] Re: Can someone please finish merging GH-13482?

> > - Does something special need to be done for doc changes? Nothing special. - Since this is a 1st-time contributor, does it need a change to the ACKS > file? I think the change is trivial enough, the misc/acks is not necessary. - Anything else? 1. Does it need to be backported? If so,

[Python-Dev] PEP 588 updates

category. (https://discuss.python.org/c/core-workflow) Thanks. Mariatta ᐧ ___ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message ar

[Python-Dev]  New keyword in bpo: `newcomer friendly`

 copy-pasta from core-mentorship mailing list. There is now a “newcomer friendly” keyword in bpo. My hope is that going forward, we can tag issues that are suitable for first time contributors with this keyword. It would be great for experienced contributors already familiar with our workflow

[Python-Dev] Re: PEP 581 has been updated with "Downsides of GitHub" section

If loading GitHub website is a technical problem, then it is a pre-existing condition not caused by PEP 581. On Sat, Jun 29, 2019, 12:47 AM Steven D'Aprano wrote: > You have missed at least one: the minimum technology requirement for > using Github is a lot more stringent than for Roundup.

[Python-Dev] Re: Annoying user on GitHub

gt; if these strange comments are removed by GitHub. > > Victor > > Le 02/07/2019 à 03:26, Mariatta a écrit : > > I've reported the user to GitHub. Ticket ID: 297185 > > > > On Mon, Jul 1, 2019, 5:40 PM Guido van Rossum > <mailto:gu...@python.org>> wrote

[Python-Dev] Re: PEP 581 has been updated with "Downsides of GitHub" section

Le 28/06/2019 à 18:56, Mariatta a écrit : > > Hi, > > > > I've updated PEP 581 yesterday, adding the "Downsides of GitHub" section. > > > > https://www.python.org/dev/peps/pep-0581/#downsides-of-github > > Hi, > > another missing point: the n

[Python-Dev] Re: Annoying user on GitHub

I've reported the user to GitHub. Ticket ID: 297185 On Mon, Jul 1, 2019, 5:40 PM Guido van Rossum wrote: > There's a user on GitHub ('experimentalles') who has created random PRs on > several projects (e.g. https://github.com/python/peps/pull/1116). Can we > ban them? The PRs look the work of a

[Python-Dev] PEP 581 has been updated with "Downsides of GitHub" section

happening there. Mercurial patches are still how you would contribute to it. Please re-read PEP 581 in its entirety. I plan to update PEP 588 sometime this weekend or next, to incorporate the discussions and suggestions brought up in Python Language Summit 2019:( http://pyfound.blogspot.com/2019/0

[Python-Dev] Re: EuroPython 2019 sprints

There were some easy issues assigned to me, that were set aside for the mentored sprint. They can be worked on by new contributors during the Euro Python sprint. ᐧ On Thu, Jun 13, 2019 at 9:37 AM Steve Dower wrote: > Hi all > > Just letting everyone know that I signed up any core devs who are

[Python-Dev] Re: 1 PR, multiple issues

Thanks Jeffrey Kintscher for asking this question. It is one of those "less obvious way to triage CPython issues" kind of thing. I think it would be great if this workflow can be documented and clarified in the devguide. I've opened https://github.com/python/devguide/issues/494 ᐧ

[Python-Dev] Re: 1 PR, multiple issues

Hmm, I personally would still consider the additional issues as duplicates. So I would make note in each of the duplicate issue saying "this is caused by the same problem as bpo-X", and close them, and attach the PR only to one bpo ticket. To decide which one I would keep open, perhaps the oldest

[Python-Dev] Re: 1 PR, multiple issues

Usually we prefer 1 PR per 1 bpo ticket. The smaller the PR is, the easier it is for us to review, and less likely to cause conflict when it comes to auto-backporting. When you say it resolves multiple issues, are these the same issue reported multiple times? ᐧ On Mon, Jun 10, 2019 at 7:52 PM

Re: [Python-Dev] Unrelated PRs linked to issues on bugs.python.org

___ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/mariatta%40python.org > _

[Python-Dev] Python Language Summit 2019 blog posts

If you have FOMO (fear of missing out) of Python Language Summit 2019, worry no more. We invited A. Jesse Jiryu Davis to cover for the language summit, and the blog posts are starting to appear in The PSF's official blog. Starts here:

[Python-Dev] Reminder: Python Language Summit 2019 Signup

, 2019) Speak: Topic submission form <https://goo.gl/forms/8l7ITEKOjlWkBjcl1> (before March 21, 2019) You will be notified by April 15, 2019 Co-chairs: Mariatta and Łukasz Blogger: A. Jesse Jiryu Davis All language summit attendees are also invited for dinner with PyCon staff and volunteers

Re: [Python-Dev] Using CLA assistant for Python contributions

On Thu, Mar 7, 2019 at 11:25 PM Paul Moore wrote: > > My preference would be to just re-sign the CLA *immediately*, and not > wait for when I have a PR - I presume that would be > possible/supported. > Yes this is possible, and once the switchover happens, I will post the link with instructions

Re: [Python-Dev] Using CLA assistant for Python contributions

Thought I'll be a little more clearer: you'll need to re-sign the CLA only for your future contributions (aka when you make new pull request to Python). Your previous CLA record are still available for The PSF, we're just not going to export over data from existing CLA host to CLA assistant. ᐧ ᐧ

Re: [Python-Dev] Using CLA assistant for Python contributions

> > I plan to > > switch us over to to CLA assistant in the coming week (before my OOOS of > > March 18) > OOOS? My Out Of Open Source aka I'm not doing any volunteer activities for 6 weeks (details: https://discuss.python.org/t/mariatta-will-be-ooos-out-of-open-source-star

Re: [Python-Dev] PEP 581: Using GitHub Issues for CPython

I've made the PR about "not closing all issues": https://github.com/python/peps/pull/917/files ᐧ ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe:

Re: [Python-Dev] PEP 581: Using GitHub Issues for CPython

On Thu, Mar 7, 2019 at 2:02 PM Skip Montanaro wrote: > I think it would be worthwhile to mention a couple > reasons, when the decision was made to use Roundup, etc. Without it, a > casual reader might think the core devs made a horrible mistake way > back when, and are only now getting around

Re: [Python-Dev] PEP 581: Using GitHub Issues for CPython

On Thu, Mar 7, 2019 at 12:36 PM Manuel Cerón wrote: > > After some frustration with bpo, I decided to file some issues into the > meta tracker, just to find out that the link [1] provided by the Python > Developer's Guide [2] is broken, giving a connection timeout. > > Sometime ago we've started

Re: [Python-Dev] PEP 581: Using GitHub Issues for CPython

On Thu, Mar 7, 2019 at 12:35 PM Matthew Woodcraft wrote: > > One part of this PEP stands out to me: > > | We should not be moving all open issues to GitHub. Issues with little > | or no activity should just be closed. Issues with no decision made for > | years should just be closed. > > I

[Python-Dev] PEP 581: Using GitHub Issues for CPython

I'd like to formally present to Python-dev PEP 581: Using GitHub Issues for CPython Full text: https://www.python.org/dev/peps/pep-0581/ This is my first PEP, and in my opinion it is ready for wider discussion. I don't know if it is "ready for pronouncement" so I'm hoping to get more guidance

[Python-Dev] Using CLA assistant for Python contributions

I've posted in Discourse under core-workflow category , and this has been previously discussed on the core-workflow mailing list

Re: [Python-Dev] "Good first issues" on the bug tracker

Cheryl, thanks for starting this thread and for helping to find easy issues to be worked on. I'm sympathetic to wanting to have tasks for the PyCon sprints, but at > the same time it feels exclusionary to "save" them from people who want > to volunteer at other times. Having paid to attend PyCon

Re: [Python-Dev] Lost sight

; https://mail.python.org/mailman/options/python-dev/mariatta%40python.org > ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] any way to subscribe to bugs and PRs on a particular topic?

__ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/mariatta%40python.org > ___ Python-Dev m

Re: [Python-Dev] Get a running instance of the doc for a PR.

r executing > arbitrary code on our server. > > ___ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/mariatta%40python.org >

Re: [Python-Dev] Get a running instance of the doc for a PR.

at can break and needs to be maintained", > and the risk of abuse. > > I have no opinion on whether the pluses outweigh the minuses. > > > -- > Steve > ___ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev >

Re: [Python-Dev] Stop automerging

Thanks Zach for fixing it quickly. Even if that bug has been fixed, per my instructions to python-committers, core devs should still edit the PR title and PR description *before* adding the '烙 automerge' label. The YouTube video (link in python-committers email) shows to edit those. The PR

Re: [Python-Dev] make patchcheck and git path

I don't quite understand the problem you're facing with git and make patchcheck? Also, perhaps this is more for core-workflow instead of python-dev. Mariatta ᐧ On Fri, Aug 24, 2018 at 3:20 AM Michael wrote: > I am trying to be a 'good scout' and run "make patchcheck" mor

Re: [Python-Dev] Python 2.7 EOL date

No more security fixes after Jan 1, 2020. It is the end of Python 2.7. On Thu, Aug 23, 2018, 12:47 PM Collin Anderson wrote: > Hi All, > > Sorry if this has been mentioned before, but I noticed the Python 2.7 EOL > date was recently set to Jan 1st, 2020. > > My understanding was Python

Re: [Python-Dev] Problem in importing python packages under python 3.6 environment

Hi Poornima, Your question is more appropriate for the python-list mailing list ( https://mail.python.org/mailman/listinfo/python-list) or python-tutors mailing list (https://mail.python.org/mailman/listinfo/tutor). On Thu, Aug 9, 2018, 8:30 AM Poornima .D. wrote: > Hi All, > > > I have

Re: [Python-Dev] Refactor __get_builtin_constructor on hasklib.py

2.7 is for bug fixes only. Unless there is a bug to be fixed, I would leave the code as is. Mariatta On Tue, Aug 7, 2018 at 8:14 AM 蔡銘峯 wrote: > Hello everybody, > I am Park Tsai. I want to refactor __get_builtin_constructor on hasklib.py > of python 2.7 ( > https://github.com/py

Re: [Python-Dev] Microsoft to acquire GitHub for $7.5 b

b data of CPython. Ernest is helping us get set up with daily backups of CPython repo to be stored within The PSF's infrastructure. Mariatta On Thu, Jun 7, 2018 at 11:24 AM, Chris Angelico wrote: > On Fri, Jun 8, 2018 at 3:33 AM, Chris Barker - NOAA Federal via > Python-Dev wrote: > > Any se

Re: [Python-Dev] Keeping an eye on Travis CI, AppVeyor and buildbots: revert on regression

Are there APIs we can use to check the status of builbots? Maybe we can have the our bots check for the buildbot status in backport PRs. On Wed, May 30, 2018, 2:33 AM Victor Stinner wrote: > > Buildbots only send email notifications to buildbot-sta...@python.org > when the state changes from

Re: [Python-Dev] Keeping an eye on Travis CI, AppVeyor and buildbots: revert on regression

Activating Travis CI GitHub app is being tracked in https://github.com/python/core-workflow/issues/255 Let's not press the button until after the 3.7 release. On Wed, Jun 6, 2018, 3:57 PM INADA Naoki wrote: > ​ > ​2018年6月7日(木) 2:44 Brett Cannon : > >> >> On Wed, 6 Jun 2018 at 09:27 INADA

Re: [Python-Dev] Microsoft to acquire GitHub for $7.5 billion

workflow, we'll discuss in core-workflow. Mariatta On Mon, Jun 4, 2018 at 10:02 AM, Antoine Pitrou wrote: > > That's true, but Microsoft has a lot of stakes in the ecosystem. > For example, since it has its own CI service that it tries to promote > (VSTS), is it in Microsoft's b

Re: [Python-Dev] How is the GitHub workflow working for people?

Can any of these said linters analyze only the diff in the PR, instead of the entire CPython codebase? Mariatta Wijaya ᐧ ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https

Re: [Python-Dev] How is the GitHub workflow working for people?

se? We'll need to come up with new workflow. How do we want to triage the issues? And what does it mean to current bug tracker triage permission? The recent > improvements to @miss-islington (kudos to Mariatta!) allowing her to > auto-backport PRs and commit them is a big time saver.

Re: [Python-Dev] GH-NNNN vs #NNNN in merge commit

No problem :) It's been deployed. Mariatta Wijaya On Fri, Jan 26, 2018 at 9:48 AM, Eric V. Smith <e...@trueblade.com> wrote: > > > It works for me: I think this is very helpful. Thanks for coding it up so > quickly! > > Eric > ___

Re: [Python-Dev] GH-NNNN vs #NNNN in merge commit

a comment to remind the core dev to update it next time. For example: ``` @Mariatta: Please replace # with GH- in the commit message next time. Thanks! ``` Does that work for everyone? Mariatta Wijaya ___ Python-Dev mailing list Python-Dev@python.

Re: [Python-Dev] GH-NNNN vs #NNNN in merge commit

can still merge using the UI if they want to. (Remember to replace the # with GH-) Mariatta Wijaya ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/opt

Re: [Python-Dev] GH-NNNN vs #NNNN in merge commit

. If it automatically merges, then there's no opportunity to adjust the commit message. So I suggest the option to provide the proper commit message to the mergebot. If not provided, I guess we'll use the GitHub PR title and description. Mariatta Wijaya ___ P

Re: [Python-Dev] GH-NNNN vs #NNNN in merge commit

New bot or miss-islington's new job? Still +1 either way, as long as other core devs are fine with it too :) Mariatta Wijaya ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.pyt

Re: [Python-Dev] GH-NNNN vs #NNNN in merge commit

> > Of course, we would still need to convince people to install it :) Right, that's the challenge :) I personally use Chrome (!) and I've been using your Chrome extension, so thank you! However, I don't feel comfortable making this available only for a specific browser user, feels exclusionary

Re: [Python-Dev] GH-NNNN vs #NNNN in merge commit

It has to be manually edited right before you commit/merge on GitHub. I don't think it can be automatically changed? Unless we have some kind of post commit hook to amend the commit message. I've been changing it to GH- , so does miss-islington when she backports. If you see the mixed GH- and #

Re: [Python-Dev] f-strings

I agree it's useful info :) I went ahead and made a PR [1]. In my PR, I simply linked to the Format Specification Mini Language[2] from f-strings documentation[3]. Not sure about updating PEP 498 at this point.. [1] https://github.com/python/cpython/pull/4888 [2]

Re: [Python-Dev] f-strings

Regards, > Wagner Herculano > > ___ > Python-Dev mailing list > Python-Dev@python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: https://mail.python.org/mailman/options/python-dev/mariatta. > wijaya%40gm

Re: [Python-Dev] "CPython loves your Pull Requests" talk by Stéphane Wirtel

/reviews * Time to merge a PR: 3 days in average, good! Regarding the average time to merge PR, I'm interested to know the average time to merge for PRs not made by Python Core Devs. Mariatta Wijaya ___ Python-Dev mailing list Python-Dev@python.org https

Re: [Python-Dev] PEPs: ``.. code:: python`` or ``::`` (syntaxhighlighting)

If we were to add Pygments support, it is to be done in pythondotorg project. I recalled the decision was to get PEPs rendered using Sphinx and host it at Read The Docs, so we don't have to worry about updating pythondotorg. Mariatta Wijaya ___ Python

Re: [Python-Dev] What's the status of PEP 505: None-aware operators?

-1 from me too. Mariatta Wijaya On Tue, Nov 28, 2017 at 12:38 PM, Barry Warsaw <ba...@python.org> wrote: > On Nov 28, 2017, at 15:31, Raymond Hettinger <raymond.hettin...@gmail.com> > wrote: > > > Put me down for a strong -1. The proposal would occasionally save

Re: [Python-Dev] Migrate python-dev to Mailman 3?

Starting with core-mentorship and then core-workflow sounds good. Let me first find out what it's going to take to do the migration. (I actually have no idea!) I've sent an email to postmaster and asked for more details :) Hope it's not too complicated... Mariatta Wijaya

  1   2   >