I couldn't find install instructions at http://pywebtool.sourceforge.net/,
so I faked it. Here's what I did, after moving the tarball to the
site-packages directory of my Python 3.4 virtual environment:
$ tar xvzf pyweb-2.3.1.ta.gz
$ cd pyweb-2.3.1
$ python setup.py install
That seemed to work okay; I have a pyweb-2.3.1-py3.4.egg-info file.
Then I tried the RST test:
$ cd test
$ python3 -m pyweb -wRST test_rst.w
And got this stack trace:
$ python3 -m pyweb -wRST test_rst.w
Traceback (most recent call last):
File "/opt/local/stow/python-3.4.2/lib/python3.4/runpy.py", line 170, in _run_module_as_main
"main", mod_spec)
File "/opt/local/stow/python-3.4.2/lib/python3.4/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/home/wdg.nrao.edu/content/Envs/p3/lib/python3.4/site-packages/pyweb.py", line 1913, in <module>
main( )
File "/home/wdg.nrao.edu/content/Envs/p3/lib/python3.4/site-packages/pyweb.py", line 1909, in main
a.process(config)
File "/home/wdg.nrao.edu/content/Envs/p3/lib/python3.4/site-packages/pyweb.py", line 1841, in process
self.logger.info( "Weaver {:s}".format(config.theWeaver) )
TypeError: non-empty format string passed to object.format</module>
Where did I go off the rails?
Best regards,
John W. Shipman, Web Developer, National Radio Astronomy Observatory
jshipman@nrao.edu, P. O. Box O, Socorro, NM 87801, cell (505)249-3839
There's a README. http://pywebtool.sourceforge.net/#the-readme-file
But that's not obvious enough. I'll look at revising the documentation to make it more clear.
https://bugs.python.org/issue7994 has cleaned up the way the {:s} format string works.
Each occurrence of
{:s}was fundamentally wrong and needs to be replaced with{!s}. I'll post a new release.Last edit: Steven F. Lott 2014-12-04