On Sun, Apr 03, 2011, Guido Carballo-Guerrero wrote:
>
> I just start writing a tutorial about Python, and will like to share
> it with you guys. It's a project that I just start, so any comment is
> very much appreciated:
>
> http://web.me.com/charras/Python/Welcome.html
If you're looking for fee
Hi Guido,
have you had a look at the official tutorial [1]_ and the Using Python
[2]_ guides? If so, what did you find particularly lacking about
them? We are always open for suggestions and happy to improve! (I'm
keeping this on-list purposefully for these questions; we usually
discuss the *P
I just start writing a tutorial about Python, and will like to share it with
you guys. It's a project that I just start, so any comment is very much
appreciated:
http://web.me.com/charras/Python/Welcome.html
Guido Carballo
___
Doc-SIG maillist - Doc
Martin Blais wrote:
> > javadoc's
> >
> > [EMAIL PROTECTED] os.popen}
> >
> > is even shorter.
> >
> > hmm. maybe a combination of rest/html/whatever and pythondoc markup
> > would be the ultimate tool for the library reference...
>
> <* heavy clapping sound of my footsteps while running away
On 12/22/05, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> Fred L. Drake, Jr. wrote:
>
> > Whether :function:`os.popen()` is any uglier than \function{os.popen()} is
> > largely a matter of what you're used to. I will note that the LaTeX version
> > is one character shorter. :-)
>
> javadoc's
>
>
Fred L. Drake, Jr. wrote:
> Whether :function:`os.popen()` is any uglier than \function{os.popen()} is
> largely a matter of what you're used to. I will note that the LaTeX version
> is one character shorter. :-)
javadoc's
[EMAIL PROTECTED] os.popen}
is even shorter.
hmm. maybe a combin
Is there a list somewhere of exactly what it is that would need to be
added to ReST in order to support writing Python documentation in
ReST?
Laura
___
Doc-SIG maillist - Doc-SIG@python.org
http://mail.python.org/mailman/listinfo/doc-sig
On 12/22/05, Fred L. Drake, Jr. <[EMAIL PROTECTED]> wrote:
> On Thursday 22 December 2005 10:47, Martin Blais wrote:
> > Well, be disappointed.
> > It does not currently, and most likely won't.
>
> Yes and no.
>
> Docutils provides support for creating new directives ("dot-dot things") and
> inte
On Thursday 22 December 2005 10:47, Martin Blais wrote:
> Well, be disappointed.
> It does not currently, and most likely won't.
Yes and no.
Docutils provides support for creating new directives ("dot-dot things") and
interpreted text roles (":colon: things"). These would go a long way to
do
On Thursday 22 December 2005 09:57, Aahz wrote:
> Submit in reST or plain-text and someone will do any necessary
> conversions. Really, don't worry about it, Just Do It.
For the record, I've assigned Fuzzyman's issue to myself, but we should make
it easier for other Python project members to r
On Thursday 22 December 2005 10:06, Martin Blais wrote:
> Convert it to LaTeX (it's easy) and submit it.
Or just submit as ReST, and request conversion. I like spending my time in
XEmacs. :-)
> The LaTeX input format using the macros from the python docs is very
> simple. Converting your d
A.M. Kuchling wrote:
> On Thu, Dec 22, 2005 at 10:06:48AM -0500, Martin Blais wrote:
>
>>Your tutorial is great. Read it a while ago. Would love to see it
>>along the other tutorials or even in the library docs for the module
>>(as the urllib2 docs are a bit thin on explanations).
>
>
> There'
On Thu, Dec 22, 2005 at 10:06:48AM -0500, Martin Blais wrote:
> Your tutorial is great. Read it a while ago. Would love to see it
> along the other tutorials or even in the library docs for the module
> (as the urllib2 docs are a bit thin on explanations).
There's also the Doc/howto directory.
> >>By the way my vote is -1 on moving to html as the standard markup format
> >>and +1 on working on docutils to turn that into an usable input format.
> >>Additionally - having a wiki version, or a version that accepts user
> >>commentary would be a very useful way of gathering additional
> >>inf
Martin Blais wrote:
> On 12/22/05, Michael Foord <[EMAIL PROTECTED]> wrote:
>
>>By the way (and in the vain (sic) of shameless self-promotion...) there
>>was a suggestion on Dobbs Python-URL that the inclusion of some of my
>>material on urllib2 would be welcome in the tutorial.
>>
>>http://groups
On 12/22/05, Michael Foord <[EMAIL PROTECTED]> wrote:
> By the way (and in the vain (sic) of shameless self-promotion...) there
> was a suggestion on Dobbs Python-URL that the inclusion of some of my
> material on urllib2 would be welcome in the tutorial.
>
> http://groups.google.com/group/comp.lan
On Thu, Dec 22, 2005, Michael Foord wrote:
>
> Is reST acceptable for *someone* to add this material - and if so, what
> should I do about it ?
Submit in reST or plain-text and someone will do any necessary
conversions. Really, don't worry about it, Just Do It.
--
Aahz ([EMAIL PROTECTED])
Michael Foord wrote:
> By the way my vote is -1 on moving to html as the standard markup format
> and +1 on working on docutils to turn that into an usable input format.
so how to you plan to achieve the required level of semantic markup in ReST?
Michael Foord wrote:
> By the way (and in the vain (sic) of shameless self-promotion...) there
> was a suggestion on Dobbs Python-URL that the inclusion of some of my
> material on urllib2 would be welcome in the tutorial.
>
> http://groups.google.com/group/comp.lang.python/browse_frm/thread/1d528
By the way (and in the vain (sic) of shameless self-promotion...) there
was a suggestion on Dobbs Python-URL that the inclusion of some of my
material on urllib2 would be welcome in the tutorial.
http://groups.google.com/group/comp.lang.python/browse_frm/thread/1d52898f07b7dfcd/d015de23ad6818fa
M
20 matches
Mail list logo
