Message 71456 - Python tracker

Message71456

Author	jnoller
Recipients	barry, benjamin.peterson, jnoller, mishok13, ncoghlan
Date	2008-08-19.18:20:52
SpamBayes Score	3.505906e-06
Marked as misclassified	No
Message-id	<4222a8490808191120l1e50b507r3e63f370f0a60562@mail.gmail.com>
In-reply-to	<1219162246.31.0.262038607589.issue3352@psf.upfronthosting.co.za>

Content
> > Nick Coghlan <ncoghlan@gmail.com> added the comment: > > Note regarding those comments - only the exitcode one is something we > should try to get sorted for the beta. Backing out the deprecation > warnings and cleaning up the documentation can wait for the first > release candidate. > Would it be acceptable to add a doc note mentioning .exitcode() may block rather than changing it back to the get_exitcode method? It's not that it's hard - but I do like the consistency of the property-style interface.

Content

>
> Nick Coghlan <ncoghlan@gmail.com> added the comment:
>
> Note regarding those comments - only the exitcode one is something we
> should try to get sorted for the beta. Backing out the deprecation
> warnings and cleaning up the documentation can wait for the first
> release candidate.
>

Would it be acceptable to add a doc note mentioning .exitcode() may
block rather than changing it back to the get_exitcode method? It's
not that it's hard - but I do like the consistency of the
property-style interface.

History
Date	User	Action	Args
2008-08-19 18:20:55	jnoller	set	recipients: + jnoller, barry, ncoghlan, benjamin.peterson, mishok13
2008-08-19 18:20:53	jnoller	link	issue3352 messages
2008-08-19 18:20:52	jnoller	create