Re: Bug reports [was Re: Python list code of conduct]

2013-07-03 Thread Grant Edwards
On 2013-07-03, Roy Smith wrote: > In article , > Grant Edwards wrote: > >> On 2013-07-03, Roy Smith wrote: >> > In article , >> > Chris Angelico wrote: >> > >> >> Of course, it's possible for there to be dark corners. But if you're >> >> working with those, you know it full well. The dark cor

Re: Bug reports [was Re: Python list code of conduct]

2013-07-03 Thread Roy Smith
In article , Grant Edwards wrote: > On 2013-07-03, Roy Smith wrote: > > In article , > > Chris Angelico wrote: > > > >> Of course, it's possible for there to be dark corners. But if you're > >> working with those, you know it full well. The dark corners of Python > >> might be in some of its

Re: Bug reports [was Re: Python list code of conduct]

2013-07-03 Thread Grant Edwards
On 2013-07-03, Roy Smith wrote: > In article , > Chris Angelico wrote: > >> Of course, it's possible for there to be dark corners. But if you're >> working with those, you know it full well. The dark corners of Python >> might be in some of its more obscure modules, or maybe in IPv6 >> handling,

Re: Bug reports [was Re: Python list code of conduct]

2013-07-03 Thread Chris Angelico
On Thu, Jul 4, 2013 at 12:23 AM, Roy Smith wrote: > In article , > Chris Angelico wrote: > >> On Thu, Jul 4, 2013 at 12:03 AM, Roy Smith wrote: >> > In article , >> > Chris Angelico wrote: >> > >> >> Of course, it's possible for there to be dark corners. But if you're >> >> working with those

Re: Bug reports [was Re: Python list code of conduct]

2013-07-03 Thread Roy Smith
In article , Chris Angelico wrote: > On Thu, Jul 4, 2013 at 12:03 AM, Roy Smith wrote: > > In article , > > Chris Angelico wrote: > > > >> Of course, it's possible for there to be dark corners. But if you're > >> working with those, you know it full well. The dark corners of Python > >> might

Re: Bug reports [was Re: Python list code of conduct]

2013-07-03 Thread Chris Angelico
On Thu, Jul 4, 2013 at 12:03 AM, Roy Smith wrote: > In article , > Chris Angelico wrote: > >> Of course, it's possible for there to be dark corners. But if you're >> working with those, you know it full well. The dark corners of Python >> might be in some of its more obscure modules, or maybe in

Re: Bug reports [was Re: Python list code of conduct]

2013-07-03 Thread Roy Smith
In article , Chris Angelico wrote: > Of course, it's possible for there to be dark corners. But if you're > working with those, you know it full well. The dark corners of Python > might be in some of its more obscure modules, or maybe in IPv6 > handling, The sad thing about this statement is th

Re: Bug reports [was Re: Python list code of conduct]

2013-07-03 Thread Chris Angelico
On Wed, Jul 3, 2013 at 10:52 AM, Steven D'Aprano wrote: > A popular language like Python has been around for about 20 years. It is > in daily use by tens of thousands of people around the world. What are > the chances that you, in your first week of using Python, just happened > to stumble across

Re: Bug reports [was Re: Python list code of conduct]

2013-07-02 Thread Joshua Landau
On 3 July 2013 01:52, Steven D'Aprano wrote: > If you are a beginner to a programming language, assume that anything > that doesn't work the way you expect is a bug in YOUR code, or YOUR > understanding, not in the language. Not just beginners. Out of the hundreds of times where I've gone "this *

Bug reports [was Re: Python list code of conduct]

2013-07-02 Thread Steven D'Aprano
On Tue, 02 Jul 2013 19:46:13 -0400, Roy Smith wrote: > In article , > Ned Deily wrote: > >> If you find a bug in Python, don't send it to comp.lang.python; file a >> bug report in the issue tracker. > > I'm not sure I agree with that one, at least not fully. It's certainly > true that you sho