Just to clarify a key point here which is covered in PEP 1 but based on
offline conversations is being missed, the need for a sponsor only kicks in
for committing it to the peps repo which typically kicks in when
transitioning from python-ideas to python-dev (although if one gets a
sponsor sooner t
As a non core-dev, my enthusiasm for submitting a pep has been diminished
by some 40%.
yours,
Abdur-Rahmaan Janhangeer
http://www.pythonmembers.club | https://github.com/Abdur-rahmaanJ
Mauritius
___
Python-Dev mailing list
Python-Dev@python.org
https://
On Mar 6, 2019, at 10:28, Abdur-Rahmaan Janhangeer wrote:
>
> As a non core-dev, my enthusiasm for submitting a pep has been diminished by
> some 40%.
I’m sorry to hear that.
I think it’s worth keeping in mind that successfully navigating the PEP process
can be quite daunting an demoralizing
i think that "should have at least a mentor guiding you" sounds a lot more
better than
a core developer needs to sign on to be a sponsor
that sounds a lot more that without backing, you can't submit a pep, i
guess the core devs wanted to make things easier but the sponsor thing etc
put me off.
f
On Wed, Mar 6, 2019 at 8:58 PM Abdur-Rahmaan Janhangeer <
arj.pyt...@gmail.com> wrote:
> i think that "should have at least a mentor guiding you" sounds a lot more
> better than
>
> a core developer needs to sign on to be a sponsor
>
> that sounds a lot more that without backing, you can't submit
