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
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
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,
On Wed, 03 Jul 2013 10:10:17 -0400, Roy Smith wrote:
> In article ,
> Terry Reedy wrote:
>
>> 6. If you make an informed post to the tracker backed up by at least
>> opinion, at least one tracker responder be in a better mode when
>> responding.
>
> What I generally do is summarize the problem
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
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
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
On 03/07/2013 12:50, rusi wrote:
On Wednesday, July 3, 2013 6:09:35 AM UTC+5:30, Ben Finney wrote:
Dennis Lee Bieber writes:
So who would enforce any rules?
Ideally, this community is healthy enough for us to enforce the code of
conduct of our host, through social convention among us all.
T
In article ,
Terry Reedy wrote:
> 6. If you make an informed post to the tracker backed up by at least
> opinion, at least one tracker responder be in a better mode when responding.
What I generally do is summarize the problem in the tracker, but also
include a link to the google groups archi
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
On Wednesday, July 3, 2013 6:09:35 AM UTC+5:30, Ben Finney wrote:
> Dennis Lee Bieber writes:
>
> > So who would enforce any rules?
>
> Ideally, this community is healthy enough for us to enforce the code of
> conduct of our host, through social convention among us all.
Thanks Ben for that.
Lets
Dennis Lee Bieber:
So who would enforce any rules? I doubt it could be ported to a new (if
approval could even be obtained) comp.lang.python.mod(erated) so nothing
can be enforced on the comp.lang.python side; and what would you do with
Google Groups?
The current news group charter
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
On Wed, 03 Jul 2013 08:39:59 +1000, Ben Finney wrote:
> Steve Simmons writes:
>> Does this list have a code of conduct or a netiqeutte (sp?)
>> statement/requirement?
>
> This forum (both a Usenet newsgroup and a mailing list) is part of the
> Python community. So the “Python Community Code of C
On 7/2/2013 7:46 PM, 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 would revise this to "If you are have really found a bug in Python..."
How does a newbie know?
I'm not sure I agre
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
*
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
On Tue, 02 Jul 2013 16:51:38 +0100, Steve Simmons wrote:
> Erm,
>
> It probably isn't the best time to start this post but I was
> wondering...
>
> Does this list have a code of conduct or a netiqeutte (sp?)
> statement/requirement?
>
> If not, should it?
I *knew* this would be raised. You are
Dennis Lee Bieber writes:
> So who would enforce any rules?
Ideally, this community is healthy enough for us to enforce the code of
conduct of our host, through social convention among us all.
--
\“I took a course in speed waiting. Now I can wait an hour in |
`\
On 02Jul2013 19:46, 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 shouldn't expec
In article ,
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 shouldn't expect anybody
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 shouldn't expect anybody to do anything about a bug unless
you open
Steve Simmons writes:
> It probably isn't the best time to start this post but I was
> wondering...
An excellent time to raise this, in my opinion. Thank you for doing so.
> Does this list have a code of conduct or a netiqeutte (sp?)
> statement/requirement?
This forum (both a Usenet newsgrou
In article ,
Steve Simmons wrote:
> Does this list have a code of conduct or a netiqeutte (sp?)
> statement/requirement?
>From http://www.python.org/community/lists/
comp.lang.python
comp.lang.python is a high-volume Usenet open (not moderated) newsgroup
for general discussions and question
> Does this list have a code of conduct or a netiqeutte (sp?)
> statement/requirement?
>
> If not, should it?
No, and probably not. As Joshua Landau indicated, nobody reads the
user manual anyway. In addition, this mailing list is not currently
moderated in an approve-each-message sort of way (
On 2 July 2013 16:51, Steve Simmons wrote:
> Erm,
>
> It probably isn't the best time to start this post but I was wondering...
>
> Does this list have a code of conduct or a netiqeutte (sp?)
> statement/requirement?
>
> If not, should it?
>
> Is the membership of this list presently in the right
Erm,
It probably isn't the best time to start this post but I was wondering...
Does this list have a code of conduct or a netiqeutte (sp?)
statement/requirement?
If not, should it?
Is the membership of this list presently in the right frame of mind to create
one or update any existing one?
27 matches
Mail list logo
