SWAMPy

✎ CARVE FLESH

EDITING: hacking.rst.txt

Hacking on :mod:`zope.event`
============================

Getting the Code
################

The main repository for :mod:`zope.event` is in the Zope Foundation
Github repository:

https://github.com/zopefoundation/zope.event

You can get a read-only checkout from there:

.. code-block:: sh

$ git clone https://github.com/zopefoundation/zope.event.git

or fork it and get a writeable checkout of your fork:

.. code-block:: sh

$ git clone git@github.com/jrandom/zope.event.git

The project also mirrors the trunk from the Github repository as a
Bazaar branch on Launchpad:

https://code.launchpad.net/zope.event

You can branch the trunk from there using Bazaar:

.. code-block:: sh

$ bzr branch lp:zope.event

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:

.. code-block:: sh

$ /path/to/virtualenv --no-site-packages /tmp/hack-zope.event

Next, get this package registered as a "development egg" in the
environment:

.. code-block:: sh

$ /tmp/hack-zope.event/bin/python setup.py develop

Running the tests
-----------------

Then, you canrun the tests using the build-in ``setuptools`` testrunner:

.. code-block:: sh

$ /tmp/hack-zope.event/bin/python setup.py test
   running test
   ...
   test_empty (zope.event.tests.Test_notify) ... ok
   test_not_empty (zope.event.tests.Test_notify) ... ok

----------------------------------------------------------------------
   Ran 2 tests in 0.000s

If you have the :mod:`nose` package installed in the virtualenv, you can
use its testrunner too:

.. code-block:: sh

$ /tmp/hack-zope.event/bin/easy_install nose
   ...
   $ /tmp/hack-zope.event/bin/python setup.py nosetests
   running nosetests
   ...
   ----------------------------------------------------------------------
   Ran 3 tests in 0.011s

or:

.. code-block:: sh

$ /tmp/hack-zope.event/bin/nosetests
   ...
   ----------------------------------------------------------------------
   Ran 3 tests in 0.011s

If you have the :mod:`coverage` pacakge installed in the virtualenv,
you can see how well the tests cover the code:

.. code-block:: sh

$ /tmp/hack-zope.event/bin/easy_install nose coverage
   ...
   $ /tmp/hack-zope.event/bin/python setup.py nosetests \
       --with coverage --cover-package=zope.event
   running nosetests
   ...
   Name         Stmts   Exec  Cover   Missing
   ------------------------------------------
   zope.event       5      5   100%   
   ----------------------------------------------------------------------
   Ran 3 tests in 0.019s

Building the documentation
--------------------------

:mod:`zope.event` uses the nifty :mod:`Sphinx` documentation system
for building its docs.  Using the same virtualenv you set up to run the
tests, you can build the docs:

.. code-block:: sh

$ /tmp/hack-zope.event/bin/easy_install Sphinx
   ...
   $ cd docs
   $ PATH=/tmp/hack-zope.event/bin:$PATH make html
   sphinx-build -b html -d _build/doctrees   . _build/html
   ...
   build succeeded.

Build finished. The HTML pages are in _build/html.

You can also test the code snippets in the documentation:

.. code-block:: sh

$ PATH=/tmp/hack-zope.event/bin:$PATH make doctest
   sphinx-build -b doctest -d _build/doctrees   . _build/doctest
   ...
   running tests...

Document: index
   ---------------
   1 items passed all tests:
     17 tests in default
   17 tests in 1 items.
   17 passed and 0 failed.
   Test passed.

Doctest summary
   ===============
      17 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 :mod:`zc.buildout`
########################

Setting up the buildout
-----------------------

:mod:`zope.event` ships with its own :file:`buildout.cfg` file and
:file:`bootstrap.py` for setting up a development buildout:

.. code-block:: sh

$ /path/to/python2.6 bootstrap.py
   ...
   Generated script '.../bin/buildout'
   $ bin/buildout
   Develop: '/home/jrandom/projects/Zope/zope.event/.'
   ...
   Generated script '.../bin/sphinx-quickstart'.
   Generated script '.../bin/sphinx-build'.

Running the tests
-----------------

You can now run the tests:

.. code-block:: sh

