<commit_before>Contribute
==========

This page is intended for developers of (or contributing to) PyPubSub.

.. contents:: In this section:
   :depth: 1
   :local:


.. _label-contributing:

Contributing
------------

Contributions are welcome! There are many ways you could contribute:

- bug fixes
- new features
- test results on different platforms
- documentation
- screencasts! (of applications using PyPubSub with output when user clicks)
- example topic trees (using ``pubsub.utils.printTopicTree()`` in latest
  version, or ``print Publisher`` in versions 1)
- other improvements
- money!

Please contact by posting on the forum pypubsub-dev forum (link in the
:ref:`label-support` section) or via http://github/schollii/pypubsub.


System Requirements
-------------------

In addition to the :ref:`label-install-reqs`, the following are required:

- To run unit tests:

  - pytest

- To generate the docs:

  - sphinx >= 1.4.8
  - In PyPubSub 3.3, which used an older version of sphinx, sphinx had to be patched as per post on
    sphinx-dev, but this no longer seems to be the required:

    .. literalinclude:: sphinx_patch1.txt
    .. literalinclude:: sphinx_patch2.txt

- To change code: PyCharm is recommended (Community Edition is sufficient). Various
  build configurations are available via the PyPubSub project when loaded into PyCharm.


Scripts Available
-----------------

*Unit Testing*:
    The test suite is most conveniently run from PyCharm via the "py.test in suite"
    build configuration. The tests can also be run automatically via pytest suite from
    the :file:`tests` folder.

    Once this passes using the project's default interpreter, a Terminal can be
    opened in PyCharm (or alternately a command shell from Windows), and from
    the PyPubSub root folder, run :command:`tox`. This will attempt to run the
    test suite in every 3.x version of Python, x>=3 (ie 3.3, 3.4, etc).

    After changes are committed to github, the Travis CI will automatically
    run the tests on a Linux platform, for all versions of Python supported
    by PyPubSub. The results will be at https://travis-ci.org/schollii/pypubsub/builds.

    There is also a buildbot maintained by <NAME> to test on additional
    \*nix flavors, including OSX. Test results can be viewed at
    https://jeromelaheurte.net/buildbot/pubsub/console.

*Performance Test*:
    A small performance test is available in the :file:`tests` folder.
    It can be run from PyCharm via the perf build configuration. This will
    generate a new :file:`.pstats` file which can be analysed.
    The test can also be run directly from command shell via
    :command:`python perf.py 1000`. The test is meant to compare the impact
    of changes before/after and is designed to compare on results on the
    same system (hardwards, OS).

*Documentation*:
    The documentation can be generated locally on Windows via the Gen Docs build
    configuration in PyCharm. Alternatively, it can be generated by running
    :command:`make html` from the :file:`docs` folder of source
    distribution.

    The documentation is automatically built and available online at
    http://pypubsub.readthedocs.io. The latest from master branch is at
    http://pypubsub.readthedocs.io/en/master/. The stable (released)
    documentation is at http://pypubsub.readthedocs.io/en/stable/.


Releases
--------

PyPubSub uses the latest stable Python packaging and distribution tools:
wheel, twine, and pypi.

Generating a new release involves the following sequence of steps:

- Verify that tox, sphinx, wheel, twine, and setuptools are installed.
- Ensure that pytest suite runs 100%, and that the examples run without error in
  examples/ folder (one of the examples requires wxPython -- install latest stable)
- Ensure that `tox` (run from pypubsub root folder) runs to completion without errors or
  warnings on all versions of Python (3.x)
- Update version number via a search-replace in the `Version Change` scope of PyCharm:

    - src/pubsub/__init__.py: version
    - docs/changelog.rst
    - src/pubsub/RELEASE_NOTES.txt
    - README.rst

- Add section at top of `docs/changelog.rst` with details of what changed (audience: pypubsub developers)
- Update `src/pubsub/RELEASE_NOTES.txt` (audience: pypubsub end-users) to have high-level summary
  of changes for this release, handling incompatibilities, etc
- Update the setup.py classifiers (such as adding a new version of Python supported)
- In docs folder:

  - Update index.rst and docs/installation.rst
  - Regenerate HTML docs via `make`, confirm ok (no warnings etc)

Persist to server:

- Commit and push to remote master repository
- Confirm that travis CI all pass

Distribute:

- Clean out the `dist/` folder
- Generate the source and wheel distributions: `python setup.py bdist_wheel sdist`
- Upload to PyPI: twine upload dist/\*:
- Verify new release info and links on pypi.python.org
- Create new branch (tag) in remote master repository
- Confirm installation will work: attempt to install locally via PyPI, then import
  from Python shell


Py2Exe and cx_Freeze
--------------------

For packaging py2exe or cx_Freeze, see (possibly out of date):

.. toctree::

   py2exe.rst<commit_msg>CHG: clarify distribution steps<commit_after>Contribute
==========

This page is intended for developers of (or contributing to) PyPubSub.

.. contents:: In this section:
   :depth: 1
   :local:


