Re: [Python-Dev] Tracker archeology

Daniel (ajax) Diniz wrote: > "Martin v. Löwis" wrote: >>> Now, getting into pie-in-the-sky territory, if someone (not logged in) >>> was to download all issues for scrapping and feeding to a local >>> database, what time of day would be less disastrous for the server? :) >> >> I think HTML scrapin

Re: [Python-Dev] Tracker archeology

"Martin v. Löwis" wrote: >> Now, getting into pie-in-the-sky territory, if someone (not logged in) >> was to download all issues for scrapping and feeding to a local >> database, what time of day would be less disastrous for the server? :) > > I think HTML scraping is a really bad idea. What is it

Re: [Python-Dev] Tracker archeology

> Now, getting into pie-in-the-sky territory, if someone (not logged in) > was to download all issues for scrapping and feeding to a local > database, what time of day would be less disastrous for the server? :) I think HTML scraping is a really bad idea. What is it that you specifically want to

Re: [Python-Dev] Tracker archeology

Brett Cannon wrote: > > > On Thu, Feb 12, 2009 at 16:45, Daniel (ajax) Diniz > wrote: > > Stephen J. Turnbull wrote: > > Reproduction really is the same thing as providing a test. > > That was where I got confused: many issues are easy to reproduce > ('

Re: [Python-Dev] Tracker archeology

On Thu, Feb 12, 2009 at 16:45, Daniel (ajax) Diniz wrote: > Stephen J. Turnbull wrote: > > Reproduction really is the same thing as providing a test. > > That was where I got confused: many issues are easy to reproduce > ('test'), but need some thinking to get automated tests right. > > urllib al

Re: [Python-Dev] Tracker archeology

Stephen J. Turnbull wrote: > Reproduction really is the same thing as providing a test. That was where I got confused: many issues are easy to reproduce ('test'), but need some thinking to get automated tests right. urllib always feels like this to me, except 'thinking' -> 'getting lost over and

Re: [Python-Dev] Tracker archeology

On Thu, Feb 12, 2009 at 16:22, Stephen J. Turnbull wrote: > Brett Cannon writes: > > > Sounds like a "*verify issue* stage is needed. Although I guess I kind > of > > assumed as part of the triage issue verification would happen as well, > but > > that might be too much as a single step. > > Ar

Re: [Python-Dev] Tracker archeology

Brett Cannon writes: > Sounds like a "*verify issue* stage is needed. Although I guess I kind of > assumed as part of the triage issue verification would happen as well, but > that might be too much as a single step. Are you confusing "reproduce" with "verify"? Remember, one of the three clas

Re: [Python-Dev] Tracker archeology

Martin v. Löwis wrote: >>> Oh, I realized that there is a component called "Unicode". So it should be >>> possible to write a request to list all issues related to unicode. >> >> Nice, I'll add set this component for issues that don't have it. I can >> still add people to these issues, if they want

Re: [Python-Dev] Tracker archeology

Brett Cannon wrote: > Sounds like a "*verify issue* stage is needed. Although I guess I kind of > assumed as part of the triage issue verification would happen as well, but > that might be too much as a single step. I'd rather think about it a bit more, available stages cover the vast majority of

[Python-Dev] patch to make IDLE load IDLESTARTUP/PYTHONSTARTUP on restart

I have submitted patches to idlelib/PyShell.py for Python 2.7 (Issue 5233) and 3.1 (5234), made against local repository copies as updated an hour ago. The purpose of the patch is to have IDLE load IDLESTARTUP or PYTHONSTARTUP on restart. Along the way I also made -s the default so IDLESTARTUP

[Python-Dev] .Idle.py init file

I was trying to disentangle some IDLE behavior today and discovered that If the user has a .Idle.py file IDLE will run it when it starts up. This is independent of running IDLESTARTUP or PYTHONSTARTUP when the -s switch is given. It is run by Tk.readprofile as called from Tk.__init__. The "Idle

[Python-Dev] Adding T_SIZET to structmember.h

After a rather long hacking on Cython in order to support 'Py_ssize_t' and 'size_t' the right way, I would like to propose the inclusion of a new T_SIZET in structmember.h in order to suport 'size_t' struct fields with PyMemberDef. Would such addition be accepted for 2.7 and 3.1? -- Lisandro Da

Re: [Python-Dev] 3.0.1 and 2.6.2

On Thu, Feb 12, 2009 at 1:57 PM, Barry Warsaw wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Feb 12, 2009, at 1:44 PM, Brett Cannon wrote: > >> What about the segfault problem? Shouldn't that get in? > > If it can be done without a regression, yes. Do it now and that will give >

Re: [Python-Dev] 3.0.1 and 2.6.2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 12, 2009, at 1:44 PM, Brett Cannon wrote: What about the segfault problem? Shouldn't that get in? If it can be done without a regression, yes. Do it now and that will give the buildbots time to run. If they go red, we'll back it out.

Re: [Python-Dev] Tracker archeology

>> Oh, I realized that there is a component called "Unicode". So it should be >> possible to write a request to list all issues related to unicode. > > Nice, I'll add set this component for issues that don't have it. I can > still add people to these issues, if they want. We can also add more com

Re: [Python-Dev] 3.0.1 and 2.6.2

On Thu, Feb 12, 2009 at 10:40, Barry Warsaw wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Feb 12, 2009, at 1:29 PM, Jesse Noller wrote: > > On Thu, Feb 12, 2009 at 1:20 PM, Antoine Pitrou >> wrote: >> >>> Jesse Noller gmail.com> writes: >>> I'm afraid I've gone bran

Re: [Python-Dev] 3.0.1 and 2.6.2

On Thu, Feb 12, 2009 at 1:40 PM, Barry Warsaw wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Feb 12, 2009, at 1:29 PM, Jesse Noller wrote: > >> On Thu, Feb 12, 2009 at 1:20 PM, Antoine Pitrou >> wrote: >>> >>> Jesse Noller gmail.com> writes: I'm afraid I've gone branch

Re: [Python-Dev] 3.0.1 and 2.6.2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 12, 2009, at 1:29 PM, Jesse Noller wrote: On Thu, Feb 12, 2009 at 1:20 PM, Antoine Pitrou wrote: Jesse Noller gmail.com> writes: I'm afraid I've gone branch-stupid. I have a a few changes that should be on the boat for the next relea

Re: [Python-Dev] Tracker archeology

On Thu, Feb 12, 2009 at 05:08, Daniel (ajax) Diniz wrote: > Brett Cannon wrote: > > One thing to keep an eye on for old issues, Daniel, is the Stage > > field. Setting that is nice for Bug Days as people can see what > > issues still need a test written or could use a review, etc. > > OK, I'll tr

Re: [Python-Dev] 3.0.1 and 2.6.2

On Thu, Feb 12, 2009 at 1:20 PM, Antoine Pitrou wrote: > Jesse Noller gmail.com> writes: >> >> I'm afraid I've gone branch-stupid. I have a a few changes that should >> be on the boat for the next release, but I can't for the life of me >> remember which branch to push to - right now the changes

Re: [Python-Dev] 3.0.1 and 2.6.2

Jesse Noller gmail.com> writes: > > I'm afraid I've gone branch-stupid. I have a a few changes that should > be on the boat for the next release, but I can't for the life of me > remember which branch to push to - right now the changes are on trunk > and py3k. The next release (3.0.1) is tomorro

[Python-Dev] 3.0.1 and 2.6.2

I'm afraid I've gone branch-stupid. I have a a few changes that should be on the boat for the next release, but I can't for the life of me remember which branch to push to - right now the changes are on trunk and py3k. -jesse ___ Python-Dev mailing list

[Python-Dev] [issue2263] struct.pack() + numpy int raises SystemError

hello, i took a look at unassigned open issue with the oldest activity this happened to be issue2263 Original bug report: struct.pack() raises SystemError when fed a numpy integer in some cases. The following was run on MacOSX 10.4, little endian (I can only reproduce the error if I speci

Re: [Python-Dev] Tracker archeology

Victor Stinner wrote: > Oh, I realized that there is a component called "Unicode". So it should be > possible to write a request to list all issues related to unicode. Nice, I'll add set this component for issues that don't have it. I can still add people to these issues, if they want. Daniel ___

Re: [Python-Dev] multiprocessing not compatible with functional.partial

On Feb 12, 2009, at 10:58 AM, Neal Becker wrote: Is it possible to get a better error message (regarding the pickle- ability)? Sure, most of the time it does have a better error msg. ___ Python-Dev mailing list Python-Dev@python.org http://mail

Re: [Python-Dev] multiprocessing not compatible with fu nctional.partial

Is it possible to get a better error message (regarding the pickle-ability)? ___ 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/archive%40m

Re: [Python-Dev] multiprocessing not compatible with functional.partial

Hrvoje Niksic wrote: > Calvin Spealman wrote: >> I don't think it would be unreasonable to consider either 1) making >> functools.partial picklable (I don't know how feasible this is) > > It's not only feasible, but quite easy and, I think, useful. A > "partial" instance is a simple triplet of (

Re: [Python-Dev] multiprocessing not compatible with functional.partial

Calvin Spealman wrote: I don't think it would be unreasonable to consider either 1) making functools.partial picklable (I don't know how feasible this is) It's not only feasible, but quite easy and, I think, useful. A "partial" instance is a simple triplet of (function, args, kwds), and it c

