Re: [Python-Dev] checklist for filing a bug

2005-07-08 Thread Terry Reedy
"Raymond Hettinger" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] >> In order to lower the barrier for reporting bugs, writing patches, and >> handling CVS commits, I am writing up checklists for each and I will >> put them up on python.org. > > -0 on the checklists. I am more enth

Re: [Python-Dev] checklist for filing a bug

2005-07-08 Thread Raymond Hettinger
> In order to lower the barrier for reporting bugs, writing patches, and > handling CVS commits, I am writing up checklists for each and I will > put them up on python.org. -0 on the checklists. I don't think existing "barriers" are high at all. The entries may be variously regarded as codifying

Re: [Python-Dev] checklist for filing a bug

2005-07-08 Thread Skip Montanaro
Brett> #. Gather important information Brett> Info such as Python version, operating system version, etc.; Brett> anything that might have influenced the code that lead to the Brett> bug. I'd change this to something more explicit: # Gather important information

Re: [Python-Dev] checklist for filing a bug

2005-07-08 Thread Tadeusz Andrzej Kadłubowski
Thus wrote Brett Cannon: How about: > #. Report the bug on SourceForge_ Make sure your bug hasn't been reported many times already. > Create a new tracker item, filling out the ``Category`` and ``Group`` > fields. Do not set the ``Assigned To`` or ``Priority`` fields. Upload >