On Friday 05 January 2007 02:49, Talin wrote:
One issue that needs to be worked out, however, is the division of
responsibility between markup processor and output formatter. Does a
__markup__ plugin do both jobs, or does it just do parsing, and leave
the formatting of output to the
Ron,
Thanks for your detailed answer.
I inserted comments below.
2007/1/5, Ron Adam [EMAIL PROTECTED]:
Laurent Gautier wrote:
[cut]
Introspection is probably already available in the separate module
'inspect',
and what a code pydoc would have to do is model the documentation
(as a
On Thu, 4 Jan 2007, Talin wrote:
One issue that needs to be worked out, however, is the division of
responsibility between markup processor and output formatter. Does a
__markup__ plugin do both jobs, or does it just do parsing, and leave
the formatting of output to the appropriate HTML / text
On Friday 05 January 2007 17:40, Gregory P. Smith wrote:
Whoever is subscribed to python-dev with a broken corporate
autoresponder that sends everyone who posts to the list this
useless response multiple times please unsubscribe yourself. Its
highly annoying and entirely useless since its not
2007/1/5, Ka-Ping Yee [EMAIL PROTECTED]:
[cut]
On the other hand, I've often seen the question of why pydoc does
both text and HTML generation instead of generating some intermediate
data structure from which both kinds of output are produced. The
answer is: I tried it. The result turned out
2007/1/5, Ka-Ping Yee [EMAIL PROTECTED]:
On Thu, 4 Jan 2007, Talin wrote:
One issue that needs to be worked out, however, is the division of
responsibility between markup processor and output formatter. Does a
__markup__ plugin do both jobs, or does it just do parsing, and leave
the
On Fri, Jan 05, 2007 at 06:01:22PM +0800, Laurent Gautier wrote:
Well, if you are ok with having the source tree hosted in a
SVN/CVS/alike I am on
(opening an account on sourceforge or savannah -for example- would be
the next step then, as it can take few days for a project to be
approved)
2007/1/5, A.M. Kuchling [EMAIL PROTECTED]:
On Fri, Jan 05, 2007 at 06:01:22PM +0800, Laurent Gautier wrote:
Well, if you are ok with having the source tree hosted in a
SVN/CVS/alike I am on
(opening an account on sourceforge or savannah -for example- would be
the next step then, as it can
No time to review this now, but I'd just like to say that the 1 thing I'd
like to see is support for decent mathematical markup. I think at this
point that support for latex markup is the way to achieve this.
___
Python-Dev mailing list
Talin wrote:
Rather than fixing on a standard markup, I would like to see support for
a __markup__ module variable which specifies the specific markup
language that is used in that module. Doc processors could inspect that
variable and then load the appropriate markup translator.
Ideally, a
On Friday, January 05, 2007, at 02:30PM, Fredrik Lundh [EMAIL PROTECTED]
wrote:
Talin wrote:
Rather than fixing on a standard markup, I would like to see support for
a __markup__ module variable which specifies the specific markup
language that is used in that module. Doc processors could
On Fri, Jan 05, 2007 at 09:12:28PM +0800, Laurent Gautier wrote:
I suspect that this is aside from the rest of the python source tree.
(or I would anticipate peppered emails if the module is broken during
its early days
-and it will- ).
Correct; it can be browsed at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 5, 2007, at 9:29 AM, Barry Warsaw wrote:
On Jan 5, 2007, at 6:06 AM, Anthony Baxter wrote:
On Friday 05 January 2007 17:40, Gregory P. Smith wrote:
Whoever is subscribed to python-dev with a broken corporate
autoresponder that sends
On Thu, Jan 04, 2007 at 01:47:13PM -0800, Neal Norwitz wrote:
We have the buildbots to help with this.
According to http://www.python.org/dev/buildbot/trunk/ we do not have
a single working XP or Cygwin buildbot right now.
Definitely! I only did a really quick review. If you want someone to
Laurent Gautier wrote:
Ron,
Thanks for your detailed answer.
I inserted comments below.
You welcome.
I think any API issues could be worked out. Are there any programs
you know of,
(yours?), that import pydoc besides the python console?
What I did barely qualifies as a hack
Finally, after a few months worth of work, I have finally gotten far enough
in my import rewrite that I am willing to stick my neck out and say it is
semantically complete! You can find it in the sandbox under import_in_py.
So, details of this implementation. I implemented PEP 302
Andrea Griffini schrieb:
I've a partially related question... why isn't the module structure in
an include file .h
and is instead in Objects/moduleobject.c ?
For the cached lookup optimization I copied the definition but that's surely
a bad way to do it I however wondered if there were
Ron Adam wrote:
Laurent Gautier wrote:
From the top of my head, there might be ipython (the excellent
interactive console) is possibly using pydoc
(in any case, I would say that the authors would be interested in
developments with pydoc)
Certainly :) I'd like to ask whether this
2007/1/6, Ron Adam [EMAIL PROTECTED]:
Laurent Gautier wrote:
[cut]
I think any API issues could be worked out. Are there any programs
you know of,
(yours?), that import pydoc besides the python console?
What I did barely qualifies as a hack for my own usage -it won't count-.
It
At 06:35 PM 1/5/2007 -0700, Fernando Perez wrote:
Ron Adam wrote:
Laurent Gautier wrote:
From the top of my head, there might be ipython (the excellent
interactive console) is possibly using pydoc
(in any case, I would say that the authors would be interested in
developments
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 5, 2007, at 9:41 PM, Phillip J. Eby wrote:
Unless there's been a complete rewrite of epydoc since the last time I
looked at it, I'd have to give a very strong -1 against epydoc; it
has all
the problems of pydoc, plus new ones.
I haven't
21 matches
Mail list logo
