[Python-Dev] Update to PEP 1 re: content type

Discussed this with Guido earlier. He is supportive, and asked me to send email to python-dev :) Thanks Mariatta Wijaya ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailm

[Python-Dev] Please use #9999 when writing a new PEP

ame the file ``pep-.rst``, instead of ``pep-.rst``. Both PEP 1 and PEP 12 have been updated to address this. Thanks :) Mariatta Wijaya ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscr

Re: [Python-Dev] Questions on the CPython Git master branch: how to exclude commits of 3.x branches?

Can you try git log master ^3.6 I think it will give what's on master and not in 3.6 On Mar 31, 2017 8:47 AM, "Victor Stinner" wrote: > Hi, > > The CPython repository was converted from Mercurial to Git. Before > with Mercurial, we used extensively merges. For

Re: [Python-Dev] Git and Mercurial Security Update

git `git --version` tells you what version you have. It should be 2.14.1 now. On Windows, perhaps see https://confluence.atlassian.com/bitbucketserver/installing-and-upgrading-git-776640906.html#InstallingandupgradingGit-InstallorupgradeGitonWindows Mariatta Wijaya On Sun, Aug 13, 2017 at 7:05

Re: [Python-Dev] Appending a link back to bugs.python.org in GitHub PRs

Thanks for working on this, Kushal and Brett. Works great! Mariatta Wijaya On Fri, Jul 21, 2017 at 2:28 PM, Brett Cannon <br...@python.org> wrote: > Thanks to Kushal Das we now have one of the most requested features since > the transition: a link in PRs back to bugs.python.or

Re: [Python-Dev] Deprecate invalid ctypes call protection on Windows

+1 My understanding is this is a documentation change, marking it as deprecated in 3.6.2 and a Misc News entry. No actual code change. Correct? Mariatta Wijaya On Tue, May 23, 2017 at 8:28 AM, Antoine Pitrou <solip...@pitrou.net> wrote: > On Mon, 22 May 2017 11:17:18 -0700 >

Re: [Python-Dev] Deprecate invalid ctypes call protection on Windows

Thanks all. Documentation has been updated in https://bugs.python.org/issue30470 On May 23, 2017 9:13 PM, "Victor Stinner" wrote: Sure, make your change and then update libffi! Victor Le 23 mai 2017 18:19, "Steve Dower" a écrit : > On

Re: [Python-Dev] Possible bug in class-init, lookin for mentors

http://cpython-devguide.readthedocs.io/gitbootcamp.html Thanks :) Mariatta Wijaya On Tue, May 2, 2017 at 9:01 AM, Erik Bray <erik.m.b...@gmail.com> wrote: > On Fri, Apr 21, 2017 at 12:09 PM, Justus Schwabedal > <jschwabe...@gmail.com> wrote: > > Hi everyone, > &

Re: [Python-Dev] Pygments in PEPs?

> > For some unknown value of "soon". :-( Well as soon as these tasks are done: https://github.com/python/peps/projects/1 Mariatta Wijaya ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/lis

[Python-Dev] 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-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/py

Re: [Python-Dev] Cherry picker bot deployed in CPython repo

will 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 <mariatta.wij...@gmail.com> wrote:

Re: [Python-Dev] HTTPS on bugs.python.org

I also would like the links from bug tracker emails be in https instead of http. On Sep 1, 2017 6:31 AM, "Antoine Pitrou" wrote: > On Fri, 1 Sep 2017 22:15:29 +0900 > INADA Naoki wrote: > > FYI, there is issue report for it. > >

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

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

Anything I can do to help make the migration to MM3 + HyperKitty happen? :) Mariatta Wijaya ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options

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] "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] Migrate python-dev to Mailman 3?

> Except of Antoine Pitrou, does everybody else like the new UI? :-) I love the new UI. +1000 for migrating. Mariatta Wijaya On Mon, Oct 30, 2017 at 8:57 AM, Stefan Krah <ste...@bytereef.org> wrote: > On Mon, Oct 30, 2017 at 07:46:42AM -0700, Guido van Rossum wrote: &g

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

Backing up GitHub data has been brought up since the time we migrated to GitHub, and being tracked here: https://github.com/pytho n/core-workflow/issues/20 TL;DR We'll be using GitHub's new Migrations API to download archived GitHub data of

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

I think we shouldn't be speculating or making guesses. If people are concerned with how Microsoft will manage GitHub, please talk to Microsoft or GitHub representative, and not gossip in python-dev. If there is actual news or announcement of how GitHub will change, and how it will affect our

Re: [Python-Dev] PEP 561: Distributing and Packaging Type Information

> > Not sure if postings to python-ideas count, PEP 1 says: Post-History is used to record the dates of when new versions of the PEP are posted to python-list and/or python-dev. So, no ? Mariatta Wijaya ___ Python-Dev mailing list Pyth

Re: [Python-Dev] PEP 561: Distributing and Packaging Type Information

Ok I created an issue https://github.com/python/peps/issues/440, maybe someone can work on updating the wordings in PEP 1 and PEP 12. Thanks :) Mariatta Wijaya On Thu, Oct 26, 2017 at 5:03 PM, Guido van Rossum <gvanros...@gmail.com> wrote: > I think python-ideas does count here.

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

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

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

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

. 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

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

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] How is the GitHub workflow working for people?

ing it. A place where I can type in the news entry, give it the GitHub PR number, the bpo number, and with a button click the News.d file magically created and added to the PR. Any thoughts about this? Mariatta Wijaya [1] https://gidgethub.readthedocs.io/en/stable/ [2] https://us.pycon.org/2018/s

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

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] 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] 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" more > regularly.

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

I think the intent is just uploading the output HTML and static assets. I agree having the temporary output of PR docs build is useful, but I don't think a python.org domain is necessary. If it can be uploaded to any cloud storage service then that's good enough, just provide the link in the

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

This will make review turnout quicker, since I can potentially review and view the output from anywhere (phone while on a beach) instead of waiting until I'm back home, open a computer, and then verify the output myself. On Sun, Nov 4, 2018, 7:56 AM Steven D'Aprano On Sun, Nov 04, 2018 at

Re: [Python-Dev] Lost sight

Sorry to hear that. Please take care. On Sat, Jan 19, 2019, 4:15 AM Serhiy Storchaka I have virtually completely lost the sight of my right eye (and the loss > is quickly progresses) and the sight of my left eye is weak. That is why > my activity as a core developer was decreased significantly

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

For GitHub PRs, you can add yourself to CODEOWNERS file, so you will be automatically requested review if a PR contains changes to unittest.mock. (and you'll receive review-request notification) https://github.com/python/cpython/blob/master/.github/CODEOWNERS When GitHub sends you review request

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