Hello,
I'd like to propose Serhiy Storchaka as a new core developer. He has
made numerous contributions, and has proven receptive to comments and
reviews. He's also interested in becoming a core developer.
What do you think?
Regards
Antoine.
--
Software development and contracting: http://pro.pitrou.net
Hi,
3.3.0 rc1 is now out, and I'd like to remind you that commits you
want to be in 3.3.0 rc2 or final have to be in my release clone,
so you need to tell me you want them there. Either ping me on IRC,
or send an email, and I'll have a look.
cheers,
Georg
I'd like to propose granting Eric Snow commit privileges.
He's been contributing for a couple of years, mostly working on the
import system replacement with Brett and participating in design
discussions on import-sig, but also contributing to patches and
discussions relating to the core compiler and code execution
machinery.
Cheers,
Nick.
--
Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia
Dear committers,
if the buffer/array-related blockers are resolved in time, the rc1
will be released one week from now.
Since some people asked: at the moment we are not in the RC phase yet,
so fixing bugs is allowed, but it would be advisable to have a second
committer review any nontrivial fix.
From the release of rc1, I will keep the code that will become 3.3 in
a separate repo, so that commits to "default" on cpython *won't* go
into 3.3. You will have to notify me of all commits that you think
*should* go there, so that I can cherry-pick them. Not all bugfixes
fall into that category; only showstopper-level ones. The rest will
have to wait for 3.3.1.
cheers,
Georg
Access to the Python results is currently down, but has anyone
actually accessed the Coverity scan results any time recently? Or who
even has access anymore?
Hi guys,
I just got an exception from the code review tool running on bugs.python.org.
The server returned the full debug stack trace (which means DEBUG=True in
Django). Is this intended?
Cheers,
-- Alexandre
