Nick Coghlan wrote:
> I consider the proposed import change (looking for __module_name__ in the
> main
> module) a bug fix for the interaction between PEP 338 and 328, but I'll hold
> off on committing it until I get the OK from yourself or Neal (and put the
> patch on SF in the meantime).
Or
Anthony Baxter wrote:
> Anyway, this is the current thinking. Am I being too dogmatic here?
> Comments solicited.
Seems like a fair policy to me.
> As far as people to sign off on things, Neal, myself or Guido should
> be the ones to do it. Course, Guido will probably decide he doesn't
> want
Only one gripe:
[Anthony Baxter]
> ...
> Once we hit release candidate 1, the trunk gets branched to
> reease25-maint.
Save the branch for 2.5 final (i.e., the 2.5final tag and the
release25-maint branch start life exactly the same). Adding a new
step before it's possible to fix rc1 critical bug
On 6/28/06, Anthony Baxter <[EMAIL PROTECTED]> wrote:
> As far as people to sign off on things, Neal, myself or Guido should
> be the ones to do it. Course, Guido will probably decide he doesn't
> want this dubious honour .
Right. But I agree with the policy.
FWIW, I think Nick's change for -m is
This is a request for comments - this is my current thinking on a
policy for checkins to the trunk between now and the release of 2.5
final.
Now that we're in beta:
If you don't add an entry to Misc/NEWS, a test (if relevant or
possible) and docs (if relevant), the checkin is probably g
