Re: [OT] Usage of U+00B6 PILCROW SIGN (was: generator slides review and Python doc (+/- text bug))

On Thu, Feb 6, 2014 at 11:23 PM, Rustom Mody wrote: > On Tuesday, February 4, 2014 8:51:25 PM UTC+5:30, jmf wrote: > >> Useless and really ugly. > > Evidently one can do worse: > > http://www.pip-installer.org/en/latest/installing.html#requirements Aside from using a little "chain link" icon rath

Re: [OT] Usage of U+00B6 PILCROW SIGN (was: generator slides review and Python doc (+/- text bug))

Le jeudi 6 février 2014 13:23:03 UTC+1, Rustom Mody a écrit : > On Tuesday, February 4, 2014 8:51:25 PM UTC+5:30, jmf wrote: > > > > > Useless and really ugly. > > > > Evidently one can do worse: > > > > http://www.pip-installer.org/en/latest/installing.html#requirements or http://cx-free

Re: [OT] Usage of U+00B6 PILCROW SIGN (was: generator slides review and Python doc (+/- text bug))

On Tuesday, February 4, 2014 8:51:25 PM UTC+5:30, jmf wrote: > Useless and really ugly. Evidently one can do worse: http://www.pip-installer.org/en/latest/installing.html#requirements -- https://mail.python.org/mailman/listinfo/python-list

Re: [OT] Usage of U+00B6 PILCROW SIGN (was: generator slides review and Python doc (+/- text bug))

2014-02-04 : > Le mardi 4 février 2014 15:39:54 UTC+1, Jerry Hill a écrit : > > Useless and really ugly. > I think this whole discussion is rather useless instead, why do you care since you're not going to use this tool anyway? -- https://mail.python.org/mailman/listinfo/python-list

Re: [OT] Usage of U+00B6 PILCROW SIGN (was: generator slides review and Python doc (+/- text bug))

Le mardi 4 février 2014 15:39:54 UTC+1, Jerry Hill a écrit : > On Tue, Feb 4, 2014 at 1:51 AM, wrote: > > > I got it. If I'm visiting a page like this: > > > > > > http://docs.python.org/3/tutorial/index.html#the-python-tutorial > > > > > > 1) To read the page, I'm scrolling down. > > > 2)

Re: [OT] Usage of U+00B6 PILCROW SIGN (was: generator slides review and Python doc (+/- text bug))

On Tue, Feb 4, 2014 at 1:51 AM, wrote: > I got it. If I'm visiting a page like this: > > http://docs.python.org/3/tutorial/index.html#the-python-tutorial > > 1) To read the page, I'm scrolling down. > 2) When I have finished to read the page, I scroll up > (or scroll back/up) to the top of the pa

Re: [OT] Usage of U+00B6 PILCROW SIGN (was: generator slides review and Python doc (+/- text bug))

On Tue, Feb 4, 2014 at 5:51 PM, wrote: > 2) When I have finished to read the page, I scroll up > (or scroll back/up) to the top of the page until I see > this "feature" and the title. > 3) I click on this "feature". > 4) The title, already visible, moves, let's say, "2cm" higher. At which point

Re: [OT] Usage of U+00B6 PILCROW SIGN (was: generator slides review and Python doc (+/- text bug))

Le lundi 3 février 2014 23:56:43 UTC+1, Ben Finney a écrit : > Rotwang writes: > > > > > Why on Earth would the ["¶", U+00B6 PILCROW SIGN] correspond to an > > > EOL? The section sign and pilcrow have a history of being used to > > > refer to sections and paragraphs respectively, so using the

[OT] Usage of U+00B6 PILCROW SIGN (was: generator slides review and Python doc (+/- text bug))

Rotwang writes: > Why on Earth would the [“¶”, U+00B6 PILCROW SIGN] correspond to an > EOL? The section sign and pilcrow have a history of being used to > refer to sections and paragraphs respectively, so using them for > permalinks to individual sections of a web page makes perfect sense. Symbo

Re: generator slides review and Python doc (+/- text bug)

