C. Titus Brown wrote:
> [...]
> I have had a hard time getting a good sense of what core code is well
> tested and what is not well tested, across various platforms. While
> Walter's C/Python integrated code coverage site is nice, it would be
> even nicer to have a way to generate all that inform
On Fri, Apr 10, 2009 at 4:38 PM, C. Titus Brown wrote:
> Unquestionably "core" by my criteria above:
>
> 3to2 tool -- 'nuff said.
I worked on the 3to2 tool during the sprint last week at PyCon. I can
chip in for GSoC in the event it does get picked up.
-Ron
PS - I'm out of town next week for
> The student will also provide some plugins for a maximum number of
> existing keyring systems.
> Some of these plugins might be included in Distutils, and some of them
> in a third-party package.
This is slightly better, but see my previous message (that is feature
creep in distutils, and likely
Tarek Ziadé wrote:
>> -> I'm also skeptical that this is a good SoC project in the first place.
>
> What is a good SoC project from your point of view ?
As a core project - tricky. Implement some long-standing complex feature
request, or fix a pile of outstanding bug reports for a module (like
th
> I'm using "core projects" as a shorthand for projects that directly
> address the core development environment, the stdlib, and priorities of
> committers on python-dev. Tarek is a committer, and it sounded like
> you, Jim, and Georg were all interested in this project, too -- that
> pushes it w
Ok what about this then: I am changing the scope a little bit, and I
think the students will be fine with this change
since it's the same work.
"The project will consist of creating a plugin system into Distutils
to be able to store and retrieve the username/password
used by some commands, without
> -> I'm also skeptical that this is a good SoC project in the first place.
What is a good SoC project from your point of view ?
> -> Coming up with a wrapper for, say, Apple Keychain, could be a good
> -> project. Coming up with a unifying API for all keychains is out of
> -> scope, IMO; various
On Sat, Apr 11, 2009 at 08:13:35AM +0200, "Martin v. L?wis" wrote:
-> > 2x "keyring package" -- see
-> >
http://tarekziade.wordpress.com/2009/03/27/pycon-hallway-session-1-a-keyring-library-for-python/.
-> > The poorer one of these will probably be axed unless Tarek gives it
-> > strong support.
-
On Sat, Apr 11, 2009 at 12:21:18PM +0200, Mario wrote:
-> > He says vague things about patches too, but I'm not sure what. If he
-> > wanted to make that into a 'patchbot' that just applied every patch in
-> > isolation and ran 'make && make test' and posted results in the
-> > tracker I'd be a ha
>
>
> He says vague things about patches too, but I'm not sure what. If he
> wanted to make that into a 'patchbot' that just applied every patch in
> isolation and ran 'make && make test' and posted results in the
> tracker I'd be a happy camper.
>
>
Jack, how about you write that idea down on the
> 2x "keyring package" -- see
> http://tarekziade.wordpress.com/2009/03/27/pycon-hallway-session-1-a-keyring-library-for-python/.
> The poorer one of these will probably be axed unless Tarek gives it
> strong support.
I don't think these are good "core" projects. Even if the students come
up with
On Fri, Apr 10, 2009 at 4:38 PM, C. Titus Brown wrote:
[megasnip]
> roundup VCS integration / build tools to support core development --
> a single student proposed both of these and has received some
> support. See http://slexy.org/view/s2pFgWxufI for details.
>From the listed web
On Fri, Apr 10, 2009 at 06:05:02PM -0500, Benjamin Peterson wrote:
-> 2009/4/10 C. Titus Brown :
-> > 2x "improve testing tools for py3k" -- variously focus on improving test
-> > ?? ?? ?? ??coverage and testing wrappers.
-> >
-> > ?? ?? ?? ??One proposes to provide a nice wrapper to make nose and
2009/4/10 C. Titus Brown :
> 2x "improve testing tools for py3k" -- variously focus on improving test
> coverage and testing wrappers.
>
> One proposes to provide a nice wrapper to make nose and py.test
> capable of running the regrtests, which (with no change to
> regrt
On Fri, Apr 10, 2009 at 6:02 PM, C. Titus Brown wrote:
> On Fri, Apr 10, 2009 at 05:53:23PM -0300, Guilherme Polo wrote:
> -> >
> -> > IDLE/Tkinter patch integration & improvement -- deal with ~120 tracker
> -> > ? ? ? ?issues relating to IDLE and Tkinter.
> -> >
> ->
> -> Is it important, for the
Well, I think Numpy is of huge importance to a major Python user segment,
the scientific community. I don't know if that makes it 'core', but I
strongly agree that it's important.
Better testing is always useful, and more "core", but IMO less important.
-T
On Sat, Apr 11, 2009 at 6:38 AM, C. Titu
On Fri, Apr 10, 2009 at 05:53:23PM -0300, Guilherme Polo wrote:
-> >
-> > IDLE/Tkinter patch integration & improvement -- deal with ~120 tracker
-> > ? ? ? ?issues relating to IDLE and Tkinter.
-> >
->
-> Is it important, for the discussion, to mention that it also involves
-> testing this area (i
On Fri, Apr 10, 2009 at 5:38 PM, C. Titus Brown wrote:
> Hi all,
>
> this year we have 10-12 GSoC applications that I've put in the "relevant
> to core Python development" category. These projects, if mentors etc
> are found, are *guaranteed* a slot under the PSF GSoC umbrella. As
> backup GSoC
Hi all,
this year we have 10-12 GSoC applications that I've put in the "relevant
to core Python development" category. These projects, if mentors etc
are found, are *guaranteed* a slot under the PSF GSoC umbrella. As
backup GSoC admin and general busybody, I've taken on the work of
coordinating
19 matches
Mail list logo
