Re: [Python-Dev] tracker status options

> It would be great to put in some of those extra status options that were > discussed recently... > >"Open/New" >"Needs help / Chatting" >"Under development" >"Pending feedback" >"Closed" Are you sure that you want them to be status options? Why not stages? ISTM that an issue

[Python-Dev] tracker status options

Hi all, I'm continuing to (slowly) work through issues. I have been looking particularly at a lot of the open issues regarding strftime. It would be great to put in some of those extra status options that were discussed recently... "Open/New" "Needs help / Chatting" "Under development"

Re: [Python-Dev] what's new in 3.1 anyone?

[Benjamin Peterson] It seems Andrew will be doing "What's new in Python 2.7?" again, but we don't seem to have a volunteer to do the 3.1 version? Would anyone like to volunteer? I'll pick-up this responsibility. Raymond ___ Python-Dev mailing list

[Python-Dev] what's new in 3.1 anyone?

It seems Andrew will be doing "What's new in Python 2.7?" again, but we don't seem to have a volunteer to do the 3.1 version? Would anyone like to volunteer? -- Regards, Benjamin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/m

Re: [Python-Dev] Core projects for Summer of Code

> Summer of Code is ramping up. Every year the common complaint is that > not > enough Python core projects get proposed by students, and of course a > big > reason for that is often the only encouragement we offer prospective > students is a link to the PEP index. > >>

Re: [Python-Dev] Core projects for Summer of Code

On Wed, Mar 18, 2009 at 9:44 PM, Daniel Fetchinson wrote: Summer of Code is ramping up.  Every year the common complaint is that not enough Python core projects get proposed by students, and of course a big reason for that is often the only encouragement we offer prospective >>

Re: [Python-Dev] Core projects for Summer of Code

>>> Summer of Code is ramping up. Every year the common complaint is that >>> not >>> enough Python core projects get proposed by students, and of course a big >>> reason for that is often the only encouragement we offer prospective >>> students is a link to the PEP index. >>> >>> So let's make th

Re: [Python-Dev] Core projects: 3to2

2009/3/18 Antoine Pitrou : > >> class C() to class C(object) > > __metaclass__ = type Or even better: just inherit from object in 3.0 and 2.x. :) -- Regards, Benjamin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/li

Re: [Python-Dev] Core projects for Summer of Code

Feel free to email wi...@bluesock.org or me with your ideas if the markup is difficult to work with. We've been on wiki duty all afternoon. description, any specific skills they'll need (special library, compiler theory, etc), what mentor should they talk to if they're interested. The markup com

Re: [Python-Dev] Core projects for Summer of Code

Arc Riley wrote: > The process is as follows; we're compiling ideas for > http://wiki.python.org/moin/SummerOfCode/2009 and getting mentors signed up > at http://socghop.appspot.com/ Any chance that we can keep http://wiki.python.org/moin/SummerOfCode/2009 light on markup? I simply can't add a 'ti

Re: [Python-Dev] Core projects: 3to2