Le lundi 3 février 2014 19:55:26 UTC+1, Rotwang a écrit : > On 03/02/2014 18:37, wxjmfa...@gmail.com wrote: > > >> [...] > > >> > > >> Hint: try clicking the ¶. > > > > > > I never was aware of this "feature". Is it deliverate? > > > > Do you mean deliberate? Of course it is. > > > > >

Re: generator slides review and Python doc (+/- text bug)

On 03/02/2014 18:37, wxjmfa...@gmail.com wrote: [...] Hint: try clicking the ¶. I never was aware of this "feature". Is it deliverate? Do you mean deliberate? Of course it is. It gives to me the feeling of a badly programmed html page, especially if this sign does correspond to an eol!

Re: generator slides review and Python doc (+/- text bug)

On Tue, Feb 4, 2014 at 5:37 AM, wrote: > Le lundi 3 février 2014 18:42:36 UTC+1, Rotwang a écrit : >> On 03/02/2014 13:59, wxjmfa...@gmail.com wrote: >> Hint: try clicking the ¶. > > I never was aware of this "feature". Is it deliverate? > > It gives to me the feeling of a badly programmed > html

Re: generator slides review and Python doc (+/- text bug)

Le lundi 3 février 2014 18:42:36 UTC+1, Rotwang a écrit : > On 03/02/2014 13:59, wxjmfa...@gmail.com wrote: > > > [...] > > > > > > I noticed the same effect with the Python doc > > > since ? (long time). > > > > > > Eg. > > &

Re: generator slides review and Python doc (+/- text bug)

2014-02-03 : > generator slides review and Python doc > > > I do not know what tool is used to produce such > slides. > > When the mouse is over a a text like a title ( ... <\H*> ???) > the text get transformed and a colored eol is appearing. > > Example

Re: generator slides review and Python doc (+/- text bug)

On 03/02/2014 13:59, wxjmfa...@gmail.com wrote: [...] I noticed the same effect with the Python doc since ? (long time). Eg. The Python Tutorial appears as The Python Tutorial¶ with a visible colored "¶", 'PILCROW SIGN', blueish in Python 3, red in Python 2.7.6. Hi

Re: generator slides review and Python doc (+/- text bug)

On 02/03/2014 06:59 AM, wxjmfa...@gmail.com wrote: > generator slides review and Python doc > > > I do not know what tool is used to produce such > slides. What slides? What web site are you referring to? A little context wouldn't hurt. -- https://mail.python.org/mailman/listinfo/python-list

Re: generator slides review and Python doc (+/- text bug)

- Original Message - > generator slides review and Python doc > > > I do not know what tool is used to produce such > slides. > > When the mouse is over a a text like a title ( ... <\H*> ???) > the text get transformed and a colored eol is appearing. U

generator slides review and Python doc (+/- text bug)

generator slides review and Python doc I do not know what tool is used to produce such slides. When the mouse is over a a text like a title ( ... <\H*> ???) the text get transformed and a colored eol is appearing. Example with the slide #3: Even numbers becomes Even numbers§ with a v

Re: Error while building Python doc

