r the built-in module sys.
The only time you need to import pydoc is if you wish to use it
programmatically. You don't need it just to view help.
Alternative, at your operating system's command prompt (terminal, shell, DOS
prompt, command line, etc), you may be able to call pydoc as if i
te:
> >> > > In fact, I wanted to run the following code. When it failed, I moved
> >> > > to the original question above.
> >> >
> >> > How did it fail? Tell us what _did_ happen.
> >> >
> >> > It works fin
In a message of Sat, 12 Dec 2015 15:01:54 -0800, Robert writes:
>Hi,
>
>I want to use pydoc as some online tutorial shows, but it cannot run as
>below. What is wrong?
>
>
>Thanks,
>
>
>
>
>>>> import pydoc
>>>> pydoc
>
>>>&g
gt;> > > to the original question above.
>> >
>> > How did it fail? Tell us what _did_ happen.
>> >
>> > It works fine for me:
>> >
>> > $ pydoc module1
>> > Help on module module1:
>> >
>> > NAME
>> >
On 13/12/15 00:19, Robert wrote:
It turns out that Enthought does not allow pydoc as the link said:
http://stackoverflow.com/questions/12063718/using-help-and-pydoc-to-list-python-modules-not-working
I don't think that's what the article is telling you. Try what I said in
my previo
ion above.
> >
> > How did it fail? Tell us what _did_ happen.
> >
> > It works fine for me:
> >
> > $ pydoc module1
> > Help on module module1:
> >
> > NAME
> > module1
> >
> > FILE
> > /tmp/robert/
o: qt
Type '?' for more information.
I don't have any experience with "Canopy", but it looks to me like it is
providing you with an interactive Python environment.
In [1]: pydoc module1
File "", line 1
pydoc module1
^
SyntaxError: in
On Saturday, December 12, 2015 at 6:24:25 PM UTC-5, Erik wrote:
> On 12/12/15 23:08, Robert wrote:
> > In fact, I wanted to run the following code. When it failed, I moved to
> > the original question above.
>
> How did it fail? Tell us what _did_ happen.
>
> It work
On 12/12/15 23:08, Robert wrote:
In fact, I wanted to run the following code. When it failed, I moved to
the original question above.
How did it fail? Tell us what _did_ happen.
It works fine for me:
$ pydoc module1
Help on module module1:
NAME
module1
FILE
/tmp/robert/module1.py
Robert writes:
> I want to use pydoc as some online tutorial shows
Which online tutorial? Please give the URL to the page that instructs
you to use ‘pydoc’ in that manner.
> >>> import pydoc
Allows you to use, in Python code, the ‘pydoc’ module by name.
> >>> py
Hi Robert,
On 12/12/15 23:01, Robert wrote:
I want to use pydoc as some online tutorial shows, but it cannot run as
below. What is wrong?
"some online tutorial"?
import pydoc
pydoc
Correct - in the interactive interpreter, typing the name of an object
prints its value
On Saturday, December 12, 2015 at 6:02:11 PM UTC-5, Robert wrote:
> Hi,
>
> I want to use pydoc as some online tutorial shows, but it cannot run as
> below. What is wrong?
>
>
> Thanks,
>
>
>
>
> >>> import pydoc
> >>> pydoc
>
&g
Hi,
I want to use pydoc as some online tutorial shows, but it cannot run as
below. What is wrong?
Thanks,
>>> import pydoc
>>> pydoc
>>> pydoc sys
SyntaxError: invalid syntax
>>> import sys
>>> pydoc sys
SyntaxError: invalid syntax
>>&
On Thu, 22 Aug 2013 06:39:48 +, Steven D'Aprano wrote:
> On Thu, 22 Aug 2013 05:13:03 +, Dan Sommers wrote:
>> class Spam1:
>>
>> def eggs(self):
>> '''Return the Meaning of Life.'''
>> return 42
>>
>> ham = eggs
>>
>>
>> help(Spam1) shows that ham = eggs(self)
On 22 Aug 2013 06:17, "Dan Sommers" wrote:
>
> Greetings,
>
> I'm hava a class in which there are two equally useful names for one
> method. Consider this design (there are other approaches, but that's
> not what my question is about):
>
> class Spam1:
>
> def eggs(self):
> '''Return
On Thu, 22 Aug 2013 05:13:03 +, Dan Sommers wrote:
> Greetings,
>
> I'm hava a class in which there are two equally useful names for one
> method. Consider this design (there are other approaches, but that's
> not what my question is about):
Generally though, one name will be the canonical
Greetings,
I'm hava a class in which there are two equally useful names for one
method. Consider this design (there are other approaches, but that's
not what my question is about):
class Spam1:
def eggs(self):
'''Return the Meaning of Life.'''
return 42
ham = eggs
help
rh writes:
> pydoc can be invoked from the operating system shell.
Which is irrelevant to what ‘pydoc’ produces, since it is looking in the
Python documentation.
You'll notice that ‘pydoc pydoc’ does not give the contents of the
‘pydoc’ manpage. Instead, it gives documentation for th
rh writes:
> I installed python from tarball and I wonder if I did something wrong.
> pydoc pydoc works fine but there's no pydoc python.
What would you expect ‘pydoc python’ to show? The word “python” is not a
keyword, is not a built-in identifier, is not a standard library module.
The pydoc.html.docmodule sends a page with clickable links relative to the
script location. Is there a way to tell pydoc to prepend a string to those URLs?
-- Gnarlie
--
http://mail.python.org/mailman/listinfo/python-list
; archived. Not only would this reduce the size of the plugin to almost
>> nothing, but it would prevent the documentation from being outdated.
>>
>>> For more information, please visit:
>>> https://sourceforge.net/projects/pydoc/
>> Why isn't it installed like ot
website running
> inside Eclipse so you can call it using Eclipse help system. As for now
> it is pretty large (~7 mb), but i'm planning to optimize it in near
> future.
>
> For more information, please visit:
>
> http://pydoc.tk/
ntation from being outdated.
>
>> For more information, please visit:
>> https://sourceforge.net/projects/pydoc/
> Why isn't it installed like other Eclipse plugins? Is it even possible
> to update the plugin via Eclipse?
>
>
> This does look like a very useful plug
,
but I can easily access it from a link in the page you've archived. Not
only would this reduce the size of the plugin to almost nothing, but it
would prevent the documentation from being outdated.
> For more information, please visit:
> https://sourceforge.net/projects/pydoc/
Why i
now it is pretty large (~7 mb), but i'm planning to optimize it
in near future.
For more information, please visit:
http://pydoc.tk/
or
https://sourceforge.net/projects/pydoc/
Advices are appreciated!
Contact e-m
now it is pretty large (~7 mb), but i'm planning to optimize it
in near future.
For more information, please visit:
http://pydoc.tk/
or
https://sourceforge.net/projects/pydoc/
Advices are appreciated!
Contact e-m
On Fri, 2010-02-26 at 13:49 -0300, Ricardo Aráoz wrote:
> Does pydoc only deal with ASCII?
UTF-8 in docstrings works for me.
Maybe:
* Its actually not UTF-8
* The console you're using doesn't support UTF-8 well
(note: I'm on linux, maybe its a problem with windows?)
code
occlass(*args)
File "C:\Python25\lib\pydoc.py", line 1208, in docclass
contents = '\n'.join(contents)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position
115: ordinal not in range(128)
The file's first two lines are :
"""
#!/usr/bin/env python
# -*- coding: utf-8 -*-
"""
Does pydoc only deal with ASCII?
--
http://mail.python.org/mailman/listinfo/python-list
Am 25.02.10 08:54, schrieb john maclean:
python version is 2.6.2 does any one else have this issue? Seen a few
closed tickets for various Linux Distros but it is obvoiusly still my
problem.
help> modules
Please wait a moment while I gather a list of all available modules...
dm.c: 1640: not r
python version is 2.6.2 does any one else have this issue? Seen a few
closed tickets for various Linux Distros but it is obvoiusly still my
problem.
help> modules
Please wait a moment while I gather a list of all available modules...
dm.c: 1640: not running as root returning empty list
** (.:8
I'm having some problems with pydoc and I was not very sucessful in
googling. (probably missng one key word)
Is there soemthing like a documentation of pydoc (execpt pydocs output
of pydoc, which doesn't seem to answer my question )
I can add docstrings to
- the file head
- to a cl
Hi,
often I start "pydoc -g" in a projects working directory in order to
view the docstrings of my own project and in order to get a quick
overview of the code structure
In some cases I would like to see also to see private methods
(especially when trying to understand the inte
Hi Diez,
Thanks for the heads up. I'll give epydoc a shot.
Matt
>
> > Anyone know the best way to getPyDocto ignore this (or other)
> > imported module(s)?
>
> Don't know aboutpydoc, but epydoc (which generates much nicer docs
> imho) can be forced to only include certain packages.
>
> Di
Matt Bellis schrieb:
Hi all,
I tried PyDoc today for documentation for a small project on which
I'm working. I have a class, foo, in foo.py. However, at the beginning
of the file I "from math import *".
When I use PyDoc, it's pulling in all the math fu
Hi all,
I tried PyDoc today for documentation for a small project on which
I'm working. I have a class, foo, in foo.py. However, at the beginning
of the file I "from math import *".
When I use PyDoc, it's pulling in all the math functions
---snip---
.
.
Hello Jean-Michel,
Thanks for your post. Based on it, and the ones received so
far I will give epydoc a closer look. I don't need something
superfancy (at least at the moment), just something that helps
me document my code more in an organized way and helps me
sift through the various classes/met
Esmail wrote:
shaileshkumar wrote:
Hello,
EPYDOC is very good for automatic generation of documentation from
source code.
You may also consider Sphinx http://sphinx.pocoo.org/ which is used
for many
projects including the official Python documentation, documentation of
Zope (http://docs.zope.o
Esmail wrote:
Mark Lawrence wrote:
Hi Mark,
The docs for the constraint package look good, see
http://labix.org/python-constraint and http://labix.org/doc/constraint.
I think they've been produced with epydoc see
http://epydoc.sourceforge.net/
Thanks for the links, I'll take a look.
Any exp
Mark Lawrence wrote:
Hi Mark,
The docs for the constraint package look good, see
http://labix.org/python-constraint and http://labix.org/doc/constraint.
I think they've been produced with epydoc see
http://epydoc.sourceforge.net/
Thanks for the links, I'll take a look.
Any experience with so
shaileshkumar wrote:
Hello,
EPYDOC is very good for automatic generation of documentation from
source code.
You may also consider Sphinx http://sphinx.pocoo.org/ which is used
for many
projects including the official Python documentation, documentation of
Zope (http://docs.zope.org/).
See the f
back to it
> > after some time, it would be nice to have some documentation
> > available to help jog my memory.
>
> > What is the best way to do this in an automated way? I have
> > been documenting my code as I've gone along.
>
> > Is pydoc still the way to go
gone along.
Is pydoc still the way to go, or should I use something else?
Thanks,
Esmail
The docs for the constraint package look good, see
http://labix.org/python-constraint and http://labix.org/doc/constraint.
I think they've been produced with epydoc see http://epydoc.sourceforge.net/
--
use only - as I can't
continuously work on this project and have to come back to it
after some time, it would be nice to have some documentation
available to help jog my memory.
What is the best way to do this in an automated way? I have
been documenting my code as I've gone along.
Is p
Thanks very much for your help
On Wed, Jul 22, 2009 at 6:43 PM, Lie Ryan wrote:
> jorma kala wrote:
> > Hi,
> > Do you know where I can find the rules for documenting Python code, so
> > that automatic document generation with Pydoc makes the most of the
> > co
jorma kala wrote:
> Hi,
> Do you know where I can find the rules for documenting Python code, so
> that automatic document generation with Pydoc makes the most of the
> comments inserted in the code?
> I know about documenting class and method through triple quote just
> under th
Hi,
Do you know where I can find the rules for documenting Python code, so that
automatic document generation with Pydoc makes the most of the comments
inserted in the code?
I know about documenting class and method through triple quote just under
the class definition. But how do you comment a
Albert Hopkins wrote:
On Mon, 2009-07-20 at 13:38 -0700, mrstevegross wrote:
I know how to use pydoc from the command line. However, because of
complicated environmental setup, it would be preferable to run it
within a python script as a native API call. That is, my python runner
looks a bit
On Mon, 2009-07-20 at 13:38 -0700, mrstevegross wrote:
> I know how to use pydoc from the command line. However, because of
> complicated environmental setup, it would be preferable to run it
> within a python script as a native API call. That is, my python runner
> looks a b
I know how to use pydoc from the command line. However, because of
complicated environmental setup, it would be preferable to run it
within a python script as a native API call. That is, my python runner
looks a bit like this:
import pydoc
pydoc.generate_html_docs_for(someFile)
However, it
I just installed the latest version of mock (0.4.0) under both Python 2.6
and 2.7 (svn trunk). In both cases pydoc fails to find anything:
~% pydoc2.6 mock
no Python documentation found for 'mock'
~% pydoc2.7 mock
no Python documentation found for 'mock'
but
path was pointing to Python25, so when I ran against the 2.5
version of Pydoc it worked fine; when I ran against the 2.6 version of
Pydoc, I got an error.
I modified my batch file to also reset the PATH after pyver was set,
and then Pydoc worked fine in both cases.
Maybe somebody out there will
On Mar 5, 1:48 pm, yino...@gmail.com wrote:
> On Mar 5, 1:29 pm, steve.ferg.bitbuc...@gmail.com wrote:
>
>
>
> > Has anybody encountered problems running pydoc with version 2.6.1?
> > I'm getting an error message that pydoc cannot import namedtuple
> > (detail
On Mar 5, 1:29 pm, steve.ferg.bitbuc...@gmail.com wrote:
> Has anybody encountered problems running pydoc with version 2.6.1?
> I'm getting an error message that pydoc cannot import namedtuple
> (details below).
> (I'm running under 64-bit Windows Vista, although that proba
Has anybody encountered problems running pydoc with version 2.6.1?
I'm getting an error message that pydoc cannot import namedtuple
(details below).
(I'm running under 64-bit Windows Vista, although that probably is not
important.)
Here's my batch file,
On Tue, 2008-12-02 at 09:38 +1100, Ken Faulkner wrote:
> Hi
>
> Yeah, I was thinking about something at commit time for a VCS...
> catch is, soo many VCS's out there.
> And I wasn't thinking of the default action throwing compile errors,
> but would only do that if a particular flag was given.
>
Hi
Yeah, I was thinking about something at commit time for a VCS... catch is,
soo many VCS's out there.
And I wasn't thinking of the default action throwing compile errors, but
would only do that if a particular flag was given.
Still, just an idea.
I'm just finding more and more public modules/
On Sun, 2008-11-30 at 16:27 -0800, [EMAIL PROTECTED] wrote:
> I've been thinking about implementing (although no idea yet *HOW*) the
> following features/extension for the python compile stage and would be
> interested in any thoughts/comments/flames etc.
>
> Basically I'm interested adding a che
Marc 'BlackJack' Rintsch <[EMAIL PROTECTED]> writes:
> On Sun, 30 Nov 2008 16:27:07 -0800, [EMAIL PROTECTED] wrote:
>
>> Basically I'm interested adding a check to see if:
>> 1) pydoc's are written for every function/method.
>
> Pylint warns for missing docstrings.
>
>> 2) There are entries fo
On Sun, 30 Nov 2008 16:27:07 -0800, [EMAIL PROTECTED] wrote:
> Basically I'm interested adding a check to see if:
> 1) pydoc's are written for every function/method.
Pylint warns for missing docstrings.
> 2) There are entries for each parameter, defined by some
predetermined syntax.
On Dec 1, 7:27 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
wrote:
> I've been thinking about implementing (although no idea yet *HOW*) the
> following features/extension for the python compile stage and would be
> interested in any thoughts/comments/flames etc.
>
> Basically I'm interested adding a
I support any idea that supports python. You have my vote friend!
--
http://mail.python.org/mailman/listinfo/python-list
Hey!
If you are interested, I have written a small tool for declaring
variables and attributes. It's not very sophisticated, because I have
written it solely for own use. It might be useful though. You can
download it from you: http://code.google.com/p/pyver/downloads/list
For a small example, it
I've been thinking about implementing (although no idea yet *HOW*) the
following features/extension for the python compile stage and would be
interested in any thoughts/comments/flames etc.
Basically I'm interested adding a check to see if:
1) pydoc's are written for every function/method.
2)
On Fri, 29 Aug 2008 07:12:28 -0700, Mike Driscoll wrote:
> On Aug 28, 5:45 pm, Tyler Shopshire <[EMAIL PROTECTED]> wrote:
>> I can't seem to access the pydoc sever from my web browser. I start the
>> server from the command prompt and everything seems to be working
On Aug 28, 5:45 pm, Tyler Shopshire <[EMAIL PROTECTED]> wrote:
> I can't seem to access the pydoc sever from my web browser. I start the
> server from the command prompt and everything seems to be working fine,
> then I got tohttp://localhost:/and it doesn't work. I
I can't seem to get Pydoc up and running in windows Vista. I can search
for modules manually by using the "pydoc module_name" command but if i
try to set up an http server, it says the server is up and running but I
can't access it in FF or IE. Any help is appreciated.
--
ht
I can't seem to access the pydoc sever from my web browser. I start the
server from the command prompt and everything seems to be working fine,
then I got to http://localhost:/ and it doesn't work. I also tried
starting the graphical mode with the -g parameter but I still cannot
On Mar 24, 3:31 am, "Gabriel Genellina" <[EMAIL PROTECTED]>
wrote:
> En Sun, 23 Mar 2008 12:57:35 -0300, A Hutchison <[EMAIL PROTECTED]> escribió:
>
> > Any known reasons why pydoc no longer works?
>
> It gets confused by many timezone changes that occur th
En Sun, 23 Mar 2008 12:57:35 -0300, A Hutchison <[EMAIL PROTECTED]> escribió:
> Any known reasons why pydoc no longer works?
It gets confused by many timezone changes that occur this month around the
world; pydoc tries hard to please all kind of users and tracking those
locale chan
Any known reasons why pydoc no longer works?
AB
--
http://mail.python.org/mailman/listinfo/python-list
Ron DuPlain wrote:
> I also expected "pydoc -w mypackage" to recursively generate html for
> the whole package, but it only wrote the top-level file for me as well
> (on Linux, for the record)
>
> I use the workaround:
> pydoc -w ./
>
> This runs "pydoc
et a File Not Found message in
> the browser for doing so.
>
I also expected "pydoc -w mypackage" to recursively generate html for
the whole package, but it only wrote the top-level file for me as well
(on Linux, for the record).
> If I'm at C:\ in the command prompt and try &qu
uot;pydoc.py -w
F:\path\to\project\myPackage" I get "no Python documentation found for
'Module'".
pydoc -g seems to display the package's doc .htmls with no problems. I
can't seem to figure what's wrong here, so any help is appreciated.
--
http://mail.python.org/mailman/listinfo/python-list
JimG wrote:
> On Dec 26, 1:56 pm, Bernard Delmée <[EMAIL PROTECTED]>
> wrote:
>> (I know replying to self is a sure sign of aging :-)
>> A quick update: after installing the 'tkinter' fedora
>> package (still in live-cd mode), the following 3 line
On Dec 26, 1:56 pm, Bernard Delmée <[EMAIL PROTECTED]>
wrote:
> (I know replying to self is a sure sign of aging :-)
> A quick update: after installing the 'tkinter' fedora
> package (still in live-cd mode), the following 3 lines
> script does what "pydoc -g
(I know replying to self is a sure sign of aging :-)
A quick update: after installing the 'tkinter' fedora
package (still in live-cd mode), the following 3 lines
script does what "pydoc -g " should:
import Tkinter
import pydoc
pydoc.gui()
HTH,
Bernard.
--
ht
than you have), if I try the following
at the interactive python prompt, I am getting "No module named
Tkinter"
import pydoc
pydoc.gui()
You probably discovered this already, but you can at least
launch "pydoc -p 1234" and view the python doc by pointing
your brows
On Dec 26, 10:43 am, JimG <[EMAIL PROTECTED]> wrote:
> On Dec 26, 9:46 am, Bernard Delmée <[EMAIL PROTECTED]>
> wrote:
>
>
>
> > FWIW I am using 2.4.4 under debian etch and 2.5.1 under windows XP,
> > and pydoc seems to support the -[pgkw] flags under both ve
On Dec 26, 9:46 am, Bernard Delmée <[EMAIL PROTECTED]>
wrote:
> FWIW I am using 2.4.4 under debian etch and 2.5.1 under windows XP,
> and pydoc seems to support the -[pgkw] flags under both versions.
> When trying -g under debian, I am getting a stack-trace and a message
> invi
FWIW I am using 2.4.4 under debian etch and 2.5.1 under windows XP,
and pydoc seems to support the -[pgkw] flags under both versions.
When trying -g under debian, I am getting a stack-trace and a message
inviting me to install the python-tk package.
Does "pydoc -g" provide any feedba
On Dec 26, 8:27 am, Bernard Delmée <[EMAIL PROTECTED]>
wrote:
> Hi Jim, I guess you're missing tk and its tkinter
> python wrapper. Sorry I don't know what the corresponding
> packages would be called under fedora...
Hi Bernard,
Thanks for the suggestion, however, that does not seem to be the
rea
Hi Jim, I guess you're missing tk and its tkinter
python wrapper. Sorry I don't know what the corresponding
packages would be called under fedora...
--
http://mail.python.org/mailman/listinfo/python-list
On Dec 24, 9:23 am, JimG <[EMAIL PROTECTED]> wrote:
> I just read about the pydoc gui in "Learning Python." But it's
> mysteriously absent from my Fedora 8 Python installation. Searching
> the filesystem exhaustively turns up no pydocgui script anywhere, and
>
I just read about the pydoc gui in "Learning Python." But it's
mysteriously absent from my Fedora 8 Python installation. Searching
the filesystem exhaustively turns up no pydocgui script anywhere, and
not only does "pydoc -g" not work, my Python documentation has no
me
kirillrd <[EMAIL PROTECTED]> wrote:
> On Nov 20, 4:28 pm, Jens <[EMAIL PROTECTED]> wrote:
>> On 20 Nov., 08:19, Marc 'BlackJack' Rintsch <[EMAIL PROTECTED]> wrote:
>>
>> > On Mon, 19 Nov 2007 10:50:28 -0800, Jens wrote:
>> > > Generating documentation form code is a nice thing, but this pydoc.py
>
On Nov 20, 4:28 pm, Jens <[EMAIL PROTECTED]> wrote:
> On 20 Nov., 08:19, Marc 'BlackJack' Rintsch <[EMAIL PROTECTED]> wrote:
>
> > On Mon, 19 Nov 2007 10:50:28 -0800, Jens wrote:
> > > Generating documentation form code is a nice thing, but this pydoc.py
> > > is driving me insane - isn't there are
On 20 Nov., 08:19, Marc 'BlackJack' Rintsch <[EMAIL PROTECTED]> wrote:
> On Mon, 19 Nov 2007 10:50:28 -0800, Jens wrote:
> > Generating documentation form code is a nice thing, but this pydoc.py
> > is driving me insane - isn't there are better way?
>
> Epydoc!?
>
> Ciao,
> Marc 'BlackJack'
for each of my modules. Seems like a silly solution.
>
> > Also, when I have a module that imports from math (for example),
> > pydoc.py generates a broken link to the math module. This just seems
> > very silly.
>
> > Generating documentation form code is a ni
link to the math module. This just seems
> very silly.
>
> Generating documentation form code is a nice thing, but this pydoc.py
> is driving me insane - isn't there are better way?
pydoc -h
[...]
pydoc -w ...
Write out the HTML documentation for a module to a file in the
c
On Mon, 19 Nov 2007 10:50:28 -0800, Jens wrote:
> Generating documentation form code is a nice thing, but this pydoc.py
> is driving me insane - isn't there are better way?
Epydoc!?
Ciao,
Marc 'BlackJack' Rintsch
--
http://mail.python.org/mailman/listinfo/python-list
On 8 Nov., 02:46, Jens <[EMAIL PROTECTED]> wrote:
> I have a project/package for which I want to generate documentation
> usingpydoc.
>
> My problem is that when I type "pydoc.py -w MyPackage" it only
> generates documentation for the package - no modules, classes or
> methods or sub-packages. Just
I have a project/package for which I want to generate documentation
using pydoc.
My problem is that when I type "pydoc.py -w MyPackage" it only
generates documentation for the package - no modules, classes or
methods or sub-packages. Just a single HTML file called
"MyPackage.html&q
On Nov 7, 4:47 pm, Laszlo Nagy <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > Has anyone ever tried mucking with pydoc to the point where you can
> > get it to give you output from a string input? For example I'd like
> > to give it a whole module to ge
[EMAIL PROTECTED] wrote:
> Has anyone ever tried mucking with pydoc to the point where you can
> get it to give you output from a string input? For example I'd like
> to give it a whole module to generate documentation for but all within
> a string:
>
> #little
Has anyone ever tried mucking with pydoc to the point where you can
get it to give you output from a string input? For example I'd like
to give it a whole module to generate documentation for but all within
a string:
#little sample
module_code='''
""&
On Sat, 20 Oct 2007 15:02:26 +, BartlebyScrivener wrote:
> On Debian Etch, if ~/mypyscripts is in my bash PATH and also in
> PYTHONPATH, I get the following pydoc behaviors. Maybe this is
> intentional. I'm just checking to be sure I don't have something
> misconfig
On Debian Etch, if ~/mypyscripts is in my bash PATH and also in
PYTHONPATH, I get the following pydoc behaviors. Maybe this is
intentional. I'm just checking to be sure I don't have something
misconfigured in my environment.
If I have two scripts or modules in ~/mypyscripts: one scr
Stuart wrote:
> I'm asking if there's some sort of commenting or input file or
> something to customize the output pydoc generates. Thanks.
AFAIK, there is no way to do this. However, you can edit the doc string
for your function, which can include the argument list. I believe th
I'm asking if there's some sort of commenting or input file or
something to customize the output pydoc generates. Thanks.
On Jun 23, 11:00 pm, 7stud <[EMAIL PROTECTED]> wrote:
> On Jun 23, 2:13 pm, Stuart <[EMAIL PROTECTED]> wrote:
>
> > With my Python
On Jun 23, 2:13 pm, Stuart <[EMAIL PROTECTED]> wrote:
> With my Python extension module all the function definitions are with
> METH_VARGS. The result being that pydoc, just puts "(...)" for the
> argument list. Can I hand edit this to put the specific variable name
1 - 100 of 171 matches
Mail list logo