[python-committers] Commit privileges for Roger Serwy for IDLE
I would like to propose Roger Serwy be given commit privileges to work on IDLE. Roger has demonstrated long-term interest in IDLE and has been contributing to IDLE in a number of ways for years. He has submitted many patches for IDLE to the tracker since at least April 2008. He has developed a number of IDLE extensions (http://idlex.sourceforge.net), some of which he has proposed for inclusion in the standard library. He is also active in triaging and commenting on the bug tracker and has had developer privileges on the tracker for the past 12 months. He has also already signed the contributor agreement and I know he has been interested in becoming a core developer for IDLE. I've informally discussed this with a few other core developers here at PyCon and I think there is general agreement that having Roger be able to contribute more directly to IDLE would be a really good thing. I would certainly be willing to help mentor him as necessary. -- Ned Deily, [email protected] ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Commit privileges for Roger Serwy for IDLE
+1, he is pretty active. I've committed many his patches. On Tue, Mar 19, 2013 at 12:17 PM, Ned Deily wrote: > I would like to propose Roger Serwy be given commit privileges to work > on IDLE. Roger has demonstrated long-term interest in IDLE and has been > contributing to IDLE in a number of ways for years. He has submitted > many patches for IDLE to the tracker since at least April 2008. He has > developed a number of IDLE extensions (http://idlex.sourceforge.net), > some of which he has proposed for inclusion in the standard library. He > is also active in triaging and commenting on the bug tracker and has had > developer privileges on the tracker for the past 12 months. He has also > already signed the contributor agreement and I know he has been > interested in becoming a core developer for IDLE. I've informally > discussed this with a few other core developers here at PyCon and I > think there is general agreement that having Roger be able to contribute > more directly to IDLE would be a really good thing. I would certainly > be willing to help mentor him as necessary. > > -- > Ned Deily, > [email protected] > > ___ > python-committers mailing list > [email protected] > http://mail.python.org/mailman/listinfo/python-committers -- Thanks, Andrew Svetlov ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Commit privileges for Roger Serwy for IDLE
+1 ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Commit privileges for Roger Serwy for IDLE
On 3/19/2013 3:17 PM, Ned Deily wrote: I would like to propose Roger Serwy be given commit privileges to work on IDLE. Roger has demonstrated long-term interest in IDLE and has been contributing to IDLE in a number of ways for years. He has submitted many patches for IDLE to the tracker since at least April 2008. He has developed a number of IDLE extensions (http://idlex.sourceforge.net), some of which he has proposed for inclusion in the standard library. He is also active in triaging and commenting on the bug tracker and has had developer privileges on the tracker for the past 12 months. He has also already signed the contributor agreement and I know he has been interested in becoming a core developer for IDLE. I've informally discussed this with a few other core developers here at PyCon and I think there is general agreement that having Roger be able to contribute more directly to IDLE would be a really good thing. I would certainly be willing to help mentor him as necessary. I have been intending to propose the same thing for the same reasons, (which you wrote up better than I would have -- thanks) but have been waiting for the resolution of http://python.org/dev/peps/pep-0434/ clarifying what rule he and I and anyone else can use for deciding what branches an IDLE change can be applied to. Terry ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Commit privileges for Roger Serwy for IDLE
+1 oh please yes ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Commit privileges for Roger Serwy for IDLE
It's maybe not the right place to discuss that, but why is IDLE part of the Python stdlib? Can't we maintain IDLE outside Python? I guess that maintaining it outside the stdlib would allow to develop it faster and be able to upgrade it for old (unmaintained) Python versions. Packaging Python with IDLE is stil a good idea, especially on Windows where there is no good text editor by default. Victor 2013/3/19 Ned Deily : > I would like to propose Roger Serwy be given commit privileges to work > on IDLE. Roger has demonstrated long-term interest in IDLE and has been > contributing to IDLE in a number of ways for years. He has submitted > many patches for IDLE to the tracker since at least April 2008. He has > developed a number of IDLE extensions (http://idlex.sourceforge.net), > some of which he has proposed for inclusion in the standard library. He > is also active in triaging and commenting on the bug tracker and has had > developer privileges on the tracker for the past 12 months. He has also > already signed the contributor agreement and I know he has been > interested in becoming a core developer for IDLE. I've informally > discussed this with a few other core developers here at PyCon and I > think there is general agreement that having Roger be able to contribute > more directly to IDLE would be a really good thing. I would certainly > be willing to help mentor him as necessary. > > -- > Ned Deily, > [email protected] > > ___ > python-committers mailing list > [email protected] > http://mail.python.org/mailman/listinfo/python-committers ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Commit privileges for Roger Serwy for IDLE
On Tue, Mar 19, 2013 at 5:00 PM, Victor Stinner wrote: > It's maybe not the right place to discuss that, but why is IDLE part > of the Python stdlib? Can't we maintain IDLE outside Python? I guess > that maintaining it outside the stdlib would allow to develop it > faster and be able to upgrade it for old (unmaintained) Python > versions. > Strongly +1 here. I'd extend it to the whole tkinter and derivatives, but IDLE itself is a worthier goal. In my view, it's been mainly "kept alive" for the past many years and is a much inferior IDE to others, and not a very good editor. FWIW, I heard some mentions how this is important for education. It's just one data point, but perhaps worth mentioning - I met a teacher during PyCon and specifically asked him if he used IDLE, and he said that no, IDLE isn't really good enough an editor and he asked his students to use Sublime text. Eli ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Commit privileges for Roger Serwy for IDLE
In article , Eli Bendersky wrote: > On Tue, Mar 19, 2013 at 5:00 PM, Victor Stinner > wrote: > > It's maybe not the right place to discuss that, but why is IDLE part > > of the Python stdlib? Can't we maintain IDLE outside Python? I guess > > that maintaining it outside the stdlib would allow to develop it > > faster and be able to upgrade it for old (unmaintained) Python > > versions. > Strongly +1 here. I'd extend it to the whole tkinter and derivatives, but > IDLE itself is a worthier goal. In my view, it's been mainly "kept alive" > for the past many years and is a much inferior IDE to others, and not a > very good editor. Please, this is definitely not the right place to discuss the issue of IDLE in the stdlib. It has been discussed repeatedly and the conclusion is always that it is an important part of the batteries-included experience. More importantly, PEP 434, is out for review concerning IDLE maintenance and features, is currently out for review. That would be a much more appropriate place to bring up any concerns. (I will be forwarding my comments to the PEP soon, BTW.) -- Ned Deily, [email protected] ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Commit privileges for Roger Serwy for IDLE
2013/3/20 Ned Deily : > Please, this is definitely not the right place to discuss the issue of > IDLE in the stdlib. It has been discussed repeatedly and the conclusion > is always that it is an important part of the batteries-included > experience. I don't propose to remove IDLE from the stdlib, just move the code to another repository to allow to maintain it more easily. And then re-add IDLE to the stdlib at each Python release. We might also release IDLE more frequently using an external repository. > More importantly, PEP 434, is out for review concerning > IDLE maintenance and features, is currently out for review. That would > be a much more appropriate place to bring up any concerns. (I will be > forwarding my comments to the PEP soon, BTW.) Oh sorry, I missed this PEP. I will read it. Victor ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Commit privileges for Roger Serwy for IDLE
On Tue, Mar 19, 2013 at 5:26 PM, Ned Deily wrote: > In article > , > Eli Bendersky wrote: > > On Tue, Mar 19, 2013 at 5:00 PM, Victor Stinner > > wrote: > > > It's maybe not the right place to discuss that, but why is IDLE part > > > of the Python stdlib? Can't we maintain IDLE outside Python? I guess > > > that maintaining it outside the stdlib would allow to develop it > > > faster and be able to upgrade it for old (unmaintained) Python > > > versions. > > Strongly +1 here. I'd extend it to the whole tkinter and derivatives, but > > IDLE itself is a worthier goal. In my view, it's been mainly "kept alive" > > for the past many years and is a much inferior IDE to others, and not a > > very good editor. > > Please, this is definitely not the right place to discuss the issue of > IDLE in the stdlib. It has been discussed repeatedly and the conclusion > is always that it is an important part of the batteries-included > experience. More importantly, PEP 434, is out for review concerning > IDLE maintenance and features, is currently out for review. That would > be a much more appropriate place to bring up any concerns. (I will be > forwarding my comments to the PEP soon, BTW.) > Sorry for mixing it up - I did not intend to hijack the discussion. While I'm not familiar with Roger's work ISTM there were enough +1 to put a stamp on it. Eli ___ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] [Infrastructure] test suite dependencies on www.python.org
On Mon, 18 Mar 2013 15:17:23 -0700, Noah Kantrowitz wrote:
> As part of the PyCon sprints I would like to move python.org off
> dinsdale to a VM at OSL. Due to the build system being tied to SVN,
> I'll also migrate that service on the same VM. Do any SVN repos other
> than www/ need to remain available? This would require at least some
> period of not changing the website, probably a few hours, but I don't
> think that would be a problem. This is mostly a legacy move so I'm not
> going to clean it up much, we'll have a new site soon enough.
While working on tests at the sprint I was reminded that there are
various tests in the Python standard library that depend on resources in
specific resources in specific locations at python.org. We will need
a plan for finding and dealing with these before (or as?) the new web
site is turned up.
Example:
request = urllib.request.Request("http://www.python.org/~jeremy/";)
And then there are things like:
h = client.HTTPSConnection('svn.python.org', 443, context=context)
I don't think there are a huge number of these, but we will need to
deal with them.
--David
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] [Infrastructure] test suite dependencies on www.python.org
On Tue, Mar 19, 2013 at 8:27 PM, R. David Murray wrote:
> While working on tests at the sprint I was reminded that there are
> various tests in the Python standard library that depend on resources in
> specific resources in specific locations at python.org. We will need
> a plan for finding and dealing with these before (or as?) the new web
> site is turned up.
>
> Example:
>
> request = urllib.request.Request("http://www.python.org/~jeremy/";)
>
> And then there are things like:
>
> h = client.HTTPSConnection('svn.python.org', 443, context=context)
>
Tests which are accessible over HTTP can still remain the same, for
others, I shall look for alternatives.
But yeah, these tests (or potential test failures) should not be be a
blocker for the Infrastructure team.
Thanks,
Senthil
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