Am 22.12.2013 21:59, schrieb Terry Reedy: > Did you run "make -C Doc checkout" first? (I do not know what the -C > does, as I just do "make checkout" and occasionally make update in Doc > on Windows, which run Doc/make.bat. -C == change directory "make -C Doc html" is like "cd Doc; make html; cd

Re: Error while building Python doc

On 12/22/2013 1:53 PM, shankha wrote: Hi, I am trying to build Python documents as listed here http://docs.python.org/devguide/documenting.html#building-the-documentation make -C Doc html Error message: Checked out revision 89010. mkdir -p build/html build/doctrees python tools/sphinx-build.py

Error while building Python doc

Hi, I am trying to build Python documents as listed here http://docs.python.org/devguide/documenting.html#building-the-documentation make -C Doc html Error message: Checked out revision 89010. mkdir -p build/html build/doctrees python tools/sphinx-build.py -b html -d build/doctrees -D latex_pape

Re: python doc available in emacs info format?

A.Politz wrote: > On Aug 17, 6:43 am, Xah Lee wrote: >> btw, is there still [no] info format for python doc? >> >> i feel kinda sad [...] >> Part of this is due to [other peoples fault] > > Someone started a rst2info project (google it), maybe you want to hel

Re: python doc available in emacs info format?

On Aug 17, 6:43 am, Xah Lee wrote: > btw, is there still [no] info format for python doc? > > i feel kinda sad [...] > Part of this is due to [other peoples fault] Someone started a rst2info project (google it), maybe you want to help this guy out. Though, he might be a techgeeker,

Re: Social problems of Python doc [was Re: Python docs disappointing]

ru...@yahoo.com writes: > I took a look at the PHP docs last night which seem pretty well > done. The User Comments looked rather as I expected, there was > useful info but most did not contain documentation quality writing. > So if they are used as a source for improving the docs, there > clearly

Re: Social problems of Python doc [was Re: Python docs disappointing]

On 18 Aug, 05:19, ru...@yahoo.com wrote: > > Yes, I agree.  I should have mentioned this as an exception > in my "wikis suck" diatribe.  Although it far better than > most wiki's I've seen, it is still pretty easy to find signs > of typical wiki-ness.  On the Documentation page my first > click was

Re: Social problems of Python doc [was Re: Python docs disappointing]

On Mon, 17 Aug 2009 13:56:13 -0700, Paul Rubin wrote: > Python 3.0 went overboard by actually removing the cmp argument and > requiring use of the key argument. That requires various kludges if the > key is, say, a tree structure that has to be recursively compared with > another such structure.

Re: Social problems of Python doc [was Re: Python docs disappointing]

Nathan Keel wrote: idiot ... asshole absolutely clueless ... idiot ...incredibly arrogant, yet incredibly clueless. To me, such name-calling is as obnoxious as the intended target. tjr -- http://mail.python.org/mailman/listinfo/python-list

Re: Social problems of Python doc [was Re: Python docs disappointing]

On 08/13/2009 08:46 AM, Paul Boddie wrote: > On 13 Aug, 16:05, ru...@yahoo.com wrote: >> All the above not withstanding, I too think a wiki is worth >> trying. But without doing a lot more than just "setting up >> a wiki", I sadly believe even a python.org supported wiki >> is doomed to failure. >

Re: Social problems of Python doc [was Re: Python docs disappointing]

[Xah Lee] > This part i don't particular agree: > > > * The reason for implementing the key= parameter had nothing to do > > with limitations of Python's compiler.  Instead, it was inspired by > > the > > decorate-sort-undecorate pattern. > > The decorate-sort-undecorate pattern is a compiler limi

Re: Social problems of Python doc [was Re: Python docs disappointing]

Jon Harrop wrote: > Xah Lee wrote: >> On Aug 12, 12:15 pm, Raymond Hettinger wrote: >>> * The reason for implementing the key= parameter had nothing to do >>> with limitations of Python's compiler. Instead, it was inspired by >>> the >>> decorate-sort-undecorate pattern. >> >> The decorate-sort

Re: python doc available in emacs info format?

y in commericial software about 10 years ago. Xah ∑ http://xahlee.org/ ☄ On Aug 17, 4:32 am, "Colin S. Miller" wrote: > Xah Lee wrote: > > btw, is there still info format for python doc? > > > i feel kinda sad that emacs info format has pretty much been > > d

Re: Social problems of Python doc [was Re: Python docs disappointing]

Jon Harrop writes: > You mean people use that pattern as a fast alternative in languages where > user-defined functions are very slow, like Python and Mathematica? It really doesn't matter whether the language is fast or slow--there are going to be applications where calling the comparison functi

Re: python doc available in emacs info format?

"Colin S. Miller" writes: [...] > Ubuntu maintains a package search site, it is on > http://packages.ubuntu.com/ > > However, there seems to be no files named > python.*info (regexp) And yet there are info files in python2.5-doc: .

Re: Social problems of Python doc [was Re: Python docs disappointing]

Jon Harrop wrote: >Xah Lee wrote: [...] Please do not feed this well-known troll. He is known to spew some remotely on-topic junk into a bunch of unrelated NGs and to enjoy the ensuing confusion. jue -- http://mail.python.org/mailman/listinfo/python-list

Re: Social problems of Python doc [was Re: Python docs disappointing]

Xah Lee wrote: > On Aug 12, 12:15 pm, Raymond Hettinger wrote: >> * The reason for implementing the key= parameter had nothing to do >> with limitations of Python's compiler. Instead, it was inspired by >> the >> decorate-sort-undecorate pattern. > > The decorate-sort-undecorate pattern is a com

Re: python doc available in emacs info format?

Xah Lee wrote: btw, is there still info format for python doc? i feel kinda sad that emacs info format has pretty much been deprecated over the past decade. About a decade ago, you still will see now and then people asking for emacs info format of docs (was the days of perl). Today, one don&#

Re: python doc available in emacs info format?

info format for Xah Lee writes: > in programing elisp in emacs, i can press “Ctrl+h f” to lookup > the doc for the function under cursor. is there such facility > when coding in perl, python, php? On Dec 11 2008, 6:56 am, Matthias wrote: > Yes, try C-h S (or similarly S): > (info-looku

Re: Social problems of Python doc [was Re: Python docs disappointing]

many examples have > been added to the docs and more are forthcoming. > > > I often receive thank you emails for 2 particular articles, which are > > most frequently google searched as indicated by my weblog: > > > • Python Doc Problem Example: gzip > > http://xahlee.or

python doc available in emacs info format?

btw, is there still info format for python doc? i feel kinda sad that emacs info format has pretty much been deprecated over the past decade. About a decade ago, you still will see now and then people asking for emacs info format of docs (was the days of perl). Today, one don't hear of it.

Re: Social problems of Python doc [was Re: Python docs disappointing]

out of the blue i noticed someone has posted a bug on python's gzip doc with acknowledgement. http://bugs.python.org/issue2406 Thank you M.-A. DARCHE (madarche). Also, i noticed python doc now and later has improved a lot since last i looked around python 2.4. For one thing, the html/xhtml is

Re: Social problems of Python doc [was Re: Python docs disappointing]

A basic question in this thread is: Who will host the doc-wiki/whatever and how will it be linked to? If not hosted at python.org it can still be linked to from their docs, if allowed, possibly with 3rd level domain and re-direct. I host a number of commercial servers but I don't expect Guido to

Re: Social problems of Python doc [was Re: Python docs disappointing]

On Wed, 12 Aug 2009 20:23:27 -0700, rurpy wrote: >> That's no different from *any* major refactoring. The exact same >> problem exists for code as well as documentation. It's a solved problem >> for code, and it's a solved problem for documentation. > > Huh? I don't buy this at all. Code refact

Re: Social problems of Python doc [was Re: Python docs disappointing]

On 13 Aug, 16:05, ru...@yahoo.com wrote: > > All the above not withstanding, I too think a wiki is worth > trying.  But without doing a lot more than just "setting up > a wiki", I sadly believe even a python.org supported wiki > is doomed to failure. The ones on python.org seem to function reasona

Re: Social problems of Python doc [was Re: Python docs disappointing]

On 08/12/2009 12:27 PM, Raymond Hettinger wrote: > On Aug 12, 3:32 am, Paul Boddie wrote: >> Maybe the problem is that although everyone welcomes contributions and >> changes (or says that they do), the mechanisms remain largely beyond >> criticism. > > FWIW, I support the idea the regular docs in

Re: Social problems of Python doc [was Re: Python docs disappointing]

Paul Boddie wrote: Right, but those good points are still worth taking on board. There have been Xah Lee posts which have been relatively constructive, The last time that he did do so that I read, I responded rationally like I would with any other normal post. He responded with foul insults.

Re: Social problems of Python doc [was Re: Python docs disappointing]

Raymond Hettinger wrote: On Aug 12, 3:32 am, Paul Boddie wrote: Maybe the problem is that although everyone welcomes contributions and changes (or says that they do), the mechanisms remain largely beyond criticism. FWIW, I support the idea the regular docs incorporating links to freely editab

Re: Social problems of Python doc [was Re: Python docs disappointing]

On 08/12/2009 01:58 AM, Steven D'Aprano wrote: > On Tue, 11 Aug 2009 14:50:51 -0700, rurpy wrote: > The issue tracker is fine for many things, but the process it provides is equivalent to peep-hole optimization. How does one submit a tracker issue for something like the overall orga

Re: Social problems of Python doc [was Re: Python docs disappointing]

> FWIW, I support the idea the regular docs incorporating links > to freely editable wiki pages. That will at least make it > easier for people to make changes or add notes. > > That being said, I would like to add a few thoughts about the > current process. ISTM that important corrections (

Re: Social problems of Python doc [was Re: Python docs disappointing]

[Raymond Hettinger] > Here are a few thoughts on list.sort() for those who are interested: After one more reading of Xah Lee's posts on the documentation for sort, here are couple more thoughts: * The reason that list.sort() allows None for the cmp parameter is not so that you can write list.sort

Re: Social problems of Python doc [was Re: Python docs disappointing]

On Aug 12, 1:27 pm, Raymond Hettinger wrote: (snip) > * Many doc requests come from people just learning the language > (that makes sense because the learning process involves reading > the docs).  Unfortunately, a fair number of those requests are > flat-out wrong or represent a profound misunder

Re: Social problems of Python doc [was Re: Python docs disappointing]

emails for 2 particular articles, which are > most frequently google searched as indicated by my weblog: > > • Python Doc Problem Example: gzip >  http://xahlee.org/perl-python/python_doc_gzip.html > > • Python Doc Problem Example: sort() >  http://xahlee.org/perl-python/python

Re: Social problems of Python doc [was Re: Python docs disappointing]

On Aug 12, 3:32 am, Paul Boddie wrote: > Maybe the problem is that although everyone welcomes contributions and > changes (or says that they do), the mechanisms remain largely beyond > criticism. FWIW, I support the idea the regular docs incorporating links to freely editable wiki pages. That wi

Re: Social problems of Python doc [was Re: Python docs disappointing]

Paul Boddie wrote: On 12 Aug, 17:08, Steven D'Aprano wrote: It's not the people who suggest improvements to the docs that are the problem, but the ones who insist that the docs are terrible, but aren't willing to do anything but complain. Oh, and trolls like ... I hesitate to mention his name i

Re: Social problems of Python doc [was Re: Python docs disappointing]

On 12 Aug, 17:08, Steven D'Aprano wrote: > On Wed, 12 Aug 2009 06:24:18 -0700, Paul Boddie wrote: > > > What does the Python entry on Wikipedia have to do with editing the > > Python documentation in a Wiki? > > Good question. I was responding to you mentioning Wikipedia as a possible > role model

Re: Social problems of Python doc [was Re: Python docs disappointing]

On Wed, 12 Aug 2009 06:24:18 -0700, Paul Boddie wrote: > On 12 Aug, 14:08, Steven D'Aprano cybersource.com.au> wrote: >> >> With tens of millions of web users, it's no surprise that Wikipedia can >> attract thousands of editors. But this does not apply to Python, which >> starts from a comparativ

Re: Social problems of Python doc [was Re: Python docs disappointing]

Paul Boddie wrote: [snip] One can always spend one's time doing something which isn't 100% enjoyable or 100% rewarding if one feels that the time is still being spent on something worthwhile. I'm getting the feeling that lots of Python-related stuff doesn't quite satisfy such criteria any more.

Re: Social problems of Python doc [was Re: Python docs disappointing]

On 12 Aug, 14:08, Steven D'Aprano wrote: > > With tens of millions of web users, it's no surprise that Wikipedia can > attract thousands of editors. But this does not apply to Python, which > starts from a comparatively tiny population, primarily those interested > in Python. Have a look at the Wi

Re: Social problems of Python doc [was Re: Python docs disappointing]

Paul Boddie boddie.org.uk> writes: > > A free-for-all isn't likely to be the best solution for more actively > edited Python documentation, but Wiki solutions undeniably provide a > superior "fast path" for edits by trusted users to be incorporated and > published in accessible end-user documenta

Re: Social problems of Python doc [was Re: Python docs disappointing]

On Wed, 12 Aug 2009 03:32:08 -0700, Paul Boddie wrote: > On 12 Aug, 09:58, Steven D'Aprano > wrote: >> >> We know that there are problems. We've said repeatedly that corrections >> and patches are welcome. We've repeatedly told you how to communicate >> your answer to the question of what should

Re: Social problems of Python doc [was Re: Python docs disappointing]

On 12 Aug, 09:58, Steven D'Aprano wrote: > > We know that there are problems. We've said repeatedly that corrections > and patches are welcome. We've repeatedly told you how to communicate > your answer to the question of what should be done. None of this is good > enough for you. I don't know wha

Re: Social problems of Python doc [was Re: Python docs disappointing]

On Wed, 12 Aug 2009 10:45:51 +0200, Hendrik van Rooyen wrote: > On Tuesday 11 August 2009 19:53:16 Steven D'Aprano wrote: > >> You want community input into the docs, but you're not willing to give >> that input except to bitch and moan and sook that the tracker is no >> good. > > wtf does the v

Re: Social problems of Python doc [was Re: Python docs disappointing]

On Tuesday 11 August 2009 19:53:16 Steven D'Aprano wrote: > You want community input into the docs, but you're not willing to give > that input except to bitch and moan and sook that the tracker is no good. wtf does the verb "sook" mean? I find: sook   /sʊk/ Show Spelled Pronunciation [so

Re: Social problems of Python doc [was Re: Python docs disappointing]

On Tue, 11 Aug 2009 14:50:51 -0700, rurpy wrote: >>> The issue tracker is fine for many things, but the process it provides >>> is equivalent to peep-hole optimization. How does one submit a >>> tracker issue for something like the overall organization of the docs >>> (for example, the mis-placem

Re: Social problems of Python doc [was Re: Python docs disappointing]

ru...@yahoo.com wrote: Such a reorg is not a simple matter of moving a file from here to there. It will require a lot moving about of sections and a lot of word-smithing to glue them back together again in a coherent way. Concerning this particular issue, not everyone would agree that the doc

Re: Social problems of Python doc [was Re: Python docs disappointing]

Carl Banks writes: > On> For example, kj (who started this mess of thread) complained that > pydoc didn't give exhaustive usage documentation. In contrast, I > think pydoc gives too much information. I would rather have only the > bare minimum; I don't want to pan through ten paragraphs just to

Re: Social problems of Python doc [was Re: Python docs disappointing]

On Aug 11, 4:08 pm, Paul Boddie wrote: > On 11 Aug, 23:50, ru...@yahoo.com wrote: > > However, were the Python docs site to provide a wiki, along > > with a mechanism to migrate suggestions developed on the wiki > > into the docs, it might well be a viable (and easier because of > > the wysiwyg ef

Re: Social problems of Python doc [was Re: Python docs disappointing]

On 11 Aug, 11:37 pm, pavlovevide...@gmail.com wrote: I will not take an opinion on whether Python's documentation is ideal (more on why below) but I will opine that the conclusion doesn't follow from your premise. People's expectations of what documentation should be are too different, there wi

Re: Social problems of Python doc [was Re: Python docs disappointing]

On Aug 11, 3:08 pm, Paul Boddie wrote: > Certainly, the documentation situation with > Python is not ideal; otherwise, people would not be complaining about > it so frequently. I will not take an opinion on whether Python's documentation is ideal (more on why below) but I will opine that the conc

Re: Social problems of Python doc [was Re: Python docs disappointing]

At 03:08 PM 8/11/2009, you wrote: I recommend going to the existing Wiki and looking at what there is already: http://wiki.python.org/moin/Documentation http://wiki.python.org/moin/CategoryDocumentation I also can't see how to get from http://wiki.python.org/moin/Documentation to http://wik

Re: Social problems of Python doc [was Re: Python docs disappointing]

On 11 Aug, 23:50, ru...@yahoo.com wrote: > > However, were the Python docs site to provide a wiki, along > with a mechanism to migrate suggestions developed on the wiki > into the docs, it might well be a viable (and easier because of > the wysiwyg effect) way of improving the docs.  As other have

Re: Social problems of Python doc [was Re: Python docs disappointing]

rsuade them to stop >>>> taxing us... >>> You know, the most interesting thing in this thread is certainly its >>> title : « Social problems of Python doc » >>> >>> Yes, the little social problem here should be clear: if you have >>> complaint

Re: Social problems of Python doc [was Re: Python docs disappointing]

Steven D'Aprano writes: > - if people are keen on a Python wiki, then by all means publish one, > just don't expect the Python dev team to build and manage it for you; There are already some nice ones at: http://en.wikibooks.org/wiki/Python -- http://mail.python.org/mailman/listinfo/python-

Re: Social problems of Python doc [was Re: Python docs disappointing]

gt; don't you think you should be discussing it on python-dev ? >>> Yea, them's be a friendly bunch to noob ideas ;). Hey i got a better >>> idea, lets go to the IRS and see if we can persuade them to stop >>> taxing us... >> >> You know, the most inter

Re: Social problems of Python doc [was Re: Python docs disappointing]

Yea, them's be a friendly bunch to noob ideas ;). Hey i got a better >> idea, lets go to the IRS and see if we can persuade them to stop >> taxing us... > > You know, the most interesting thing in this thread is certainly its title : > « Social problems of Python do

Re: Social problems of Python doc [was Re: Python docs disappointing]

better idea, lets go to the IRS and see if we can persuade them to stop taxing us... You know, the most interesting thing in this thread is certainly its title : « Social problems of Python doc » Yes, the little social problem here should be clear: if you have complaints to voice or improvements

Re: Social problems of Python doc [was Re: Python docs disappointing]

;). Hey i got a better > idea, lets go to the IRS and see if we can persuade them to stop > taxing us... You know, the most interesting thing in this thread is certainly its title : « Social problems of Python doc » Yes, the little social problem here should be clear: if you have complaints t

Re: Social problems of Python doc [was Re: Python docs disappointing]

On Aug 9, 11:02 pm, David Lyon wrote: > Since you're talking about documentation, which is a part of python, > don't you think you should be discussing it on python-dev ? Yea, them's be a friendly bunch to noob ideas ;). Hey i got a better idea, lets go to the IRS and see if we can persuade them

Re: Social problems of Python doc [was Re: Python docs disappointing]

On Aug 9, 10:02 pm, David Lyon wrote: ... > Before you do that, you should clearly work out in your own mind > how you think things need to improve. It's not good enough just > saying this or that is bad without having specific ideas on what > needs to change. ''' He did. Did you read, for examp

Re: Social problems of Python doc [was Re: Python docs disappointing]

t; > I often receive thank you emails for 2 particular articles, which are > most frequently google searched as indicated by my weblog: > > • Python Doc Problem Example: gzip > http://xahlee.org/perl-python/python_doc_gzip.html > > • Python Doc Problem Example: sort() >

Social problems of Python doc [was Re: Python docs disappointing]

on_re-write/lib/module-re.html there are some positive reviews, but most are drawn out by nay-sayers. I often receive thank you emails for 2 particular articles, which are most frequently google searched as indicated by my weblog: • Python Doc Problem Example: gzip http://xahlee.

Re: about Python doc reader

Tim Golden wrote: norseman wrote: I did try these. Doc at once: outputs two x'0D' and the file. Then it appends x'0D' x'0D' x'0A' x'0D' x'0A' to end of file even though source file itself has no EOL. ( EOL is EndOfLine aka newline ) That's cr cr There are two blank lines at be

Re: about Python doc reader

norseman wrote: I did try these. Doc at once: outputs two x'0D' and the file. Then it appends x'0D' x'0D' x'0A' x'0D' x'0A' to end of file even though source file itself has no EOL. ( EOL is EndOfLine aka newline ) That's cr cr There are two blank lines at begining. cr

Fw: about Python doc reader

Shailja Gulati wrote: > Sorry about mailing u Tim.It just happened by mistake. > > Reg win32api , i m still facing the same problem of Import error...Could > anyone pls help?? m stuck Shailja. Did you download and install the download .exe from the link below? yeah..I have installed it from t

Re: about Python doc reader

Shailja Gulati wrote: Sorry about mailing u Tim.It just happened by mistake. Reg win32api , i m still facing the same problem of Import error...Could anyone pls help?? m stuck Shailja. Did you download and install the download .exe from the link below? http://sourceforge.net/project/platfo

about Python doc reader

[forwarding back to the list] Please reply to the list: I'm not the only person who can help, and I might not have the time even if I can. Shailja Gulati wrote: > I have installed win32com but still not able to run tht code as its giving > error > > File "readDocPython.py", line 1, in ? >

Re: about Python doc reader

[forwarding back to the list] Please reply to the list: I'm not the only person who can help, and I might not have the time even if I can. Shailja Gulati wrote: I have installed win32com but still not able to run tht code as its giving error File "readDocPython.py", line 1, in ? import

Re: about Python doc reader

norseman wrote: Tim Golden wrote: Shailja Gulati wrote: Hi , I am currently working on "Information retrieval from semi structured Documents" in which there is a need to read data from Resumes. Could anyone tell me is there any python API to read Word doc? If you haven't already, get hold

Re: about Python doc reader

Tim Golden wrote: Shailja Gulati wrote: Hi , I am currently working on "Information retrieval from semi structured Documents" in which there is a need to read data from Resumes. Could anyone tell me is there any python API to read Word doc? If you haven't already, get hold of the pywin32 e

Re: about Python doc reader

Kushal Kumaran wrote: On Wed, May 13, 2009 at 4:28 PM, Shailja Gulati wrote: Hi , I am currently working on "Information retrieval from semi structured Documents" in which there is a need to read data from Resumes. Could anyone tell me is there any python API to read Word doc? If you're us

Re: about Python doc reader

Shailja Gulati wrote: Hi , I am currently working on "Information retrieval from semi structured Documents" in which there is a need to read data from Resumes. Could anyone tell me is there any python API to read Word doc? If you haven't already, get hold of the pywin32 extensions: http:/

Re: about Python doc reader

On Wed, May 13, 2009 at 4:28 PM, Shailja Gulati wrote: > > Hi , > > I am currently working on "Information retrieval from semi structured > Documents" in which there is a need to read data from Resumes. > > Could anyone tell me is there any python API to read Word doc? > If you're using Windows,

about Python doc reader

Hi , I am currently working on "Information retrieval from semi structured Documents" in which there is a need to read data from Resumes. Could anyone tell me is there any python API to read Word doc? Thanks and regards, Shailja =-=-= Notice: The information contained in t

Re: Python Doc 2.6 vs 2.5--A Matter of Format?

> I see for 2.5 and > for 2.6. I'm guessing these two pages differ > somewhat in formats simply because someone decided to do so, and not > that I'm in the wrong place for each of the two versions, correct? Correct. The documentation forma

Re: Python Doc 2.6 vs 2.5--A Matter of Format?

On Sat, Jan 31, 2009 at 9:14 AM, W. eWatson wrote:I see for 2.5 and for 2.6. I'm guessing these two pages differ somewhat in formats simply because someone decided to do so, and not that I'm in the wrong place for each of the two versions,

Python Doc 2.6 vs 2.5--A Matter of Format?

I see for 2.5 and for 2.6. I'm guessing these two pages differ somewhat in formats simply because someone decided to do so, and not that I'm in the wrong place for each of the two versions, correct? For example, somewhere down in the 2.5

Re: python doc in command line

Peng Yu <[EMAIL PROTECTED]> writes: > Perl has a command line help perldoc. I'm wondering if python has a > similar help command. The interactive interpreter has a "help" command, and a corresponding "help" function which can be passed an object to display its docstrings recursively and nicely-fo

Re: python doc in command line

Peng Yu wrote: Perl has a command line help perldoc. I'm wondering if python has a similar help command. it's built into the interpreter, and Python tells you how to use it when you start Python in interactive mode. $ python Python 2.5.1 Type "help", "copyright", "credits" or "license" for

python doc in command line

Hi, Perl has a command line help perldoc. I'm wondering if python has a similar help command. Thanks, Peng -- http://mail.python.org/mailman/listinfo/python-list

Python doc problem example: gzip module (reprise)

>>> fileToCompress = open('finalcallejon.mb') >>> fileToStr = fileToCompress.read() >>> import gzip >>> fileZipped = gzip.GzipFile('finalcallejon.mb.gz', 'wb', 9) >>> fileZipped.write(fileToStr) >>> fileZipped.close() this may help you in http://mail.python.org/pipermail/python-list/2005-November

Re: python-doc

h file. So i "cd" to the directory containing the python scripts I wish to python-doc, typing in "python-doc.py scriptname.py" and after about 1 second, i get nothing. No error, but again, no indication that this process has been completed. I have no idea where to look for

  1   2   >