Am 26.04.2010 15:34, schrieb Lennart Regebro:
> On Mon, Apr 26, 2010 at 12:58, Stephen J. Turnbull wrote:
>> It is entirely *not* evident to me that it's too hard to get
>> privileges in the Python development community (Python's development
>> process works -- and it works really well by comparis
On Tue, Apr 27, 2010 at 09:18, Georg Brandl wrote:
> Am 26.04.2010 15:34, schrieb Lennart Regebro:
>> Yes, but only when the checkin was wrong. For all other checkins, it's
>> *less* work. Hence, a committer needs to basically fudge up every
>> second checkin to cause more work than he relieves wo
On Tue, Apr 27, 2010 at 1:24 AM, Toshio Kuratomi wrote:
> On Mon, Apr 26, 2010 at 05:46:55PM -0400, Barry Warsaw wrote:
>> On Apr 26, 2010, at 09:39 PM, Tarek Ziadé wrote:
>>
>> >You should be permissive on that one. Until we know how to describe resource
>> >files properly, __file__ is what devel
On Tue, Apr 27, 2010 at 2:43 AM, David Cournapeau wrote:
> On Tue, Apr 27, 2010 at 5:10 AM, Piotr Ożarowski wrote:
>
>> if there's no other way (--install-data is ignored right now, and I know
>> you're doing a great work to change that, thanks BTW), one could always
>> use it in *one* place and
On Mon, 26 Apr 2010 14:15:01 -0400, Steve Holden wrote:
> Antoine Pitrou wrote:
> > Steven D'Aprano pearwood.info> writes:
> >> Who are we worried about offending? The crowds on the Internet who never
> >> volunteer for anything, who never submit patches, let alone offer to do
> >> the unglamou
Terry Reedy udel.edu> writes:
>
> On 4/26/2010 11:09 AM, Alexander Belopolsky wrote:
> >
> > I also I don't remember ever seeing spam in the bugs.python.org
> > comments which suggests that the subscription process weeds bots
> > reasonably well.
>
> And when it fails, spam is deleted just so no
R. David Murray wrote:
> On Mon, 26 Apr 2010 14:15:01 -0400, Steve Holden wrote:
[...]
> For the record, note that both Antoine and I have been instrumental in
> bringing more than one new person into both the triage and the committer
> ranks. We (along with others) *are* the ones doing the welco
Antoine Pitrou pitrou.net> writes:
>
> Speaking of which, what is the procedure to delete a spam message and remove a
> spamming user?
Well, for some reason I hadn't seen the "remove button" message...
As for deleting the user, I suppose an admin can do it.
Regards
Antoine.
_
On Mon, 26 Apr 2010 14:23:00 -0400, Terry Reedy wrote:
> On 4/26/2010 2:12 AM, Sean Reifschneider wrote:
> > Then we went on to issue 5575 and read through it. In reading this one
> > to determine the priority, it was clear that the ball was back in
> > Collin's court, so I showed tha
On Mon, 26 Apr 2010 22:39:39 +0200, =?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=
wrote:
> >> If possible, I think 'normal' should be the default in the hox or else
> >> there should be some sort of auto replacement.
> >
> > Makes sense to me.
>
> I have now changed to make 'normal' the default pr
R. David Murray wrote:
> And I at
> least am in the mode of *discussing* it, not speaking from a position set
> in stone...if the consensus that develops is that the familiarization
> period can be skipped in certain cases, I'm not going to block that
> consensus or get mad about it...but I don't t
On Tue, 27 Apr 2010 11:15:49 +1000, Steven D'Aprano wrote:
> No, of course not. There are always other reasons, the biggest is too
> many things to do and not enough time to do it. If I did review
> patches, would they be accepted on the strength on my untrusted
> reviews?
It is very very help
R. David Murray wrote:
> Well, in my recent experience there are two things the assignee gets
> used for. The first is someone claiming an issue, saying, in effect,
> I'm going to work this issue until it is closed. The other is to do
> exactly what Sean did, assign it to the next person whose de
On Tue, 27 Apr 2010 23:34:48 +1000, Nick Coghlan wrote:
> R. David Murray wrote:
> > And I at
> > least am in the mode of *discussing* it, not speaking from a position set
> > in stone...if the consensus that develops is that the familiarization
> > period can be skipped in certain cases, I'm not
May I have enhanced permissions on the bug tracker, so that I can perform
the following tasks?
- Assign issues to myself that I plan to write a patch for
- Update the Stage to "patch review" after writing a patch
- Occasional bug triage
My login name on the tracker is "stutzbach".
I only find th
On Tue, Apr 27, 2010 at 09:41:02AM +0200, Tarek Ziadé wrote:
> On Tue, Apr 27, 2010 at 1:24 AM, Toshio Kuratomi wrote:
> > On Mon, Apr 26, 2010 at 05:46:55PM -0400, Barry Warsaw wrote:
> >> On Apr 26, 2010, at 09:39 PM, Tarek Ziadé wrote:
> >>
> >> >You should be permissive on that one. Until we k
On 01:38 pm, rdmur...@bitdance.com wrote:
On Tue, 27 Apr 2010 11:15:49 +1000, Steven D'Aprano
wrote:
No, of course not. There are always other reasons, the biggest is too
many things to do and not enough time to do it. If I did review
patches, would they be accepted on the strength on my untrus
On Tue, Apr 27, 2010 at 09:22, Daniel Stutzbach <
dan...@stutzbachenterprises.com> wrote:
> May I have enhanced permissions on the bug tracker, so that I can perform
> the following tasks?
>
> - Assign issues to myself that I plan to write a patch for
> - Update the Stage to "patch review" after w
On Tue, 27 Apr 2010 09:22:07 -0500, Daniel Stutzbach
wrote:
> May I have enhanced permissions on the bug tracker, so that I can perform
> the following tasks?
Done. I agree with Brian, Daniel has been making valuable
contributions for quite some time now. I/we will keep an eye on
his triage, o
On Apr 27, 2010, at 02:40 PM, exar...@twistedmatrix.com wrote:
>On 01:38 pm, rdmur...@bitdance.com wrote:
>>2) have unit tests that fail before the patch and succeed after
>
>This list would make a good addition to one of the cpython development
>pages. If potential contributors could find
On Tue, Apr 27, 2010 at 10:14 AM, R. David Murray wrote:
> Done. I agree with Brian, Daniel has been making valuable
> contributions for quite some time now. I/we will keep an eye on
> his triage, of course.
>
Thanks. Is there a document that describes the meaning of all of the
different field
On Tue, 27 Apr 2010 11:16:51 -0400, Barry Warsaw wrote:
> It would be kind of cool if there were some best practices for running said
> unittest both with and without the patch enabled. Kind of like using #ifdefs
> in C but without all the commenting-out-commenting-in error proneness. I
> guess
On Tue, Apr 27, 2010 at 5:16 PM, Barry Warsaw wrote:
> On Apr 27, 2010, at 02:40 PM, exar...@twistedmatrix.com wrote:
>
> >On 01:38 pm, rdmur...@bitdance.com wrote:
>
> >>2) have unit tests that fail before the patch and succeed after
> >
> >This list would make a good addition to one of the
On Tue, 27 Apr 2010 10:34:16 -0500, Daniel Stutzbach
wrote:
> Thanks. Is there a document that describes the meaning of all of the
> different fields in the bug tracker?
>
> I've read http://www.python.org/dev/workflow/, but it doesn't cover
> everything.
I think it is on Brett's list to updat
I have two somewhat unrelated thoughts about PEPs.
* Accepted: header
When PEP 3147 was accepted, I had a few folks ask that this be recorded in the
PEP by including a link to the BDFL pronouncement email. I realized that
there's no formal way to express this in a PEP, and many PEPs in fact don'
On Tue, Apr 27, 2010 at 11:16 AM, R. David Murray wrote:
> I think it is on Brett's list to update that doc, but maybe we should help
> him out :). Can you list what's missing? We should fill in the gaps.
>
Sure, here's what I've noticed:
The page doesn't document the Resolution or Status fiel
On Apr 27, 2010, at 11:43 AM, R. David Murray wrote:
>I wonder if it would be better to encourage people to post the unit
>tests and the fix as separate patch files.
I think this is not bad idea for larger fixes, where it's not trivial to
manually edit the diff.
-Barry
signature.asc
Descriptio
Sounds good to me (from my phone on my way to WWW2010).
On Apr 27, 2010 10:49 AM, "Barry Warsaw" wrote:
I have two somewhat unrelated thoughts about PEPs.
* Accepted: header
When PEP 3147 was accepted, I had a few folks ask that this be recorded in
the
PEP by including a link to the BDFL prono
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
R. David Murray wrote:
> On Tue, 27 Apr 2010 11:15:49 +1000, Steven D'Aprano
> wrote:
>> No, of course not. There are always other reasons, the biggest is too
>> many things to do and not enough time to do it. If I did review
>> patches, would they
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Barry Warsaw wrote:
> On Apr 27, 2010, at 02:40 PM, exar...@twistedmatrix.com wrote:
>
>> On 01:38 pm, rdmur...@bitdance.com wrote:
>
>>>2) have unit tests that fail before the patch and succeed after
>> This list would make a good addition to on
Tres Seaver palladion.com> writes:
>
> This is an excellent set of guidelines. The only drawback I see here is
> that the current VCS situation makes doing the review more tedious than
> it should be, especially for non-committers. Or maybe the Hg mirrors
> are truly up-to-date and working? La
On Tue, Apr 27, 2010 at 10:46 AM, Barry Warsaw wrote:
> I have two somewhat unrelated thoughts about PEPs.
>
> * Accepted: header
>
> When PEP 3147 was accepted, I had a few folks ask that this be recorded in the
> PEP by including a link to the BDFL pronouncement email. I realized that
> there's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Antoine Pitrou wrote:
> Tres Seaver palladion.com> writes:
>> This is an excellent set of guidelines. The only drawback I see here is
>> that the current VCS situation makes doing the review more tedious than
>> it should be, especially for non-commi
On Tue, Apr 27, 2010 at 03:23:19PM -0400, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Antoine Pitrou wrote:
> > Tres Seaver palladion.com> writes:
> >> This is an excellent set of guidelines. The only drawback I see here is
> >> that the current VCS situation makes d
On Apr 27, 2010, at 02:37 PM, Tres Seaver wrote:
>You can always "shelve" the part of the patch which isn't the test: I
>do that pretty frequently in the Zope tree, where I am now doing most
>development with bzr.
Yes definitely. bzr-loom just makes that much easier to manage.
-Barry
signatu
R. David Murray wrote:
> On Mon, 26 Apr 2010 22:39:39 +0200,
> =?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?= wrote:
If possible, I think 'normal' should be the default in the hox or else
there should be some sort of auto replacement.
>>> Makes sense to me.
>> I have now changed to make 'no
On Tue, Apr 27, 2010 at 4:38 PM, "Martin v. Löwis" wrote:
> Done!
Thanks, Martin!
-Fred
--
Fred L. Drake, Jr.
"Chaos is the score upon which reality is written." --Henry Miller
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.pyth
Antoine Pitrou wrote:
> Antoine Pitrou pitrou.net> writes:
>> Speaking of which, what is the procedure to delete a spam message and remove
>> a
>> spamming user?
>
> Well, for some reason I hadn't seen the "remove button" message...
> As for deleting the user, I suppose an admin can do it.
For
> My perception is that making someone nosy on an issue is preferred to
> assigning it to them (allowing them to assign it to themselves if they
> think that is appropriate), unless the issue is of higher priority or
> someone actively working on the issue really needs the other person's
> input i
> Hmm, it feels exactly the other way around to me: working with the DVCS
> tools while reviewiing a patch allows me to be more productive (e.g.,
> using 'bzr shelve' or the equivalent hg subcommand).
Just try using Subversion for some time again, and you'll see that it is
not difficult at all. S
> The page doesn't document the Resolution or Status fields.
The resolutions are the same as the ones on SourceForge. You only have
resolutions on closed issues, and they explain why an issue was closed.
If any specific one is unclear in that context, please be more specific.
On the status, I hop
Martin v. Löwis v.loewis.de> writes:
>
> In the specific case (msg104314), "remove" was probably the right thing,
> since it isn't real spam, but just non-sensical. I don't think the user
> needs to be banned from the tracker.
The message was a copy of a previous message by someone else, with an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin v. Löwis wrote:
>> Hmm, it feels exactly the other way around to me: working with the DVCS
>> tools while reviewiing a patch allows me to be more productive (e.g.,
>> using 'bzr shelve' or the equivalent hg subcommand).
>
> Just try using Subv
> The message was a copy of a previous message by someone else, with an
> additional
> HTML link in the middle. The target of that link was clearly the kind that
> would
> pay to increase its Google rank through whatever means (bogus diploma stuff,
> IIRC).
Ah, I missed that. I've marked it as
Ezio Melotti wrote:
> When I'm writing the patch it's usually easy, I write the tests, see
> that they fail, write the fix, see that they pass.
> When I'm reviewing the patch, I apply the patch, see that the tests
> pass, svn revert the fix, check that they fail.
> Most of the patches affect just a
Guido van Rossum wrote:
>> When PEP 3147 was accepted, I had a few folks ask that this be recorded in
>> the
>> PEP by including a link to the BDFL pronouncement email. I realized that
>> there's no formal way to express this in a PEP, and many PEPs in fact don't
>> record more than the fact that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 27/04/10 17:16, Barry Warsaw wrote:
> It would be kind of cool if there were some best practices for running said
> unittest both with and without the patch enabled. Kind of like using #ifdefs
> in C but without all the commenting-out-commenting-in
On Tue, 27 Apr 2010 12:59:26 pm Stephen J. Turnbull wrote:
> Steve Holden writes:
> > Yes, in the last year in particular there has been some excellent
> > effort of maintaining the issue tracker content. But the question
> > still remains - who are we worried about offending?
>
> In this thread
On 4/27/2010 4:38 PM, "Martin v. Löwis" wrote:
Done!
When I open http://bugs.python.org/iss...@template=item
priority is (still) set at no selection. Is this my local cache (which I
do not know how to clear in FF) or is 'normal' filled in after submission?
I do verify that searching for any
> When I open http://bugs.python.org/iss...@template=item
> priority is (still) set at no selection. Is this my local cache (which I
> do not know how to clear in FF) or is 'normal' filled in after submission?
It is filled in after submission.
Regards,
Martin
50 matches
Mail list logo
