«

The OP speaks for himself alone.

Python - for such a very young language, and with the documentation and
community blogs available at this point - I cannot ask for more.

And who needs docs when the python syntax is as good as writing plain
english sentence?


On Fri, Mar 1, 2013 at 9:06 PM, Jean-Michel Pichavant <
> wrote:

> [snip hostile replies]
>
> It's somehow funny to read such posts on a thread about someone
> complaining about the community python being hostile.
> I think we should really try to resist the urge of answering trolls
> because no matter how many times we slap them, they'll stay trolls and
> probably get even bigger.
>
> Instead, we take revenge by helping someone asking us to do his homework
> and show the world how merciful the python community is.
>
> JM
>
>
> -- IMPORTANT NOTICE:
>
> The contents of this email and any attachments are confidential and may
> also be privileged. If you are not the intended recipient, please notify
> the sender immediately and do not disclose the contents to any other
> person, use it for any purpose, or store or copy the information in any
> medium. Thank you.
> --
> http://mail.python.org/mailman/listinfo/python-list
>

On Tue, 26 Feb 2013 18:06:21 -0800
rh <> wrote:

> On 26 Feb 2013 12:54:56 GMT
> Steven D'Aprano <steve+comp.lang.python-iDnA/YwAAsAk
> +I/> wrote:
>
> > One week ago, "JoePie91" wrote a blog post challenging the Python
> > community and the state of Python documentation, titled:
> >
> > "The Python documentation is bad, and you should feel bad".
> >
> > http://joepie91.wordpress.com/2013/0...tation-is-bad-
> > and-you-should-feel-bad/
> >
> > It is valuable to contrast and compare the PHP and Python docs:
> >
> > http://php.net/manual/en/index.php
> > http://www.python.org/doc/
>
> FWIW, I refer to the docs often. I keep a local copy and
> serve the pages up locally
>
> 1. http://docs.python.org/2/archives/py...s-html.tar.bz2
> 2. unroll
> 3. cd python-2.7.3-docs-html
> 4. python -c 'import SimpleHTTPServer as foo;foo.test()' 9292
> 5. point browser to 0:9292

I find that this works now to replace step #4:
python -m SimpleHTTPServer 9292

On Wed, 27 Feb 2013 15:25:25 -0800 (PST), alex23 wrote:

> On Feb 27, 1:13*pm, Rick Johnson <rantingrickjohn...@gmail.com> wrote:
>
> > [...] do you /really/ expect that people
> > have the time to open an issue on the bug tracker?
>
> If someone can write a paragraph on their blog or this list
> complaining about a problem, then yes, they have the time to open an
> issue on the bug tracker.

I've tried twice to register with the bug tracker -- including
just before sending this post. Both times I got something like
this:

Subject: Failed issue tracker submission
From: Python tracker <roundup->
Date: Wed, 06 Mar 2013 00:56:44 +0000

An unexpected error occurred during the processing
of your message. The tracker administrator is being
notified.

So, it's not all that easy to report bugs for me, anyway. I'd
given up, prior, but reading this thread I thought I'd try one
more time.

I had wanted to report doc bugs, too, as I used to do copy and
line editing. I seem to be able to find typos and such rather
easily, but reporting said bugs -- not so easy.

Something seems amiss, I'd say. It may be just me, but the point
still stands.

--Bob Hanson

--
Hanson's Heuristic: Ninety-eight percent of what I think I know
is bullshit. The rest is crap.

[Sorry for the double-post -- I somehow had Followup-To set to
poster in the first post.]

On Wed, 27 Feb 2013 15:25:25 -0800 (PST), alex23 wrote:

> On Feb 27, 1:13*pm, Rick Johnson <rantingrickjohn...@gmail.com> wrote:
>
> > [...] do you /really/ expect that people
> > have the time to open an issue on the bug tracker?
>
> If someone can write a paragraph on their blog or this list
> complaining about a problem, then yes, they have the time to open an
> issue on the bug tracker.

I've tried twice to register with the bug tracker -- including
just before sending this post. Both times I got something like
this:

Subject: Failed issue tracker submission
From: Python tracker <roundup->
Date: Wed, 06 Mar 2013 00:56:44 +0000

An unexpected error occurred during the processing
of your message. The tracker administrator is being
notified.

So, it's not all that easy to report bugs for me, anyway. I'd
given up, prior, but reading this thread I thought I'd try one
more time.

I had wanted to report doc bugs, too, as I used to do copy and
line editing. I seem to be able to find typos and such rather
easily, but reporting said bugs -- not so easy.

Something seems amiss, I'd say. It may be just me, but the point
still stands.

--Bob Hanson

--
Hanson's Heuristic: Ninety-eight percent of what I think I know
is bullshit. The rest is crap.

[Sorry for the double-post -- I somehow had Followup-To set to
poster in the first post.]

On Wed, 27 Feb 2013 15:25:25 -0800 (PST), alex23 wrote:

> On Feb 27, 1:13*pm, Rick Johnson <rantingrickjohn...@gmail.com> wrote:
>
> > [...] do you /really/ expect that people
> > have the time to open an issue on the bug tracker?
>
> If someone can write a paragraph on their blog or this list
> complaining about a problem, then yes, they have the time to open an
> issue on the bug tracker.

I've tried twice to register with the bug tracker -- including
just before sending this post. Both times I got something like
this:

Subject: Failed issue tracker submission
From: Python tracker <roundup->
Date: Wed, 06 Mar 2013 00:56:44 +0000

