[Sorry for stepping in so late]
On Thu, Feb 12 2009 at 02:05:23PM BRST, Daniel (ajax) Diniz
aja...@gmail.com wrote:
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
But no way to share aggregated search results (I've sent some
off-list), 'follow' users (i.e., be added as nosy for issues where
user A is nosy), auto-add as nosy based on keywords, etc. Someday we
could have these nosy features hosted externally, e.g. as an AppEngine
app that subscribes to
Daniel (ajax) Diniz schrieb:
Over-spammig:
Sorry, Georg! I only noticed all issues in the Documentation
component are auto-assigned to you today. This meant dozens of unasked
for assignments :-/
That's okay, I'll go through them at the weekend and just unassign what
I won't manage to do.
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 interface is pretty good for handling individual
issues,
Brett Cannon wrote:
On Thu, Feb 12, 2009 at 16:45, Daniel (ajax) Diniz aja...@gmail.com 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 so it's short and to the point and you
For starters, free form searches, aggregation and filtering of
results.
What is free form searches (example)? What is aggregation?
What results do you want to filter? (roundup can already filter
results quite well)
The web interface is pretty good for handling individual
issues, but not so
Send emails before they were done :D
Again: what's that?
Use a VCS for in-progress activities
Hmm. Why do you need a database copy for that?
Figure out how to serialize and submit the work done locally
Again, don't understand. too brief.
Share results with interested parties
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 to filter?
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 mailing list
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
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 ready to
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
On Thu, Feb 12, 2009 at 05:08, Daniel (ajax) Diniz aja...@gmail.com 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,
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 components
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 the
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.
We can
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 classes for
On Thu, Feb 12, 2009 at 16:22, Stephen J. Turnbull step...@xemacs.orgwrote:
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
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
On Thu, Feb 12, 2009 at 16:45, Daniel (ajax) Diniz aja...@gmail.com 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.
Brett Cannon wrote:
On Thu, Feb 12, 2009 at 16:45, Daniel (ajax) Diniz aja...@gmail.com
mailto:aja...@gmail.com 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
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 scraping is a really
On Wed, Feb 11, 2009 at 12:46 AM, Stephen Thorne step...@thorne.id.au wrote:
On 2009-02-10, Tarek Ziadé wrote:
On Tue, Feb 10, 2009 at 2:23 PM, Daniel (ajax) Diniz aja...@gmail.com
wrote:
If anyone is interested in being added as nosy for any category of
bugs, let me know and I'll do
[Daniel (ajax) Diniz]
Now will I'll start verifying, adding tests, updating or closing as
needed the recently changed old issues, until I've taken a good look
at these. Then, if there's still time left before Saturday, I'll focus
on verifying/flagging more ancient ones.
Thanks for your
2009/2/11 Daniel (ajax) Diniz aja...@gmail.com
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
+1 on the cleanup: reading the bug description of
http://bugs.python.org/issue1533164, this will also help Jython. Now I know
why we see scenarios of package with setup.cfg with optimize=1:
Indeed, this is a well-known issue. Many packages put an optimize=1 in
their setup.cfg in order to solve
Jim Baker wrote:
+1 on the cleanup: reading the bug description of
http://bugs.python.org/issue1533164, this will also help Jython. Now I
know why we see scenarios of package with setup.cfg with optimize=1:
Indeed, this is a well-known issue. Many packages put an optimize=1 in
their setup.cfg
On Thu, Feb 12, 2009 at 4:11 AM, Daniel (ajax) Diniz aja...@gmail.com wrote:
Now will I'll start verifying, adding tests, updating or closing as
needed the recently changed old issues, until I've taken a good look
at these. Then, if there's still time left before Saturday, I'll focus
on
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
2009/2/10 Daniel (ajax) Diniz aja...@gmail.com:
If anyone is interested in being added as nosy for any category of
bugs, let me know and I'll do that as I scan the tracker.
Anything related to Decimal, add me.
Thanks!
--
.Facundo
Blog: http://www.taniquetil.com.ar/plog/
PyAr:
Thanks Daniel! This kind of work is never fun but very much needed and
I'm very glad you did it. A round of applause!!
On Tue, Feb 10, 2009 at 5:23 AM, Daniel (ajax) Diniz aja...@gmail.com wrote:
Hi all,
For the past two days I've been doing some housekeeping
*cough*spamming*cough* on the
On Tue, Feb 10, 2009 at 05:23, Daniel (ajax) Diniz aja...@gmail.com wrote:
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,
On Tue, Feb 10, 2009 at 8:23 AM, Daniel (ajax) Diniz aja...@gmail.com wrote:
If anyone is interested in being added as nosy for any category of
bugs, let me know and I'll do that as I scan the tracker.
Adding/assigning to me on 2to3 bugs is fine, but usually I notice
stuff I'm interested in as
On Tue, Feb 10, 2009 at 05:23, Daniel (ajax) Diniz aja...@gmail.com wrote:
[SNIP]
Iff this kind of Bug-Day-ish work is desirable, doesn't disrupt real
work and people agree the workflow would be better, I'd like to have
developer rights in the tracker, as per Antoine's suggestion. FWIW, I
On Tue, Feb 10, 2009 at 2:23 PM, Daniel (ajax) Diniz aja...@gmail.com wrote:
If anyone is interested in being added as nosy for any category of
bugs, let me know and I'll do that as I scan the tracker.
I'll take Distutils related issues,
Thank you
Tarek
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 import
On 2009-02-10, Tarek Ziadé wrote:
On Tue, Feb 10, 2009 at 2:23 PM, Daniel (ajax) Diniz aja...@gmail.com wrote:
If anyone is interested in being added as nosy for any category of
bugs, let me know and I'll do that as I scan the tracker.
I'll take Distutils related issues,
If you could
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 themselves
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
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,
42 matches
Mail list logo
