I posted this on comp.lang.python and only got one email back. Maybe
someone here could point me to a package python package that does man pages
right. I know I am a dinosaur for still liking man pages. And a follow
on... I just grabbed that 3.0 alpha of epydoc and after using it for two
weeks, I REALLY like it, but it has some quirks. I haven't heard back from
the author, but what is the current state of documentation best practice for
python. I got frustrated by lack of features from pydoc and doxygen doesn't
really understand python that well.
my nntp post...
I am rearranging the layout of one of my python projects so that it
more closely conforms to how most python projects seem to work. I now
have a structure like this:
- bulk of the code
- programs that go in bin
I am using OptionParser, help2man, groff and man2html to provide man
pages. Everything was sitting in the top level directory, so it was
clear where to put these, but where do I put the foo.help2man files
that contain extra text for the man pages? If I put it in scripts,
that is pretty easy to cope with, but I was thinking about a docs
directory, but then the build process might be more difficult. Or
should I be putting in another string in each executable that contains
this extra man page info? Then it would show up in epydoc as well.
Maybe something like
__help2man__ = '''
The --coord-unit option is designed to allow use of databases that
exclude the CoordUnit field. This field is probably the same for all
traces in the majority of SEGY data files, so most segy-py drivers
will want to exclude coordunit from the short list (see segysql.py).
The values are taken from page 14 of the SEG-Y Rev 1 specification
-1 = Follow field 89-90 of the trace header
1 = Length (meters or feet) [NOT supported]
2 = Seconds of arc
3 = Degrees, minutes, seconds (DMS) [NOT SUPPORTED]
I am still in the middle of shuffling the tree about, but it is
Any thoughts would be greatly appreciated! I am still trying to
understand the best practices for python packaging.
- bulk of the code *.py
- programs that go in bin/the users executable path (no .py
For Mac OSX 10.4 folks...
Now that the sf.net cvs server is back alive, I have added setuptools and
sqlalchemy to the 10.4-transitional/unstable tree. Any reports of success,
failure, or suggestions would be greatly appreciated! Once this has been
out there for a few days, I will try package a couple other things that need
setuptools. BTW, I am holding off on pysqlite2 in fink since I think that
will break existing trac installs. Any suggestions on handling that?
fink install setuptools-py24
fink install sqlalchemy-py24
After running this (break.py)::
import os, shutil, distutils.dir_util
I get this error::
Traceback (most recent call last):
File "break.py", line 8, in ?
File "C:\Python24\lib\distutils\dir_util.py", line 175, in copy_tree
preserve_times, update, dry_run=dry_run)
File "C:\Python24\lib\distutils\file_util.py", line 165, in copy_file
File "C:\Python24\lib\distutils\file_util.py", line 47, in _copy_file_contents
fdst = open(dst, 'wb')
IOError: [Errno 2] No such file or directory: './b\\testfile'
Am I doing something wrong?
Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates starting at 1¢/min.