There shouldn't be any bridgehead between "Optional Download" and
<itemizedlist>. Otherwise, jhalfs does not see the itemized list.
Note that this is a recent change in jhalfs for coping with other
places where there are several itemized lists, and only the first
one should be used...
Now all sourceforge.net subdomains have a valid SSL certificate. The
changes are automatically done via a sed. I've reviewed the changes and
reverted the changes in archive/*, pst/xml/docbook-xsl.xml, and
stylesheets/lfs-xsl/lfs-l10n.xml. Other changes should (hopefully) be
fine.
It is not easy to make one's mind whether a dash or an underscore
should be used: pypi, and doc, use hatch-vcs. But tarball name
nd installed module directories have hatch_vcs (note that dashes
are forbidden in python module names). So use hatch_vcs in written
text (don't change the dash in the entities and the id).
If using this option, the build system uses a newly built version
of ruby instead of the installed version of ruby, if it is
already installed. This is worth documenting.
We will change pythonhosted.xml to incorporate all python modules
(perhaps excepting PyXDG) at https://files.pythonhosted.org
and move it to the top of the Python Modules page.
We will need to place the md5sums for the module sources in packages.ent
so they can be referenced in two places.
For now, remove the page from the build. Later we will need to clean up
Makefile and archive stylesheets/{pyhosted-inc,pythonhosted}.xsl.
This branch introduces a new layout for python modules, similar
to what is done for perl modules. This allows to have useful python
modules in the book (sphinx, pytest, requests, gi-docgen), together
with their dependencies.
As a convenience for users who build by hand, a "Building
pythonhosted.org Files" section is added, which allows building all
the python modules dependencies in one go. It is generated from
the individual module pages, so the authoritative instructions are
on those individual pages.
