Hacking on zope.dublincore
¶
Getting the Code¶
The main repository for zope.dublincore
is in the Zope Foundation
Github repository:
You can get a read-only checkout from there:
$ git clone https://github.com/zopefoundation/zope.dublincore.git
or fork it and get a writeable checkout of your fork:
$ git clone git@github.com/jrandom/zope.dublincore.git
The project also mirrors the trunk from the Github repository as a Bazaar branch on Launchpad:
https://code.launchpad.net/zope.dublincore
You can branch the trunk from there using Bazaar:
$ bzr branch lp:zope.dublincore
Working in a virtualenv
¶
Installing¶
If you use the virtualenv
package to create lightweight Python
development environments, you can run the tests using nothing more
than the python
binary in a virtualenv. First, create a scratch
environment:
$ /path/to/virtualenv --no-site-packages /tmp/hack-zope.dublincore
Next, get this package registered as a “development egg” in the environment:
$ /tmp/hack-zope.dublincore/bin/python setup.py develop
Running the tests¶
Run the tests using the build-in setuptools
testrunner:
$ /tmp/hack-zope.dublincore/bin/python setup.py test
running test
........
----------------------------------------------------------------------
Ran 80 tests in 0.000s
OK
If you have the nose
package installed in the virtualenv, you can
use its testrunner too:
$ /tmp/hack-zope.dublincore/bin/easy_install nose
...
$ /tmp/hack-zope.dublincore/bin/nosetests
.......
----------------------------------------------------------------------
Ran 80 tests in 0.000s
OK
If you have the coverage
pacakge installed in the virtualenv,
you can see how well the tests cover the code:
$ /tmp/hack-zope.dublincore/bin/easy_install nose coverage
...
$ /tmp/hack-zope.dublincore/bin/nosetests --with coverage
running nosetests
......................................................................................
Name Stmts Miss Cover Missing
-----------------------------------------------------------------------
zope/dublincore.py 0 0 100%
zope/dublincore/annotatableadapter.py 73 73 100%
zope/dublincore/browser.py 0 0 100%
zope/dublincore/browser/metadataedit.py 21 21 100%
zope/dublincore/creatorannotator.py 24 24 100%
zope/dublincore/dcsv.py 92 92 100%
zope/dublincore/dcterms.py 65 65 100%
zope/dublincore/interfaces.py 72 72 100%
zope/dublincore/property.py 66 66 100%
zope/dublincore/timeannotators.py 27 27 100%
zope/dublincore/xmlmetadata.py 173 173 100%
zope/dublincore/zopedublincore.py 198 !98 100%
-----------------------------------------------------------------------
TOTAL 811 811 100%
----------------------------------------------------------------------
Ran 86 tests in 0.000s
OK
Building the documentation¶
zope.dublincore
uses the nifty Sphinx
documentation system
for building its docs. Using the same virtualenv you set up to run the
tests, you can build the docs:
$ /tmp/hack-zope.dublincore/bin/easy_install Sphinx
...
$ bin/sphinx-build -b html -d docs/_build/doctrees docs docs/_build/html
...
build succeeded.
You can also test the code snippets in the documentation:
$ bin/sphinx-build -b doctest -d docs/_build/doctrees docs docs/_build/doctest
...
Doctest summary
===============
73 tests
0 failures in tests
0 failures in setup code
build succeeded.
Testing of doctests in the sources finished, look at the \
results in _build/doctest/output.txt.
Using zc.buildout
¶
Setting up the buildout¶
zope.dublincore
ships with its own buildout.cfg
file and
bootstrap.py
for setting up a development buildout:
$ /path/to/python2.6 bootstrap.py
...
Generated script '.../bin/buildout'
$ bin/buildout
Develop: '/home/jrandom/projects/Zope/BTK/dublincore/.'
...
Generated script '.../bin/sphinx-quickstart'.
Generated script '.../bin/sphinx-build'.
Running the tests¶
Run the tests:
$ bin/test --all
Running zope.testing.testrunner.layer.UnitTests tests:
Set up zope.testing.testrunner.layer.UnitTests in 0.000 seconds.
Ran 400 tests with 0 failures and 0 errors in 0.366 seconds.
Tearing down left over layers:
Tear down zope.testing.testrunner.layer.UnitTests in 0.000 seconds.
Using tox
¶
Running Tests on Multiple Python Versions¶
tox is a Python-based test automation
tool designed to run tests against multiple Python versions. It creates
a virtualenv
for each configured version, installs the current package
and configured dependencies into each virtualenv
, and then runs the
configured commands.
zope.dublincore
configures the following tox
environments via
its tox.ini
file:
The
py26
,py27
,py33
,py34
, andpypy
environments builds avirtualenv
withpypy
, installszope.dublincore
and dependencies, and runs the tests viapython setup.py test -q
.The
coverage
environment builds avirtualenv
withpython2.6
, installszope.dublincore
, installsnose
andcoverage
, and runsnosetests
with statement coverage.The
docs
environment builds a virtualenv withpython2.6
, installszope.dublincore
, installsSphinx
and dependencies, and then builds the docs and exercises the doctest snippets.
This example requires that you have a working python2.6
on your path,
as well as installing tox
:
$ tox -e py26
GLOB sdist-make: .../zope.interface/setup.py
py26 sdist-reinst: .../zope.interface/.tox/dist/zope.interface-4.0.2dev.zip
py26 runtests: commands[0]
..........
----------------------------------------------------------------------
Ran 400 tests in 0.152s
OK
___________________________________ summary ____________________________________
py26: commands succeeded
congratulations :)
Running tox
with no arguments runs all the configured environments,
including building the docs and testing their snippets:
$ tox
GLOB sdist-make: .../zope.interface/setup.py
py26 sdist-reinst: .../zope.interface/.tox/dist/zope.interface-4.0.2dev.zip
py26 runtests: commands[0]
...
Doctest summary
===============
73 tests
0 failures in tests
0 failures in setup code
0 failures in cleanup code
build succeeded.
___________________________________ summary ____________________________________
py26: commands succeeded
py27: commands succeeded
py32: commands succeeded
pypy: commands succeeded
coverage: commands succeeded
docs: commands succeeded
congratulations :)
Contributing to zope.dublincore
¶
Submitting a Bug Report¶
zope.dublincore
tracks its bugs on Github:
Please submit bug reports and feature requests there.