The online docs are very good. Just run "perldoc perl", and then go
through the various tutorial pages (starting with "perldoc perlintro").
You can also read them online here: http://perldoc.perl.org/perl.html .
Then go to http://www.perlmonks.org . They have many tutorial-style
articles there, as
> so you think that a "why all this creativity when you could just
> standardize on something ported from java, and throw away every-
> thing else" post is friendly ? really ?
Sorry for the sloppy writing. Thanks for clarifying. I wrote:
> If unittest is the standard way to write test code, why
> and you can kill two birds with one stone.
By that, do you mean you can write your tests and your
docstrings in one shot with doctest?
> I would like to see yet another alternatise such as py.test
> in the standard lib,
Ah: http://codespeak.net/py/current/doc/home.html
--
http://mail.python.
> because it's a vastly superior way to write tests ?
Well, since this is a mailing list where this sort of thing is
discussed, and since I was was asking about which way
is preferred, could you tell us why you (presumably) think
doctest is vastly superior to unittest?
> why is it that comp.lang.
For writing testcode, it looks like there's three ways that it's
typically done:
(1). using the doctest module,
(2). using the unittest module (i.e. "pyunit"), or else
(3). just putting an "if __name__ = '__main__':" at the bottom of your
module containing code to manually run your class through
Tim Roberts wrote:
> "Dave" <[EMAIL PROTECTED]> wrote:
> >
> >Please be mindful of making statements such as:
> >"it's silly to believe both will behave equally"
> >
> >One of the greatest weaknesses of Python is the less than friendly
> >attitude Pythonistas display towards one another.
>
> I don
Jason Earl wrote:
> "msoulier" <[EMAIL PROTECTED]> writes:
>
> >> I have found the Python sidebar VERY helpful:
> >
> > Personally, I can't use local docs on my desktop as they may not be
> > the same version of the docs for the Python distro running on the
> > server that I'm deploying on. I usua
msoulier wrote:
>
> [snip]
> But, if Python would match Perl for docs available on the command-line,
> then I'd have it all at my fingertips. I simply don't understand why
> this is not being done. [snip]
>
> Mike
Ok, well, here's my attempt to begin to make that happen:
http://www.simisen.com/jm
> And the patch procedure you described requires
> a higher degree of motivation (and free time) than
> most potential contributors might have on offer, imo.
Another option is to simply email the author/maintainer
for a given module your modifications to their module.
cd ~/dev/python/modified_mod
Well, we've already got a wiki, of course: http://wiki.python.org/moin/
Regarding the docs for the module you're asking about, the way it's
supposed to work is (I think), you're supposed to checkout the Python
source, add your docs to the docstrings of that module, then either
commit your changes
Ok. I'm going to try and make something happen. Give me a day or so.
:)
---John
--
http://mail.python.org/mailman/listinfo/python-list
> So far epytext suited my needs.
I like it too.
Ok, now I'm starting to get excited. :)
--
http://mail.python.org/mailman/listinfo/python-list
Thanks Diez! Epydoc looks great.
Can we use epytext to generate output suitable for a manpage?
Do you prefer epytext or reST?
--
http://mail.python.org/mailman/listinfo/python-list
Just tried Ruby over the past two days. I won't bore you
with the reasons I didn't like it, however one thing really
struck me about it that I think we (the Python community)
can learn from.
Ruby has ... an issue with docs. That is to say, there are
almost none. Well, actually, there are some. For
I've got a fairly substantial webapp written in Java (plus Tomcat,
Hibernate, Struts, JSP, MySQL) that is a bit of a bear to work with. I
didn't write it. Much of it is only very sparsely documented (if at
all). No design docs anywhere. It's a large webapp with many classes
and fairly deep inherita
15 matches
Mail list logo