.. _label-contributing:

Contributing
------------

Contributions are welcome! There are many ways you could contribute:

- bug fixes
- new features
- test results on different platforms
- documentation
- screencasts! (of applications using PyPubSub with output when user clicks)
- example topic trees (using ``pubsub.utils.printTopicTree()`` in latest
  version, or ``print Publisher`` in versions 1)
- other improvements
- money!

Please contact by posting on the forum pypubsub-dev forum (link in the
:ref:`label-support` section) or via http://github/schollii/pypubsub.


System Requirements
-------------------

In addition to the :ref:`label-install-reqs`, the following are required:

- To run unit tests:

  - pytest

- To generate the docs:

  - sphinx >= 1.4.8
  - In PyPubSub 3.3, which used an older version of sphinx, sphinx had to be patched as per post on
    sphinx-dev, but this no longer seems to be the required:

    .. literalinclude:: sphinx_patch1.txt
    .. literalinclude:: sphinx_patch2.txt

- To change code: PyCharm is recommended (Community Edition is sufficient). Various
  build configurations are available via the PyPubSub project when loaded into PyCharm.


Scripts Available
-----------------

*Unit Testing*:
    The test suite is most conveniently run from PyCharm via the "py.test in suite"
    build configuration. The tests can also be run automatically via pytest suite from
    the :file:`tests` folder.

    Once this passes using the project's default interpreter, a Terminal can be
    opened in PyCharm (or alternately a command shell from Windows), and from
    the PyPubSub root folder, run :command:`tox`. This will attempt to run the
    test suite in every 3.x version of Python, x>=3 (ie 3.3, 3.4, etc).

    After changes are committed to github, the Travis CI will automatically
    run the tests on a Linux platform, for all versions of Python supported
    by PyPubSub. The results will be at https://travis-ci.org/schollii/pypubsub/builds.

    There is also a buildbot maintained by <NAME>te to test on additional
    \*nix flavors, including OSX. Test results can be viewed at
    https://jeromelaheurte.net/buildbot/pubsub/console.

*Performance Test*:
    A small performance test is available in the :file:`tests` folder.
    It can be run from PyCharm via the perf build configuration. This will
    generate a new :file:`.pstats` file which can be analysed.
    The test can also be run directly from command shell via
    :command:`python perf.py 1000`. The test is meant to compare the impact
    of changes before/after and is designed to compare on results on the
    same system (hardwards, OS).

*Documentation*:
    The documentation can be generated locally on Windows via the Gen Docs build
    configuration in PyCharm. Alternatively, it can be generated by running
    :command:`make html` from the :file:`docs` folder of source
    distribution.

    The documentation is automatically built and available online at
    http://pypubsub.readthedocs.io. The latest from master branch is at
    http://pypubsub.readthedocs.io/en/master/. The stable (released)
    documentation is at http://pypubsub.readthedocs.io/en/stable/.


Releases
--------

PyPubSub uses the latest stable Python packaging and distribution tools:
wheel, twine, and pypi.

Generating a new release involves the following sequence of steps:

- Verify that tox, sphinx, wheel, twine, and setuptools are installed.
- Ensure that pytest suite runs 100%, and that the examples run without error in
  examples/ folder (one of the examples requires wxPython -- install latest stable)
- Ensure that `tox` (run from pypubsub root folder) runs to completion without errors or
  warnings on all versions of Python (3.x)
- Update version number via a search-replace in the `Version Change` scope of PyCharm:

    - src/pubsub/__init__.py: version
    - docs/changelog.rst
    - src/pubsub/RELEASE_NOTES.txt
    - README.rst

- Add section at top of `docs/changelog.rst` with details of what changed (audience: pypubsub developers)
- Update `src/pubsub/RELEASE_NOTES.txt` (audience: pypubsub end-users) to have high-level summary
  of changes for this release, handling incompatibilities, etc
- Update the setup.py classifiers (such as adding a new version of Python supported)
- In docs folder:

  - Update index.rst and docs/installation.rst
  - Regenerate HTML docs via `make`, confirm ok (no warnings etc)

Persist to server:

- Commit and push to remote master repository
- Confirm that travis CI all pass

Distribute:

- Clean out the `dist/` folder
- Generate the source and wheel distributions: `python setup.py bdist_wheel sdist`
- Upload to PyPI: `twine upload dist/\*`
- Verify new release info and links on https://pypi.python.org
- Create new branch (tag) in github
- Verify documentation updated on pypubsub.readthedocs.io
- Confirm installation will work: attempt to install locally via PyPI, then import
  from Python shell and verify version


Py2Exe and cx_Freeze
--------------------

For packaging py2exe or cx_Freeze, see (possibly out of date):

.. toctree::

   py2exe.rst
{'fraction_non_alphanumeric': 0.08312819541753456, 'fraction_numerical': 0.004923309979170612, 'mean_word_length': 3.4796437659033077, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 9, 'https://': 5, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6862683', 'n_tokens_mistral': 3044, 'n_tokens_neox': 2888, 'n_words': 1358}