Stalled ticket in Python bug tracker

[Steven D'Aprano]

I'm interested in this ticket in the bug tracker:

http://bugs.python.org/issue2527

but it seems to have been stalled for nine months. Is there a procedure
for starting it up again? Should I ask about it on the python-dev mailing
list, or just wait until somebody happens to notice it?

Peter Otten, if you're reading this, is your offer to jump through the
necessary hoops still standing?

 

[skip]

Steven> I'm interested in this ticket in the bug tracker:

Steven> http://bugs.python.org/issue2527

Steven> but it seems to have been stalled for nine months. Is there a
Steven> procedure for starting it up again?

Assign it to yourself? Add a comment with relevant updates?

Steven> Should I ask about it on the python-dev mailing list, or just
Steven> wait until somebody happens to notice it?

But you've already noticed it. ;-)

Skip

 

[Benjamin Peterson]

I'm interested in this ticket in the bug tracker:

http://bugs.python.org/issue2527

but it seems to have been stalled for nine months. Is there a procedure
for starting it up again? Should I ask about it on the python-dev mailing
list, or just wait until somebody happens to notice it?

Nobody is likely to notice it unless someone pushes forward with it. Non release
critical bug reports and feature requests tend to fall down a black hole after
about a week.

 

[Steven D'Aprano]

Steven> I'm interested in this ticket in the bug tracker:

Steven> http://bugs.python.org/issue2527

Steven> but it seems to have been stalled for nine months. Is there
a Steven> procedure for starting it up again?

Assign it to yourself? Add a comment with relevant updates?

Steven> Should I ask about it on the python-dev mailing list, or
just Steven> wait until somebody happens to notice it?

But you've already noticed it. ;-)

(Note to self: stop posting ambiguous messages when tired.)


I meant bringing it to the attention of somebody who can actually commit
the patch to production, or rule that the patch isn't suitable. I can't
do that.

Sorry for the naive questions, I'm new to the bug tracker and I'm not
entirely sure about the protocol. Should I just drop a note to python-dev
and ask somebody with commit privileges to look at it, or is that rude?

 

[Terry Reedy]

You seem to have missed or not understood this answer. See below.

(Note to self: stop posting ambiguous messages when tired.)


I meant bringing it to the attention of somebody who can actually commit
the patch to production, or rule that the patch isn't suitable. I can't
do that.

However, you can do something to move it forward.

1. There were some suggested changes to the patch but no revised version
uploaded. What do *you* think of them?

2. The patch is small enough that you could apply it by hand, with or
without any further changes, to a copy of timeit.py on your system.

3. The patch is against python2.5. Test it with 2.6 and 3.0 with the
current test file in Lib/test.

4. The patch lacks any test of the new feature. Write one that could be
added to the current test file.

5. The patch lack documentation of the new feature. Write a entry that
could be added to the current timeit module doc.

6. Ask the OP to incorporate the test and doc in the appropriate file
and generate and post a new diff patch.

The patch as is is unacceptable without the test and doc.

Sorry for the naive questions, I'm new to the bug tracker and I'm not
entirely sure about the protocol. Should I just drop a note to python-dev
and ask somebody with commit privileges to look at it, or is that rude?

Slightly rude, perhaps, but more importantly, without volunteer work on
your part, probably useless. Everyone else is a volunteer also.

tjr

 

[skip]

Steven> I meant bringing it to the attention of somebody who can
Steven> actually commit the patch to production, or rule that the patch
Steven> isn't suitable. I can't do that.

Perhaps not, but you can help the process along by adding your perspective.
Does it solve a problem you have? Does it run on your platform? Can you
provide further examples? Can you add missing parts to what's already there
(doc changes, test cases)?

These are general questions which won't be appropriate for every issue in
the tracker, but are some ways Python users without checkin privileges can
help the development process.

Steven> Sorry for the naive questions, I'm new to the bug tracker and
Steven> I'm not entirely sure about the protocol. Should I just drop a
Steven> note to python-dev and ask somebody with commit privileges to
Steven> look at it, or is that rude?

You might want to peruse some of the links on this page:

http://www.python.org/dev/

That might give you some insight into the Python development process and how
you fit into it.

 

[Peter Otten]

I'm interested in this ticket in the bug tracker:

http://bugs.python.org/issue2527

but it seems to have been stalled for nine months. Is there a procedure
for starting it up again? Should I ask about it on the python-dev mailing
list, or just wait until somebody happens to notice it?

Peter Otten, if you're reading this, is your offer to jump through the
necessary hoops still standing?

I guess what killed any chance for the patch to be included was that there
was a "competing" patch that I asked to be reversed. Also, just saying that
you are willing to provide docs and test didn't work either.

What's needed then as a 'sine qua non' is an updated patch against the tip
with documentation and tests.

If you don't beat me to it I may give it another try, but probably not
before next month.

Peter