Re: [Python-Dev] multiprocessing not compatible with functional.partial

On Thu, Feb 12, 2009 at 9:22 AM, Calvin Spealman wrote: > On Thu, Feb 12, 2009 at 9:06 AM, Christian Heimes wrote: >> Neal Becker schrieb: >>> If the argument to pool.map (f, args) >>> is >>> f = functional.partial (my_func, some_keyword_arg=whatever) >>> >>> I get: >>> >>> Traceback (most recent

Re: [Python-Dev] multiprocessing not compatible with functional.partial

On Thu, Feb 12, 2009 at 9:06 AM, Christian Heimes wrote: > Neal Becker schrieb: >> If the argument to pool.map (f, args) >> is >> f = functional.partial (my_func, some_keyword_arg=whatever) >> >> I get: >> >> Traceback (most recent call last): >> File "/usr/lib/python2.5/site-packages/multiproce

Re: [Python-Dev] multiprocessing not compatible with functional.partial

Neal Becker schrieb: > If the argument to pool.map (f, args) > is > f = functional.partial (my_func, some_keyword_arg=whatever) > > I get: > > Traceback (most recent call last): > File "/usr/lib/python2.5/site-packages/multiprocessing-2.6.1.1-py2.5-linux- > self.run() > File "/usr/lib/pyt

[Python-Dev] multiprocessing not compatible with functional.partial

If the argument to pool.map (f, args) is f = functional.partial (my_func, some_keyword_arg=whatever) I get: Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/multiprocessing-2.6.1.1-py2.5-linux- self.run() File "/usr/lib/python2.5/site-packages/multiprocessing-2.6.

Re: [Python-Dev] Tracker archeology

Le Thursday 12 February 2009 14:10:32, vous avez écrit : > Victor Stinner wrote: > > I like everything related to Unicode and the separation of byte and > > character strings in Python3 :-) > > That's a big one. But Ezio Melotti already asked for Unicode, so I > have some 75 issues selected and re

