Re: [python-committers] Adding Ivan Levkivskyi as a core committer
Thank you Mariatta, Ethan, Eric, Guido, and everyone! I am overwhelmed by all the positive comments! I am so glad to be the part of the team and looking forward to make more contributions. (Will start right now form polishing PEP 560 and PEP 562 implementation :-) -- Ivan On 6 December 2017 at 19:20, Mariatta Wijaya wrote: > 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/ > > ___ 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] Adding Ivan Levkivskyi as a core committer
Thank you, Victor! -- Ivan On 8 December 2017 at 16:47, Victor Stinner wrote: > 2017-12-06 17:57 GMT+01:00 Mariatta Wijaya : > > Please add Ivan to the Developer Log in Dev Guide, and he should > subscribe > > to python-committers mailing list :) > > I added Ivan to the Devguide: > https://github.com/python/devguide/commit/f414589365e8d3808eaef3cf9f2b73 > 70314133a1 > > Victor > ___ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ python-committers 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] Wanting to merge my first PR under github - a bit of advice
Also don't forget to replace # with GH- in the commit message. I was hit by this few times. -- Ivan On 20 March 2018 at 20:58, Paul Moore wrote: > Hi, > Cheryl Sabella kindly migrated a patch I'd put on bpo some time ago > but forgotten about onto github. The PR (#6158) is ready to go (I > think) but this is the first time since the migration to github that > I've done a merge, and I'm not quite sure what the workflow is :-( I > didn't see much in the devguide (which covers how to write a PR, how > to test it etc, but not so much how to merge it, unless I missed > something, or it's so simple that the little I did find is all that's > needed!) > > Am I right that all I need to do is hit "Squash and Merge", tidy up > the commit message, and that's it for master? This is a doc change > which should probably go into 3.7 - so I presume I just add the "Needs > backport" label and Miss Islington does the rest? (I assume doc fixes > are still OK for 3.7 at this point?) > > Is there anything else I've missed? (Do I need another approver? I'm > assuming not, for a doc fix). > > Sorry for the dumb questions - if I've missed a glaringly obvious > explanation, feel free to let me know. I'm just a little nervous that > it's *so* simple I feel I must have missed something! > > Paul > > PS Thanks to everyone who has worked on the new github workflow. What > I've done so far has been really straightforward, and if I'm right in > what I think I need to do above, then you've made the rest of the > process beautifully simple, too! > ___ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ python-committers 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] Poll: Do you like the PEP 572 Assignment Expressions?
0: this might be a handy feature, but I am not sure the dangers it introduces are adequate for the problem it solves. -- Ivan On 2 May 2018 at 11:06, INADA Naoki wrote: > 0: I will use it if it's accepted, but I'm not sure it's merit is enough > for changing how Python code looks. > ___ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ python-committers 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] Proposing Mark Shannon to be a core developer
+1 Yes, I actually thought he is a core dev for ages :-) -- Ivan On 14 May 2018 at 17:42, Eric Snow wrote: > +1 > > -eric > > On Mon, May 14, 2018 at 4:41 PM, Larry Hastings > wrote: > > > > > > Dr. Mark Shannon contributed the "key sharing dictionary" to Python, > writing > > both the PEP and the implementation. This shipped in Python 3.3 and was > > listed as one of the top features of that release as according to the > > "What's New?" document. > > > > We've asked Mark in the past if he'd be interested in becoming a core > > developer--and he actually said no. At the time he said he didn't like > our > > antiquated workflow. Now that we've switched to the git-based core dev > > workflow, this objection is gone, and he's now interested in accepting > the > > commit bit and the responsibilities that it entails. > > > > I suspect you, my colleagues in CPython core development, will be > surprised > > at the current state of affairs. I'm expecting a load of "you mean Mark > > *isn't* a core developer yet?" replies. > > > > > > Submitted for your consideration, > > > > > > /arry > > > > ___ > > python-committers mailing list > > python-committers@python.org > > https://mail.python.org/mailman/listinfo/python-committers > > Code of Conduct: https://www.python.org/psf/codeofconduct/ > > > ___ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ python-committers 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] A different way to focus discussions
I would like to clarify, what would be a typical time-line for a PEP? Will
it look like this:
0. Preliminary discussions to determine whether an idea is PEP-worthy (can
happen anywhere, python-ideas, SIGs, even offline)
1. A PEP number is requested by a champion and assigned by a PEP editor (in
python/peps repo)
2. PEP is drafted and discussed by a narrow circle of interested
participants (happens in a separate repo)
3. When PEP is ready and polished make a PR to python/peps repo, and post
it to python-dev to get feedback (if any) from a wider audience
4. If reasonable objections appear at this step, go to step 2
5. Repeat steps 2-4 until accepted/rejected/deferred
Is this what you propose? Or you want to completely avoid posting to
python-dev?
--
Ivan
On 18 May 2018 at 18:25, Guido van Rossum wrote:
> Discussing PEPs on python-dev and python-ideas is clearly not scalable any
> more. (Even python-committers probably doesn't scale too well. :-)
>
> I wonder if it would make sense to require that for each PEP a new GitHub
> *repo* be created whose contents would just be a draft PEP and whose issue
> tracker and PR manager would be used to debate the PEP and propose specific
> changes.
>
> This way the discussion is still public: when the PEP-specific repo is
> created the author(s) can notify python-ideas, and when they are closer to
> submitting they can notify python-dev, but the discussion doesn't attract
> uninformed outsiders as much as python-{dev,ideas} discussions do, and it's
> much easier for outsiders who want to learn more about the proposal to find
> all relevant discussion.
>
> PEP authors may also choose to use a different repo hosting site, e.g.
> Bitbucket or GitLab. We can provide a script that allows checking the
> formatting of the PEP easily (basically pep2html.py from the peps repo).
>
> Using a separate repo per PEP has the advantage that people interested in
> a topic can subscribe to all traffic in that repo -- if we were to use the
> tracker of the peps repo you would have to subscribe to all peps traffic.
>
> Thoughts? (We can dogfood this proposal too, if there's interest. :-)
>
> --
> --Guido van Rossum (python.org/~guido)
>
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
>
___
python-committers 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] A different way to focus discussions
On 18 May 2018 at 19:46, Gregory P. Smith wrote: > > I'm all for picking a victom^Wvolunteer PEP to try dogfood it on. > > Can few related PEPs share the same repository? For example, I want to start writing three PEPs about extensions to PEP 484 type system: literal types, final/const qualifier, and integer generics (simple dependent types). They all are tightly connected (but I don't want a single mega-PEP), can I put these three in the same repo? -- Ivan ___ 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] FINAL WEEK FOR 3.7.0 CHANGES!
> 2. Pickle support in typing is not perfect. I was going to fix it (I had almost ready code), but lost a chance of doing this before. It can be changed in 3.7.1, but this means that pickles of some derived typing types created in 3.7.0 will be not compatible with future versions (may be 3.7.1 will not break compatibility, but it will be broken in future because we will not specially supported compatibility with 3.7.0). I think I had fixed this one. At least the examples reported on typing tracker are now fixed. Do you have some other examples that still fail? -- Ivan On 24 May 2018 at 12:02, Ned Deily wrote: > On May 24, 2018, at 11:35, Serhiy Storchaka wrote: > > I have doubts about two issues. I feel the responsibility for them > because I had the opportunity to solve them before, but I lost it. > [...] > > Serhiy, what are the bugs.python.org issue numbers for these? Are they > marked as "release blocker"? > > -- > Ned Deily > n...@python.org -- [] > > ___ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ python-committers 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] FINAL WEEK FOR 3.7.0 CHANGES!
> But cases not supported before 3.7 (like List[int]) now produce fragile pickles. List[int] pickled in 3.7 can't be un-pickled in 3.6, but I wouldn't worry too much about this because it never worked in 3.6. I remember you proposed using __getitem__ in __reduce__, but I am not sure it is a better way, although it will fix the above problem. I don't think this one is a blocker and we can move this discussion back to b.p.o., unless you have some particular concerns. The AST one however looks more serious. -- Ivan On 24 May 2018 at 12:26, Serhiy Storchaka wrote: > 24.05.18 19:02, Ned Deily пише: > >> On May 24, 2018, at 11:35, Serhiy Storchaka wrote: >> >>> I have doubts about two issues. I feel the responsibility for them >>> because I had the opportunity to solve them before, but I lost it. >>> >> [...] >> >> Serhiy, what are the bugs.python.org issue numbers for these? Are they >> marked as "release blocker"? >> > > For docstring in AST: https://bugs.python.org/issue32911 > > Inada's patch looked complex (actually it mostly restored the code before > his previous change). We didn't know about IPython and we decided that it > is not worth to change this code at this stage (after beta2). And > definitely it will be later to do this after rc1. > > For pickling of typing types: https://bugs.python.org/issue32873 > > Ivan fixed cases supported before 3.7. They now are backward and forward > compatible. But cases not supported before 3.7 (like List[int]) now produce > fragile pickles. > > > ___ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ python-committers 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] Comments on moving issues to GitHub
On 1 June 2018 at 20:29, Barry Warsaw wrote: > On Jun 1, 2018, at 16:54, Antoine Pitrou wrote: > > > > I wonder if other hosted services, such as Gitlab, offer a more > > sophisticated issue tracker. > > Note that GitHub (and I think GitLab too) provides two additional ways to categorise issues: project boards, and milestones. I think together with labels this may simulate current b.p.o. structure to certain extent. For example (approximately): * We can have milestones for releases (including past releases) * We can have "project boards" (slightly abusing this feature): new, triaged, PR review * Labels can be grouped using name prefix and color, for example (we have similar structure in mypy): - priority-low - priority-normal - priority-etc... - kind-bug - kind-docs - kind-feature - topic-asincio - topic-etc.. This is still quite limited, but together with bots this can practically replace current categorisation. -- Ivan ___ 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] New core developers: Lisa Roach and Emily Morehouse-Valcarcel
Welcome, Lisa and Emily! -- Ivan On Fri, 14 Sep 2018 at 20:29, Raymond Hettinger wrote: > At the developer sprints this week, we collectively decided to grant core > committer status to Emily and Lisa. > > Please join me in welcoming them to the team. > > > Raymond > > > --- > > Emily is the Director of Engineering at Cuttlesoft. She has previously > attended two Language Summits and three core development sprints at PyCon. > Since July, Emily has worked with Guido's guidance to implement PEP 572, > Assignment Expressions. She has also worked with Eric Snow to dive into > CPython's runtime as well as subinterpreters. This year at PyCon she gave > a talk on Python's AST. Here is her speaker bio > https://us.pycon.org/2018/speaker/profile/283/ and a link to her talk > video: https://www.youtube.com/watch?v=XhWvz4dK4ng > > Lisa has a background in network engineering and supported the Cisco sale > engineer team to develop high quality Python product demonstrations. Later > she moved to the Facebook security team. This is her third core developer > sprint. She and Guido are co-authors of PEP 526, Syntax for Variable > Annotations. Last year, she worked with Eric Smith on PEP 557, Data > Classes. Here is her speaker bio > https://us.pycon.org/2018/speaker/profile/824/ and a link to her Pycon > talks: https://www.youtube.com/watch?v=hKxbO4rRlpg and > https://www.youtube.com/watch?v=ww1UsGZV8fQ > ___ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
[python-committers] Re: Notification of a three-month ban from Python core development
Hi, I don't remember participating in any of the recent discussions on the mentioned lists. Why is this sent to me? Can you mention any particular posts? The scary atmosphere here becomes unbearable. I wasn't very active lately anyway, and I think I will stop contributing indefinitely. Best regards, Ivan On Wed, 22 Jul 2020 at 20:30, Python Steering Council < steering-coun...@python.org> wrote: > The following message was sent to a core developer. This message was > thoughtfully and respectfully sent by the Steering Council as a serious > reminder that the privilege to serve as a core developer comes with the > responsibility to act thoughtfully. > > --- > > Based on Code of Conduct violations in your recent mailing list posts, and > under the recommendation of the Code of Conduct Working Group, the Python > Steering Council has voted to issue a three-month corrective action to you > for Core Python development. > This corrective action bans you from all Core Development privileges > including commit rights, issue tracker privileges, and participation in all > core development communication spaces including mailing lists, Discourse, > and Zulip channels. This corrective action will be in effect for three > months. At the end of the three month period, these privileges will be > automatically reinstated. > > The Python Code of Conduct workgroup reviewed the conduct reports and > recommended that corrective action was necessary for the violations. The > Python Steering Council finds these violations to be serious breaches of > civility and expected core development conduct. > > Please consider this corrective action as a serious reminder that Python > core development is a privilege. This privilege to serve as a core > developer comes with the responsibility to act thoughtfully and reflect on > how hostile communications are harmful to other members of the community. > We trust that you will respect the temporary loss of privileges and the > seriousness of this action. > > Respectfully, > Python Steering Council > ___ > 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-committers.python.org/ > Message archived at > https://mail.python.org/archives/list/python-committers@python.org/message/2HC5XPURMQL6VRCXPMLQUL7OXBGU6OMS/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ 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-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/CLS5E634FCMB6W5H5JBLHZNSFRKKZGJG/ Code of Conduct: https://www.python.org/psf/codeofconduct/
[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? Anyway, this doesn't change my decision. On Wed, 22 Jul 2020 at 20:42, Alex Gaynor wrote: > It was sent to all of python-committers as a heads up that _someone_ was > banned. > > I didn't follow the thread in question, so this is all a little opaque to > me, I have no idea who we're talking about or what their conduct is. I > assume that's intentional. > > Alex > > On Wed, Jul 22, 2020 at 3:40 PM Ivan Levkivskyi > wrote: > >> Hi, >> >> I don't remember participating in any of the recent discussions on the >> mentioned lists. Why is this sent to me? Can you mention any particular >> posts? >> The scary atmosphere here becomes unbearable. I wasn't very active lately >> anyway, and I think I will stop contributing indefinitely. >> >> Best regards, >> Ivan >> >> >> On Wed, 22 Jul 2020 at 20:30, Python Steering Council < >> steering-coun...@python.org> wrote: >> >>> The following message was sent to a core developer. This message was >>> thoughtfully and respectfully sent by the Steering Council as a serious >>> reminder that the privilege to serve as a core developer comes with the >>> responsibility to act thoughtfully. >>> >>> --- >>> >>> Based on Code of Conduct violations in your recent mailing list posts, >>> and under the recommendation of the Code of Conduct Working Group, the >>> Python Steering Council has voted to issue a three-month corrective action >>> to you for Core Python development. >>> This corrective action bans you from all Core Development privileges >>> including commit rights, issue tracker privileges, and participation in all >>> core development communication spaces including mailing lists, Discourse, >>> and Zulip channels. This corrective action will be in effect for three >>> months. At the end of the three month period, these privileges will be >>> automatically reinstated. >>> >>> The Python Code of Conduct workgroup reviewed the conduct reports and >>> recommended that corrective action was necessary for the violations. The >>> Python Steering Council finds these violations to be serious breaches of >>> civility and expected core development conduct. >>> >>> Please consider this corrective action as a serious reminder that Python >>> core development is a privilege. This privilege to serve as a core >>> developer comes with the responsibility to act thoughtfully and reflect on >>> how hostile communications are harmful to other members of the community. >>> We trust that you will respect the temporary loss of privileges and the >>> seriousness of this action. >>> >>> Respectfully, >>> Python Steering Council >>> ___ >>> 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-committers.python.org/ >>> Message archived at >>> https://mail.python.org/archives/list/python-committers@python.org/message/2HC5XPURMQL6VRCXPMLQUL7OXBGU6OMS/ >>> Code of Conduct: https://www.python.org/psf/codeofconduct/ >>> >> ___ >> 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-committers.python.org/ >> Message archived at >> https://mail.python.org/archives/list/python-committers@python.org/message/CLS5E634FCMB6W5H5JBLHZNSFRKKZGJG/ >> Code of Conduct: https://www.python.org/psf/codeofconduct/ >> > > > -- > All that is necessary for evil to succeed is for good people to do nothing. > ___ 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-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/2BGTFAR3DW7XXGQA35ZLGWQXEWKCVGTC/ Code of Conduct: https://www.python.org/psf/codeofconduct/
