Hi all,
For the past two days I've been doing some housekeeping
*cough*spamming*cough* on the tracker, mostly on ancient and/or easy
bugs. So far, ten bugs have been closed (thanks Antoine, Barry,
Benjamin, Guilherme, Martin and Raymond). I nominated some other bugs
(below) for closing and added a
Brett Cannon wrote:
> OK, three enthusiastic votes to give them is plenty for me. You should have
> the Developer role now, Daniel. Let me know if I screwed up at all in
> switchng the role on for you.
Thanks a lot! Looks like it worked fine :)
Let me try the new thing, then: warnings and impor
Hi Raymond,
Thanks a lot for the feedback. I actually am more than a bit concerned
about the effect of my wholesale edits on the signal to noise ration.
Any clarifications are most welcome (and I'm open to change methods
and immediate goals) :)
Raymond Hettinger wrote:
> ISTM, that when closing du
Brett Cannon wrote:
> Warnings and import for me.
Done. Tomorrow I'll see what I can triage/test in those.
>> Talking about Bug Days, I see lots of easy bugs, some with outdated
>> patches. Is there any plan of doing a Bug Day around PyCon time?
>
> Well, the sprints at PyCon are Bug Days themsel
Tarek Ziadé wrote:
> I'll take Distutils related issues,
Done. Since Akira Kitada is helping with many distutils issues, I'll
skip looking at them for now. Ping me if you need tests or simple
patches :)
Regards,
Daniel
___
Python-Dev mailing list
Python
Benjamin Peterson wrote:
> Adding/assigning to me on 2to3 bugs is fine, but usually I notice
> stuff I'm interested in as it rises to the top.
Done, found a couple more. There are also some -3 warnings open, if
that interests you :)
Thanks for the support, I only saw it was a +10 now :D
Cheers,
Hi,
Here's a status report about the digging. Thanks Benjamin, Antoine,
Martin, Raymond, Guilherme, Georg, Brett, Mark and everyone else for
helping :)
Good:
Many requested assignments:
Thanks everyone that asked for bugs. If anyone else wants more,
just let me know :)
Old issues closed
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
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
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
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
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
___
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
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
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
"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
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 disastro
Daniel (ajax) Diniz wrote:
> "Martin v. Löwis" wrote:
>> I think HTML scraping is a really bad idea. What is it that you
>> specifically want to do with these data?
>
> For starters, free form searches, aggregation and filtering of
> results. The web int
Brett Cannon wrote:
> On Thu, Feb 12, 2009 at 16:45, Daniel (ajax) Diniz wrote:
>> I have to test my patch against a good
>> representation of the issue, regression tests must pass, 'automated
>> test needed' fits well :)
>
> Go with "Unit test needed&qu
Steve Holden wrote:
> Can I just say (without in any way wanting to get involved in what might
> be considered as "work") that it's encouraging the tracker received a
> bit more TLC we might eventually be able to see at least the occasional
> week where the issue count increment was negative :)
Th
Hi Martin,
Sorry about being so brief, I got a lot of unexpected interruptions
and was rushing things.
"Martin v. Löwis" wrote:
>> For starters, free form searches, aggregation and filtering of
>> results.
>
> What is "free form searches" (example)? What is aggregation?
> What results do you want
Daniel (ajax) Diniz wrote:
> Status report and roadmap to be posted later today, before date +%s
> turns 1234567890 :)
Missed that and got almost no tracker work done. Postponed to Monday,
after some weekend cleaning.
Daniel
___
Python-Dev mailin
Terry Reedy wrote:
> Can http://bugs.python.org/issue995458
> "Does not build selected SGI specific modules"be closed?
>
> PEP11 lists Irix 4 as gone. What about Irix 6?
> http://www.python.org/dev/peps/pep-0011/
Thank you, thank you, thank you :)
Can I close these other IRIX issues?
http://bug
Hi,
In the discussion of a feature request for MacPython[1], the OP (hhas) said:
As of Python 2.6/3.0, all Mac-specific modules are deprecated/eliminated
from the standard library and there are no longer any plans to submit
appscript for possible inclusion. This issue should be reject
Mitchell,
I can't find the string ".Idle.py" in trunk. If you haven't already,
please open a documentation issue for this one. I don't see any
obvious downside to this behavior and people might be relying on it by
now.
Thanks for reporting these IDLE issues!
Daniel
_
Looks like the MDS ate the copy sent to the list, here's it again:
Brett Cannon wrote:
> As of Python 2.6 everything Mac-specific is deprecated and in 3.0 they
> are gone (you can read PEP 3108 for the details or just note that the
> Mac/Modules directory is gone in 3.0). They will still be around
Daniel (ajax) Diniz wrote:
> Can I close these other IRIX issues?
>
> http://bugs.python.org/issue2048
> http://bugs.python.org/issue1086642
> http://bugs.python.org/issue1178510
> http://bugs.python.org/issue1070140
So, I'll close these later this week (citing that &q
Hi,
I've marked some issues (25 now) to close, mostly because:
- there was no reply from OP, nor a clear justification for the issue;
- there are messages explaining why the issue is invalid;
- the OSes/versions of the report suggest the issue is currently invalid;
However, I've been mistaken abou
M.-A. Lemburg wrote:
>> http://bugs.python.org/issue1231081 platform.processor() could be smarter
Thanks, Marc-Andre!
If anyone else feels like closing some of these issues, go ahead (no
need to report back, I'll find it out later). My rather bureaucratic
approach is just to avoid a possible trig
Hi,
Here's a summary of what's been accomplished and what's almost done.
This kinda marks the end of this Bug Season for me, but I'd like to do
at least one more installment before PyCon.
We have closed 51 issues so far (sorry if I missed some):
* Barry
** Benja
This is the janitorial plan I mentioned earlier...
It's so humongously huge by now that I'm not sure whether I should
submit it to e.g. the Python Papers or just print it and set it on
fire and run screaming. Fortunately, a tl;dl summary is provided :)
Daniel
Summary
Let's improve the tracker UI
Paul Moore wrote:
> 2009/2/16 Daniel (ajax) Diniz :
>> Hi,
>> Here's a summary of what's been accomplished and what's almost done.
>> This kinda marks the end of this Bug Season for me, but I'd like to do
>> at least one more installment before PyC
Hi Ned,
Ned Deily wrote:
> Other than Mac/Modules, the rest of the Mac/ directory is mainly stuff
> used for building or going into the OS X installer images, including
> things like IDLE.app. These are used in 2.x and in 3.x.
Thanks, knowing that makes the ticket handling easier!
>> There are
Hi, Ronald,
Ronald Oussoren wrote:
>
> On 15 Feb, 2009, at 21:13, Daniel (ajax) Diniz wrote:
>
>> Hi,
>>
>> In the discussion of a feature request for MacPython[1], the OP (hhas) said:
>>
>> As of Python 2.6/3.0, all Mac-specific modules are deprecated/el
Brett Cannon wrote:
>
> Ditto from me! And I will eventually get to the bugs assigned to me
> (hopefully starting some time this week).
>
No hurry, just let me know if you see stupid mistakes on my part (I've
once or twice added an issue as its own dependency) :)
Daniel
_
Jack Jansen wrote:
> I had a cursory look at these issues as they came by, and I didn't see any
> that struck me as still being relevant.
>
Thanks a lot for the feedback, Jack!
Daniel
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python
John J Lee wrote:
> On Mon, 16 Feb 2009, Daniel (ajax) Diniz wrote:
>>
>> http://bugs.python.org/issue809887 Improve pdb breakpoint feedback
>
> Why this one?
Nice catch, this makes no sense. The patch even applies almost
cleanly. I'll update it and set the oth
Hi Venkatraman,
Venkatraman S wrote:
>
> On Tue, Feb 17, 2009 at 1:45 PM, "Martin v. Löwis" wrote:
>>
>> Don't expect too much
>> help from other people - I have been waiting for volunteers to show up
>> helping with the tracker for more than a year now.
>
> I have been mostly a silent spectator
Python tracker wrote:
>
> ACTIVITY SUMMARY (02/13/09 - 02/20/09)
> Python tracker at http://bugs.python.org/
[...]
> 2341 open (+55) / 14813 closed (+27) / 17154 total (+82)
I was about to cry foul, +27 closed? We closed so many issues last
week, how come?
Then, I realized the headings tell anot
Antoine Pitrou wrote:
> Guido van Rossum python.org> writes:
>> The svn history of those lines may have more pointers.
>
> Well this code dates back to the first checkin in the py3k branch. Apparently
> the old p3yk branch is not there anymore...
The history is available (see below), but tells no
print '''
tav wrote:
> Daniel emailed in the exploit below and it is pretty devastating. It
> takes advantage of the fact that the warnings framework in 2.6+
> dynamically imports modules without being explicitly called!!
Here's one I couldn't develop to a working exploit, but think is promising.
Hi,
Benjamin Peterson wrote:
> 3.1a1 March 7
> 3.1a2 April 4
> 3.1b1 May 2
> 3.1rc1 May 30
> 3.1rc2 June 13
> 3.1 Final June 27
Benjamin, I'd like to nominate a couple (minor) RFEs[1] and bug
fixes[2] for 3.1. By 'nominate' I mean 'group related issues together,
offer tests, docs, patches and/or
Mitchell L Model wrote:
> Would whoever is responsible for IDLE please take a look at the patches
> I submitted for Python 2 & 3 [tracker IDs 5233 and 5234 respectively].
[...]
> I would really like to see them in 3.1. The patch is already there;
> someone just has to do whatever gets done with pat
Hi,
Here's a progress report on the "let's make the tracker a bit better" tasks.
Note: if you make use of saved queries, I recommend reading the
'anyone can remove any queries' issue:
http://psf.upfronthosting.co.za/roundup/meta/issue244
Feedback on meta-tracker open issues, as well as new RFEs a
Jesse Noller wrote:
> Slightly off topic Daniel, but if you see any multiprocessing bugs
> lurking out there, can you make me (jnoller) the assignee?
Sure!
FWIW, I've just submitted a patch[1] that will make working with
arbitrary issue sets much saner and should have a 'mass-add user X as
nosy
CC'ing python-dev, as more RFEs might be uncovered :)
Daniel (ajax) Diniz wrote:
> Martin v. Löwis wrote:
>> I think a patch (or full file) would be good enough. We could put it
>> into the tracker itself, and publish it prominently where people
>> upload files.
>
&g
Hi Tennessee,
I plan to take a look at all open issues before PyCon, do you want to
join forces? :)
Tennessee Leeuwenburg wrote:
> I am beginning reviewing some more issues in the tracker. I think it would
> be useful to have the following status options (new status options marked
> with a '+'):
Terry Reedy wrote:
> The other problem with too many specifics is non-use. As it is, an issue is
> sometimes closed with no resolution marked, so one has to scroll down,
> possibly a long way, to see whether it was accepted or rejected. (Is it
> possible to require a resolution when closing?)
Y
Tennessee Leeuwenburg wrote:
> I am continuing to look at issues in the issue tracker. It would be handy to
> be able to update some of the metadata fields. For contributions, it's fine
> to just be able to upload patches / post messages, but I can see any number
> of issues which could use a bit o
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
Hi,
I'd like to propose a two housecleaning GSoC ideas for discussion,
they both need mentors. First, Mark's suggested overhaul of the struct
module, along with finishing PEP 3118 if possible. Second, a clean up
of the socket module, along with checking its usage in the stdlib if
possible. Details
Martin v. Löwis wrote:
> In addition, I would like to see a specification of the exact labels to
> be used, plus a one-line description that should be attached to the
> labels.
Tennessee,
If you'd like to test those additional status options, I'm setting a
test instance of the Python tracker up at
Hi,
I'd like to bring up the general idea of using a PSF slot in GSoC2009
to improve the Python development infrastructure. I also happen to
have two concrete proposals for that (such a coincidence!). But I
assure you the general idea is more important than my proposals :)
General:
Solving issues
C. Titus Brown wrote:
> Given the relative paucity of core Python GSoC ideas, I think you should
> go for both of these, *especially* if you have a mentor up front. So,
> write 'em up, add 'em to the GSoC page, and let's see who we get...
> If we get good applications for both, then I think we can
Thanks for the feedback, Antoine!
Antoine Pitrou wrote:
> Daniel (ajax) Diniz gmail.com> writes:
>>
>> Sometimes, non-obvious bits like the right sequence of svnmerge
>> commands, the right way to link a Rietveld code review to a given
>> issue or checking for
Nick Coghlan wrote:
> Everything I've seen from Daniel so far seems to be about either making
> things we already do more efficient, or else providing additional
> features in ways that don't make the tools any more confusing for others
> already used to a particular way of doing things. So he seem
"Martin v. Löwis" wrote:
> Yes, I'm also quite grateful for the contributions I have received from
> Daniel.
Thank you Martin. I'm sure I'd still be going around in circles if it
weren't for your guidance, and I'd be MIA after the first time I broke
the tracker too. So thanks a lot for the support
Antoine Pitrou wrote:
> Well, it seems to me that most of these steps are separated by manual
> intervention (e.g. compile and run the test suite to check that everything
> works
> smoothly)
Agreed.
> so there's no real point in making a script out of them.
The idea would be to provide scripts
R. David Murray wrote:
> I understood from posts I saw go by earlier from Daniel that 'pending'
> meant 'close pending unless there is feedback to the contrary' (and I
> just used it that way). It sounds like that is indeed correct but not
> universally known, and thus I would suggest that at a mi
This proposal has two main goals: making the Python bug tracker more
efficient for core developers and improving Roundup in areas that
don't directly concern the PSF trackers. Most of the code would land
in Roundup's repositories, but many instance-level changes would be
specific to our tracker.
Aahz wrote:
> Is this for GSoC? If yes, please make sure to include that tag in the
> Subject: line to make it easier to track.
Oops, makes a lot of sense :)
Daniel
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listin
Hi,
I've just left the soc2009-mentors list on request, as I'm not a
mentor. So if you need my input on the mentor side regarding ideas
I've contributed to [1] (struct, socket, core helper tools or
Roundup), please CC me.
Best regards,
Daniel
[1] http://wiki.python.org/moin/SummerOfCode/2009/Inco
"Martin v. Löwis" wrote:
>> I think it would be a good idea to host a temporary svn mirrors for
>> developers who accesses their VCS via an IDE. Although, I am sure
>> anymore if supporting these developers (if there are any) would worth
>> the trouble. So, think of this as optional.
>
> Any decisi
Dirkjan Ochtman wrote:
> One of the nicer features of Mercurial/DVCSs, in my experience, is
> that non-committers get to keep the credit on their patches. That
> means that it's impossible to enforce a policy more extensive than
> some basic checks (such as the format above). Unless we keep a list
Hi,
As discussed before, I have put two mock Python Tracker instances online.
The Test[1] instance follows bugs.python.org code, so we can test
bugfixes and procedures without breaking the real tracker. The
Experimental[2] one, aka the cool instance, is where new features are
showcased.
Currently
On Thu, Apr 10, 2008 at 12:10 PM, Rodrigo Bernardo Pimentel
<[EMAIL PROTECTED]> wrote:
> On Wed, Apr 09 2008 at 11:12:58AM BRT, Trent Nelson <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > Is there another online sprint/bugfix day in the pipeline? If not, can
> > there be? ;-)
>
> +1.
>
> The Sao
Alexandre Vassalotti wrote:
> The logs of failing test runs all shows the same error message:
>
> [31481 refs]
> * ob
> object :
> type: str
> refcount: 0
> address : 0x3a97728
> * op->_ob_prev->_ob_next
> object :
> type: str
> refcount: 0
> address : 0x3a97728
> * op->_ob_next->_ob_pr
Georg Brandl wrote:
>
> This only occurs --with-pydebug, I assume?
For me, on 32 bits Linux, yes, only --with-pydebug*.
> It is the same basic problem as in http://bugs.python.org/issue3299,
> which I analysed some time ago.
Yes, I guess my 'catch' is exactly that. But it might be a red herring
Tres Seaver wrote:
> Brett Cannon wrote:
>> No because you are getting back the repr for the bytes object. Str
>> does not know what the encoding is for the bytes so it has no way of
>> performing the decoding.
>
> The encoding information *is* available in the response headers, e.g.:
[snip]
That'
69 matches
Mail list logo