Re: [Python-Dev] Tracker archeology

Victor Stinner wrote: > I like everything related to Unicode and the separation of byte and character > strings in Python3 :-) That's a big one. But Ezio Melotti already asked for Unicode, so I have some 75 issues selected and ready to add you two to, but I'll do it later today or after 3.0.1 tom

Re: [Python-Dev] Tracker archeology

Senthil Kumaran wrote: > For urllib,urllib2 and urlparse related, please add me (orsenthil) to > nosy list. I should already there. > I shall test and provide patches. Great! I always find it harder to test urllib[x] than to fix the bug. I'm in the process of gluing some tools and scripts together

Re: [Python-Dev] Tracker archeology

Brett Cannon wrote: > One thing to keep an eye on for old issues, Daniel, is the Stage > field. Setting that is nice for Bug Days as people can see what > issues still need a test written or could use a review, etc. OK, I'll try to set a useful Stage for bugs I edit. I'll reread your blog post on

Re: [Python-Dev] Python 3.0.1 planned for this Friday, Feb 13

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 12, 2009, at 7:52 AM, Benjamin Peterson wrote: On Thu, Feb 12, 2009 at 6:28 AM, Daniel (ajax) Diniz wrote: Barry Warsaw wrote: A quick reminder that I am planning to release Python 3.0.1 this Friday, February 13. Cool :) Should I hold

Re: [Python-Dev] Python 3.0.1 planned for this Friday, Feb 13

On Thu, Feb 12, 2009 at 6:28 AM, Daniel (ajax) Diniz wrote: > Barry Warsaw wrote: >> A quick reminder that I am planning to release Python 3.0.1 this Friday, >> February 13. > > Cool :) > > Should I hold the tracker cleanup until then (the posting part, not > the searching)? I'd hate to bury some

Re: [Python-Dev] Python 3.0.1 planned for this Friday, Feb 13

Barry Warsaw wrote: > A quick reminder that I am planning to release Python 3.0.1 this Friday, > February 13. Cool :) Should I hold the tracker cleanup until then (the posting part, not the searching)? I'd hate to bury some important report in a sea of ancientness. Daniel PS: Are you aiming at

Re: [Python-Dev] test_tk failing

On Thu, Feb 12, 2009 at 6:59 AM, Raymond Hettinger wrote: > C:\py27>py27 lib\test\regrtest.py -uall test_tk > test_tk > test test_tk failed -- Traceback (most recent call last): > File "c:\py27\lib\lib-tk\test\test_tkinter\test_text.py", line 32, in > test_search > self.failUnlessEqual(text.sea

[Python-Dev] test_tk failing

C:\py27>py27 lib\test\regrtest.py -uall test_tk test_tk test test_tk failed -- Traceback (most recent call last): File "c:\py27\lib\lib-tk\test\test_tkinter\test_text.py", line 32, in test_search self.failUnlessEqual(text.search('-test', '1.0', 'end'), '1.2') AssertionError: != '1.2' 1 test

Re: [Python-Dev] Tracker archeology

Hi Daniel, > Good: > Many requested assignments: > Thanks everyone that asked for bugs. If anyone else wants more, > just let me know :) I like everything related to Unicode and the separation of byte and character strings in Python3 :-) I already have some pending issues.. -- Victor St