$ bin/test --all
   Running zope.testing.testrunner.layer.UnitTests tests:
     Set up zope.testing.testrunner.layer.UnitTests in 0.000 seconds.
     Ran 2 tests with 0 failures and 0 errors in 0.000 seconds.
   Tearing down left over layers:
     Tear down zope.testing.testrunner.layer.UnitTests in 0.000 seconds.

Using :mod:`tox`
################

Running Tests on Multiple Python Versions
-----------------------------------------

`tox <http://tox.testrun.org/latest/>`_ 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.
   
:mod:`zope.event` configures the following :mod:`tox` environments via
its ``tox.ini`` file:

- The ``py26``, ``py27``, ``py33``, ``py34``, and ``pypy`` environments
  builds a ``virtualenv`` with the corresponding interpreter,
  installs :mod:`zope.event` and dependencies, and runs the tests
  via ``python setup.py -q test -q``.

- The ``coverage`` environment builds a ``virtualenv`` with ``python2.6``,
  installs :mod:`zope.event`, installs
  :mod:`nose` and :mod:`coverage`, and runs ``nosetests`` with statement
  and branch coverage.

- The ``docs`` environment builds a virtualenv with ``python2.6``, installs
  :mod:`zope.event`, installs ``Sphinx`` 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``:

.. code-block:: sh

$ tox -e py26
   GLOB sdist-make: .../zope.event/setup.py
   py26 sdist-reinst: .../zope.event/.tox/dist/zope.event-4.0.2dev.zip
   py26 runtests: commands[0]
   ...
   ----------------------------------------------------------------------
   Ran 2 tests in 0.000s

OK
   ___________________________________ summary ____________________________________
   py26: commands succeeded
   congratulations :)

Running ``tox`` with no arguments runs all the configured environments,
including building the docs and testing their snippets:

.. code-block:: sh

$ tox
   GLOB sdist-make: .../zope.event/setup.py
   py26 sdist-reinst: .../zope.event/.tox/dist/zope.event-4.0.2dev.zip
   py26 runtests: commands[0]
   ...
   Doctest summary
   ===============
    17 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 :mod:`zope.event`
#################################

Submitting a Bug Report
-----------------------

:mod:`zope.event` tracks its bugs on Github:

https://github.com/zopefoundation/zope.event/issues

Please submit bug reports and feature requests there.

Sharing Your Changes
--------------------

.. note::

Please ensure that all tests are passing before you submit your code.
   If possible, your submission should include new tests for new features
   or bug fixes, although it is possible that you may have tested your
   new code by updating existing tests.

If have made a change you would like to share, the best route is to fork
the Githb repository, check out your fork, make your changes on a branch
in your fork, and push it.  You can then submit a pull request from your
branch:

https://github.com/zopefoundation/zope.event/pulls

If you branched the code from Launchpad using Bazaar, you have another
option:  you can "push" your branch to Launchpad:

.. code-block:: sh

$ bzr push lp:~jrandom/zope.event/cool_feature

After pushing your branch, you can link it to a bug report on Github,
or request that the maintainers merge your branch using the Launchpad
"merge request" feature.

CANCEL

Name	Type	Size	Modified	Actions
↩ ..	DIR	—	—
📄 api.rst.txt	TXT	238 B	2015-01-22 16:27	EDIT
📄 api.txt	TXT	238 B	2015-01-22 16:27	EDIT
📄 classhandler.rst.txt	TXT	1.1 KB	2016-02-17 14:26	EDIT
📄 classhandler.txt	TXT	1.1 KB	2016-02-17 14:26	EDIT
📄 hacking.rst.txt	TXT	8.4 KB	2015-02-16 15:00	EDIT
📄 hacking.txt	TXT	8.4 KB	2015-02-16 15:00	EDIT
📄 index.rst.txt	TXT	624 B	2016-02-17 14:26	EDIT
📄 index.txt	TXT	624 B	2016-02-17 14:26	EDIT
📄 theory.rst.txt	TXT	493 B	2015-01-22 16:27	EDIT
📄 theory.txt	TXT	493 B	2015-01-22 16:27	EDIT
📄 usage.rst.txt	TXT	1.8 KB	2015-01-22 16:27	EDIT
📄 usage.txt	TXT	1.8 KB	2015-01-22 16:27	EDIT