Antoine Pitrou wrote:
> Guido van Rossum <guido <at> python.org> writes:
>> Thanks Barry! Indeed, I want everyone to focus on stabilization and
>> release blockers (and the occasional speed-up). Be extra careful with
>> what you submit between now and October, ask for a code review unless
>> you're really sure. Also, remember, NO NEW FEATURES!
>
> What should be done about http://bugs.python.org/issue2834?
> Should it make it into 3.0 or be delayed until 3.1?
>
> (code-wise there isn't left to be done, take a decision about a potential "(?
> a)" modifier and then implement it)
Before beta 3, I think if we need minor features (such as re.ASCII) to
fix fairly major bugs (re.IGNORECASE not working properly by default in
Py3k) then they should probably go in (case by case permission still
needed from Barry or Guido though, as with any post-beta1 feature addition).
Once we're past beta 3 and heading for rc1 then the bar for approving
feature additions to fix bugs will move even higher though.
Cheers,
Nick.
--
Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
---------------------------------------------------------------
http://www.boredomandlaziness.org
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4