An unexpected error occurred during the processing
of your message. The tracker administrator is being
notified.

So, it's not all that easy to report bugs for me, anyway. I'd
given up, prior, but reading this thread I thought I'd try one
more time.

I had wanted to report doc bugs, too, as I used to do copy and
line editing. I seem to be able to find typos and such rather
easily, but reporting said bugs -- not so easy.

Something seems amiss, I'd say. It may be just me, but the point
still stands.

--Bob Hanson

--
Hanson's Heuristic: Ninety-eight percent of what I think I know
is bullshit. The rest is crap.

On 06/03/2013 01:43, Bob Hanson wrote:
> On Wed, 27 Feb 2013 15:25:25 -0800 (PST), alex23 wrote:
>
>> On Feb 27, 1:13 pm, Rick Johnson <rantingrickjohn...@gmail.com> wrote:
>>
>>> [...] do you /really/ expect that people
>>> have the time to open an issue on the bug tracker?
>>
>> If someone can write a paragraph on their blog or this list
>> complaining about a problem, then yes, they have the time to open an
>> issue on the bug tracker.
>
> I've tried twice to register with the bug tracker -- including
> just before sending this post. Both times I got something like
> this:
>
> Subject: Failed issue tracker submission
> From: Python tracker <roundup->
> Date: Wed, 06 Mar 2013 00:56:44 +0000
>
> An unexpected error occurred during the processing
> of your message. The tracker administrator is being
> notified.
>
> So, it's not all that easy to report bugs for me, anyway. I'd
> given up, prior, but reading this thread I thought I'd try one
> more time.
>
> I had wanted to report doc bugs, too, as I used to do copy and
> line editing. I seem to be able to find typos and such rather
> easily, but reporting said bugs -- not so easy.
>
> Something seems amiss, I'd say. It may be just me, but the point
> still stands.
>
> --Bob Hanson
>

You'll be delighted to know that everybody will have to sign a
contributor agreement if they're supplying a patch file on the bug
tracker, see
http://blog.python.org/2013/03/intro...ntributor.html
and http://mail.python.org/pipermail/pyt...ch/124540.html

--
Cheers.

Mark Lawrence

On Tue, 05 Mar 2013 17:51:36 -0800, Bob Hanson wrote:


> I've tried twice to register with the bug tracker -- including just
> before sending this post. Both times I got something like this:
>
> Subject: Failed issue tracker submission From: Python tracker
> <roundup-> Date: Wed, 06 Mar 2013
> 00:56:44 +0000
>
> An unexpected error occurred during the processing of your message.
> The tracker administrator is being notified.

Works for me.


Please try again, and if it still does not work, please email me off-list
and I will help you either set up an account or report a tracker bug.



--
Steven

On Tue, 05 Mar 2013 17:51:36 -0800
Bob Hanson <> wrote:
>
> I've tried twice to register with the bug tracker -- including
> just before sending this post. Both times I got something like
> this:
>
> Subject: Failed issue tracker submission
> From: Python tracker <roundup->
> Date: Wed, 06 Mar 2013 00:56:44 +0000
>
> An unexpected error occurred during the processing
> of your message. The tracker administrator is being
> notified.
>
> So, it's not all that easy to report bugs for me, anyway. I'd
> given up, prior, but reading this thread I thought I'd try one
> more time.
>
> I had wanted to report doc bugs, too, as I used to do copy and
> line editing. I seem to be able to find typos and such rather
> easily, but reporting said bugs -- not so easy.

Can you post to comp.python.bugs? Or ?
Who wants to sign up for yet another website?

>
> Something seems amiss, I'd say. It may be just me, but the point
> still stands.
>
> --Bob Hanson

On 3/6/2013 2:48 PM, rh wrote:

>> I've tried twice to register with the bug tracker -- including
>> just before sending this post. Both times I got something like
>> this:
>>
>> Subject: Failed issue tracker submission
>> From: Python tracker <roundup->
>> Date: Wed, 06 Mar 2013 00:56:44 +0000
>>
>> An unexpected error occurred during the processing
>> of your message. The tracker administrator is being
>> notified.
>>
>> So, it's not all that easy to report bugs for me, anyway. I'd
>> given up, prior, but reading this thread I thought I'd try one
>> more time.
>>
>> I had wanted to report doc bugs, too, as I used to do copy and
>> line editing. I seem to be able to find typos and such rather
>> easily, but reporting said bugs -- not so easy.

From http://docs.python.org/3/bugs.html

"Documentation bugs

If you find a bug in this documentation or would like to propose an
improvement, please send an e-mail to describing the bug
and where you found it. If you have a suggestion how to fix it, include
that as well.

is a mailing list run by volunteers; your request will
be noticed, even if it takes a while to be processed."

For anything more than trivial changes (typos, grammar errors), a
tracker issue is better. But the above is better than nothing.

--
Terry Jan Reedy

On Wednesday, March 6, 2013 5:50:35 PM UTC-6, Terry Reedy wrote:

> If you find a bug in this documentation or would like to propose an
> improvement, please send an e-mail to describing the bug
> and where you found it. If you have a suggestion how to fix it, include
> that as well.

That's great Terry, but how will the next person find the link? I went to Python.org and i did not see it on the home page, nor the doc page... and i've been Python-ing for years now!

If i can't find the link, how will a noob find it? How much longer are we going to "treat the symptoms" before we realize that we're dealing with a disease that can be cured?