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
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://gi
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
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.
> _
+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
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
py
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,
> 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
> 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
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:
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
>
>
> -
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 regar
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,
>
13 matches
Mail list logo