Terry Reedy udel.edu> writes: > > Some of the people who need to support both late 2.x and 3.x would > prefer to write 3.x code and backport. The OP of a current python-list > thread asked whether there was any way to write something like > > @alias('__nonzero__') > def __bool__(s

Re: [Python-Dev] Core projects for Summer of Code

Arc Riley wrote: > I've heard from four people that improving 2to3 would be a great project > (plus many more suggesting "port X to Python 3" as project ideas). > > Note the SoC timeline; > http://socghop.appspot.com/document/show/program/google/gsoc2009/timeline > > So maybe it won't work for 3.

Re: [Python-Dev] Core projects: 3to2

Antoine Pitrou wrote: Terry Reedy udel.edu> writes: Or the much requested 3to2 using the same tools. I didn't know there was such a request. I thought it was only a PyPy April fool. Some of the people who need to support both late 2.x and 3.x would prefer to write 3.x code and backport. T

Re: [Python-Dev] Core projects for Summer of Code

Arc Riley wrote: > On Wed, Mar 18, 2009 at 5:59 PM, Maciej Fijalkowski > wrote: > > I think we need to ask first guys who spend their live maintaining > libraries instead of just proposing "let's make some poor student port > it to py3k", but I might be just w

Re: [Python-Dev] Non-Core project: IDLE

On Wed, Mar 18, 2009 at 7:53 PM, Terry Reedy wrote: > IDLE needs lots of attention -- more than any one experienced person is > likely to have > > I've actually heard this from several people, IDLE on Py3 etc Who would be a good person to mentor such a project? __

Re: [Python-Dev] Non-Core project: IDLE

IDLE needs lots of attention -- more than any one experienced person is likely to have ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/

Re: [Python-Dev] What level of detail wanted for import and the language reference?

Benjamin Peterson schrieb: > 2009/3/16 Brett Cannon : >> At this point importlib is done for its public API for Python 3.1. That >> means it's time to turn my attention to making sure the semantics of import >> are well documented. But where to put all of the details? The language >> reference for

Re: [Python-Dev] Core projects for Summer of Code

2009/3/18 Arc Riley : > On Wed, Mar 18, 2009 at 6:13 PM, Brett Cannon wrote: >> >> I would double-check Benjamin can do this since I don't think he will be >> 18 by the time GSoC starts. The FAQ at >> http://socghop.appspot.com/document/show/program/google/gsoc2009/faqs#mentor_eligibility >> seems

Re: [Python-Dev] Core projects for Summer of Code

C. Titus Brown wrote: > On Wed, Mar 18, 2009 at 09:24:25PM +, Antoine Pitrou wrote: > -> Rather than performance, I think some more interesting areas would be > related to > -> some of the standard library modules. For instance, the unittest module > could > -> welcome some new features (test

Re: [Python-Dev] Core projects for Summer of Code

On Wed, Mar 18, 2009 at 7:23 PM, Daniel Fetchinson wrote: >> Hey guys/gals >> >> Summer of Code is ramping up.  Every year the common complaint is that not >> enough Python core projects get proposed by students, and of course a big >> reason for that is often the only encouragement we offer prosp

Re: [Python-Dev] Core projects for Summer of Code

On Wed, Mar 18, 2009 at 6:26 PM, Raymond Hettinger wrote: > Without help, it is going to take a long time to get many packages > converted to 3.x. I don't disagree, I just don't want to volunteer projects for something they don't want. Unless I misunderstand the situation, PIL doesn't seem app

Re: [Python-Dev] Core projects for Summer of Code

As a project maintainer I wouldn't want an intern being the most familiar person with our Py3 migration, I'd rather students stick with new features or optimization and coordinate the migration process as a group-wide effort. Without help, it is going to take a long time to get many packag

Re: [Python-Dev] Core projects for Summer of Code

> Hey guys/gals > > Summer of Code is ramping up. Every year the common complaint is that not > enough Python core projects get proposed by students, and of course a big > reason for that is often the only encouragement we offer prospective > students is a link to the PEP index. > > So let's make

Re: [Python-Dev] Core projects for Summer of Code

On Wed, Mar 18, 2009 at 6:13 PM, Brett Cannon wrote: > > I would double-check Benjamin can do this since I don't think he will be > 18 by the time GSoC starts. The FAQ at > http://socghop.appspot.com/document/show/program/google/gsoc2009/faqs#mentor_eligibilityseems > to suggest it won't be an i

Re: [Python-Dev] Core projects for Summer of Code

2009/3/18 Arc Riley > On Wed, Mar 18, 2009 at 5:59 PM, Maciej Fijalkowski wrote: > >> I think we need to ask first guys who spend their live maintaining >> libraries instead of just proposing "let's make some poor student port >> it to py3k", but I might be just wrong, I don't know. > > > I agree

Re: [Python-Dev] Core projects for Summer of Code

On Wed, Mar 18, 2009 at 14:56, Benjamin Peterson wrote: > 2009/3/18 Arc Riley : > >> > Note the SoC timeline; > >> > > >> > > http://socghop.appspot.com/document/show/program/google/gsoc2009/timeline > >> > > >> > So maybe it won't work for 3.1, but perhaps 3.1.1? 3.2? > >> > >> Well, there won't

Re: [Python-Dev] Core projects for Summer of Code

On Wed, Mar 18, 2009 at 5:59 PM, Maciej Fijalkowski wrote: > I think we need to ask first guys who spend their live maintaining > libraries instead of just proposing "let's make some poor student port > it to py3k", but I might be just wrong, I don't know. I agree. Part of Summer of Code is abo

Re: [Python-Dev] Core projects for Summer of Code

2009/3/18 Terry Reedy > R. David Murray wrote: > > How about improving 2to3? Seems like that could be an interesting, >> challenging, useful, and rewarding project :). >> > > Or the much requested 3to2 using the same tools. I'm not in a position to mentor this, but I too think this would be a

Re: [Python-Dev] Core projects for Summer of Code

> > While working on the core is admirable, I think gsoc would provide an > opportunity to port important Python libraries to 3.x. It's important > to remember that doing ports helps the core immensely by uncovering > 2to3 and py3k bugs. > Hello. It's a very noble task to have important python li

Re: [Python-Dev] Core projects for Summer of Code

On Wed, Mar 18, 2009 at 09:24:25PM +, Antoine Pitrou wrote: -> Rather than performance, I think some more interesting areas would be related to -> some of the standard library modules. For instance, the unittest module could -> welcome some new features (test discovery, support for skipped tes

Re: [Python-Dev] Core projects for Summer of Code

2009/3/18 Arc Riley : >> > Note the SoC timeline; >> > >> > http://socghop.appspot.com/document/show/program/google/gsoc2009/timeline >> > >> > So maybe it won't work for 3.1, but perhaps 3.1.1? 3.2? >> >> Well, there won't be any major changes in 3.1.1, but 3.2 is definitely >> open. > > Cool, the

Re: [Python-Dev] Core projects for Summer of Code

> > > Note the SoC timeline; > > > http://socghop.appspot.com/document/show/program/google/gsoc2009/timeline > > > > So maybe it won't work for 3.1, but perhaps 3.1.1? 3.2? > > Well, there won't be any major changes in 3.1.1, but 3.2 is definitely > open. Cool, these are of course details you can

Re: [Python-Dev] SoC: security

Tav organized a challenge to prove that its simple idea could be used to write a new "restricted python" module. Restart Python security is an huge project, but also an interesting project. http://tav.espians.com/a-challenge-to-break-python-security.html http://wiki.python.org/moin/Security --

Re: [Python-Dev] SoC: regex 2.7

There are different patches to improve regex library. You can start with: http://bugs.python.org/issue2636 I don't know that status of the issues, but it can be an interresting project. -- Victor Stinner aka haypo http://www.haypocalc.com/blog/ ___

Re: [Python-Dev] SoC: Optimize Python3

Hi, There are some very interresting issues about long type optimization: faster long multiplication http://bugs.python.org/issue3944 Asymptotically faster divmod and str(long) http://bugs.python.org/issue3451 Use 30-bit digits instead of 15-bit digits for Python integers. http://bugs.python.or

Re: [Python-Dev] Core projects for Summer of Code

2009/3/18 Arc Riley : > I've heard from four people that improving 2to3 would be a great project > (plus many more suggesting "port X to Python 3" as project ideas). Ok. That's excellent. > > Note the SoC timeline; > http://socghop.appspot.com/document/show/program/google/gsoc2009/timeline > > So

Re: [Python-Dev] Core projects for Summer of Code

I've heard from four people that improving 2to3 would be a great project (plus many more suggesting "port X to Python 3" as project ideas). Note the SoC timeline; http://socghop.appspot.com/document/show/program/google/gsoc2009/timeline So maybe it won't work for 3.1, but perhaps 3.1.1? 3.2? We

Re: [Python-Dev] Core projects for Summer of Code

Terry Reedy udel.edu> writes: > > Or the much requested 3to2 using the same tools. I didn't know there was such a request. I thought it was only a PyPy April fool. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listi

Re: [Python-Dev] Core projects for Summer of Code

R. David Murray wrote: How about improving 2to3? Seems like that could be an interesting, challenging, useful, and rewarding project :). Or the much requested 3to2 using the same tools. ___ Python-Dev mailing list Python-Dev@python.org http://mail.

Re: [Python-Dev] Core projects for Summer of Code

Hello Arc, Arc Riley gmail.com> writes: > > I've seen and heard that a lot of work is still needed on > http://svn.python.org /view/python/trunk both during the 3.1 release cycle, optimization possible all over the place. Well, first, it's too late for 3.1, which will (should) be out before Ju

Re: [Python-Dev] Core projects for Summer of Code

2009/3/18 Arc Riley : > Hey guys/gals Thanks for organizing this! > > Summer of Code is ramping up.  Every year the common complaint is that not > enough Python core projects get proposed by students, and of course a big > reason for that is often the only encouragement we offer prospective > stu

Re: [Python-Dev] Core projects for Summer of Code

On Wed, 18 Mar 2009 at 16:56, Arc Riley wrote: Summer of Code is ramping up. Every year the common complaint is that not enough Python core projects get proposed by students, and of course a big reason for that is often the only encouragement we offer prospective students is a link to the PEP in

[Python-Dev] Core projects for Summer of Code

Hey guys/gals Summer of Code is ramping up. Every year the common complaint is that not enough Python core projects get proposed by students, and of course a big reason for that is often the only encouragement we offer prospective students is a link to the PEP index. So let's make this year diff

Re: [Python-Dev] In-place operators

Martin v. Löwis wrote: Certainly, the doc string is wrong: isub(a, b) -- Same as a -= b. That's not quite the same - you would have to write a = isub(a, b) -- Same as a -= b. It seems a perfectly fine solution is simply to fix the docstring, exactly like that: a = isub(a, b) -- Same a

Re: [Python-Dev] In-place operators

Raymond Hettinger wrote: > > [Martin v. Löwis] >> I would object to their removal, though, >> because it would hurt my sense of symmetry. > > I wasn't going to propose removal. If everyone had > agreed that the operator in-place functions were > problematic, I was going to suggest moving their