Brett,
>> I think this is less accurate. Patches languish because of limited time
>> *and* because newbies don't have any social capital w/in the Python
>> community. New patch contributors are volunteers too, so they understand
>> that constraint. Their big problem is their outsider status, to wh
Brett,
> When you submit your patch, the tracker notifies a mailing list that
> most core Python developers subscribe to of the creation of your new
> patch.
Isn't "of the creation of your new patch" redundant? What else would it
be notifying the list of?
> Your patch may languish for week
Brett,
>> I liked the "patch angel" term in Chad's version. Stating "a Python
>> developer will take a look at your patch" smacks of a guarantee,
>> while Chad's use of "patch angel" and "get the ball rolling" better
>> conveyed the fact that this 5-for-1 rule is simply a practice of some
>>
Brett,
> Below is a draft for a set of patch guidelines.
Thanks for getting around to this!
> Wait for a developer to contact you
> ===
>
> At this point you need to wait for a Python developer to come along
> and look at your patch. This might be a while
Martin,
Thanks for the reply.
> I notice that my message comes across pretty negative.
No worries. I'm a volunteer too. :)
> It's a new feature, so it can't possibly get into Python 2.5. That means
> that no action is likely taken before October. It might take years until
> the patch gets con
Skip,
> It's worth noting that a number of people will look at a patch after the
> submitter has reviewed five other patches or bug reports
Also helpful, thanks!
chad
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/li
Brett,
> "We" is most of the developers on python-dev. There is a Python patches
> mailing list that most developers subscribe to.
Helpful, thanks.
> The latter unfortunatley. Since this all relies on people's volunteer
> efforts the patch usually has to matter to someone to lead to them putt
Brett,
Thanks for the helpful reply.
> Let it sit for now. We get email notifications when new patches come in.
Can I ask who "we" are? Is that the seven SF "Project Admins?" Is that
the 68 SF "Developers?"
And is every patch eventually responded to? Or do some simply fall by
the wayside?
Dear All,
Last week I submitted a patch (my first), and now I'm wondering what my
expectations should be. Do I sit around and wait? How long? Do I notify
this list? Do I notify a specific person, say, an author or reviewer of
the original code I modified? Do I use SF's assignment mechanism? Who
Thanks Jeremy. Also wandered off-list w/ Ka-Ping; posting here for
posterity.
chad
-
chad: BTW, how does the concept of AST transformations relate to the
concept of (Lisp) macros? Am I right to think that they are similar?
?!ng: Absolutely. In terms of mechanism, they're basically the s
> Would there be any interest in extending the compiler package with tools
> for AST transformations and for emitting Python source code from ASTs?
Heh, so I guess the answer is "yes."
BTW, how does the concept of AST transformations relate to the concept
of (Lisp) macros? Am I right to think th
Ka-Ping,
FWIW, I've also got an implementation, which is based on the parser
module rather than the compiler module. Much simpler, imo, but
whitespace isn't preserved (could be perhaps?).
Anyway, take it or leave it. Links follow.
chad
-
Subversion repository:
http://svn.zetadev.com/
12 matches
Mail list logo
