1 new commit in pytest: https://bitbucket.org/pytest-dev/pytest/commits/de09a4c6bc60/ Changeset: de09a4c6bc60 User: bubenkoff Date: 2015-02-27 13:58:27+00:00 Summary: Merged in docs_community (pull request #254)
added documentationo on the new pytest-dev teams on bitbucket and Affected #: 16 files diff -r 1abf285d64ae7fcfaee1fcd01c045357a8a7411b -r de09a4c6bc60c27686245e705947439270e2c69b CHANGELOG --- a/CHANGELOG +++ b/CHANGELOG @@ -3,6 +3,10 @@ - add ability to set command line options by environment variable PYTEST_ADDOPTS. +- added documentation on the new pytest-dev teams on bitbucket and + github. See https://pytest.org/latest/contributing.html . + Thanks to Anatoly for pushing and initial work on this. + - fix issue650: new option ``--docttest-ignore-import-errors`` which will turn import errors in doctests into skips. Thanks Charles Cloud for the complete PR. diff -r 1abf285d64ae7fcfaee1fcd01c045357a8a7411b -r de09a4c6bc60c27686245e705947439270e2c69b CONTRIBUTING.rst --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -1,18 +1,59 @@ -============ -Contributing -============ +============================ +Contribution getting started +============================ Contributions are highly welcomed and appreciated. Every little help counts, so do not hesitate! +.. contents:: Contribution links + :depth: 2 -Types of contributions -====================== + +.. _submitplugin: + +Submit a plugin, co-develop pytest +---------------------------------- + +Pytest development of the core, some plugins and support code happens +in repositories living under: + +- `the pytest-dev bitbucket team <https://bitbucket.org/pytest-dev>`_ + +- `the pytest-dev github organisation <https://github.com/pytest-dev>`_ + +All pytest-dev team members have write access to all contained +repositories. pytest core and plugins are generally developed +using `pull requests`_ to respective repositories. + +You can submit your plugin by subscribing to the `pytest-dev mail list +<https://mail.python.org/mailman/listinfo/pytest-dev>`_ and writing a +mail pointing to your existing pytest plugin repository which must have +the following: + +- PyPI presence with a ``setup.py`` that contains a license, ``pytest-`` + prefixed, version number, authors, short and long description. + +- a ``tox.ini`` for running tests using `tox <http://tox.testrun.org>`_. + +- a ``README.txt`` describing how to use the plugin and on which + platforms it runs. + +- an issue tracker unless you rather want to use the core ``pytest`` + issue tracker. + +If no contributor strongly objects and two agree, the repo will be +transferred to the ``pytest-dev`` organisation and you'll become a +member of the ``pytest-dev`` team, with commit rights to all projects. +We recommend that each plugin has at least three people who have the +right to release to pypi. + + +.. _reportbugs: Report bugs ----------- -Report bugs at https://bitbucket.org/hpk42/pytest/issues. +Report bugs for pytest at https://bitbucket.org/pytest-dev/pytest/issues If you are reporting a bug, please include: @@ -22,13 +63,15 @@ installed libraries and pytest version. * Detailed steps to reproduce the bug. +.. _submitfeedback: + Submit feedback for developers ------------------------------ Do you like pytest? Share some love on Twitter or in your blog posts! We'd also like to hear about your propositions and suggestions. Feel free to -`submit them as issues <https://bitbucket.org/hpk42/pytest/issues>`__ and: +`submit them as issues <https://bitbucket.org/pytest-dev/pytest/issues>`__ and: * Set the "kind" to "enhancement" or "proposal" so that we can quickly find about them. @@ -37,21 +80,24 @@ * If you have required skills and/or knowledge, we are very happy for :ref:`pull requests <pull-requests>`. +.. _fixbugs: Fix bugs -------- Look through the BitBucket issues for bugs. Here is sample filter you can use: -https://bitbucket.org/hpk42/pytest/issues?status=new&status=open&kind=bug +https://bitbucket.org/pytest-dev/pytest/issues?status=new&status=open&kind=bug :ref:`Talk <contact>` to developers to find out how you can fix specific bugs. +.. _writeplugins: + Implement features ------------------ Look through the BitBucket issues for enhancements. Here is sample filter you can use: -https://bitbucket.org/hpk42/pytest/issues?status=new&status=open&kind=enhancement +https://bitbucket.org/pytest-dev/pytest/issues?status=new&status=open&kind=enhancement :ref:`Talk <contact>` to developers to find out how you can implement specific features. @@ -67,6 +113,7 @@ * Blog posts, articles and such -- they're all very appreciated. .. _pull-requests: +.. _`pull requests`: Preparing Pull Requests on Bitbucket ===================================== @@ -74,7 +121,7 @@ .. note:: What is a "pull request"? It informs project's core developers about the changes you want to review and merge. Pull requests are stored on - `BitBucket servers <https://bitbucket.org/hpk42/pytest/pull-requests>`__. + `BitBucket servers <https://bitbucket.org/pytest-dev/pytest/pull-requests>`__. Once you send pull request, we can discuss it's potential modifications and even add more commits to it later on. @@ -82,7 +129,7 @@ the issues there and submit your pull requests. 1. Fork the - `pytest BitBucket repository <https://bitbucket.org/hpk42/pytest>`__. It's + `pytest BitBucket repository <https://bitbucket.org/pytest-dev/pytest>`__. It's fine to use ``pytest`` as your fork repository name because it will live under your user. @@ -149,12 +196,12 @@ source: YOUR_BITBUCKET_USERNAME/pytest branch: your-branch-name - target: hpk42/pytest + target: pytest-dev/pytest branch: default .. _contribution-using-git: -What about git (and so GitHub)? +Using git with bitbucket/hg ------------------------------- There used to be the pytest GitHub mirror. It was removed in favor of the @@ -162,10 +209,10 @@ put their issues and pull requests. Also it wasn't easily possible to automate the mirroring process. -However, it's still possible to use git to contribute to pytest using tools -like `gitifyhg <https://github.com/buchuki/gitifyhg>`_ which allows you to -clone and work with Mercurial repo still using git. +In general we recommend to work with the same version control system of the +original repository. If you insist on using git with bitbucket/hg you +may try `gitifyhg <https://github.com/buchuki/gitifyhg>`_ but are on your +own and need to submit pull requests through the respective platform, +nevertheless. -.. warning:: - Remember that git is **not** a default version control system for pytest and - you need to be careful using it. + diff -r 1abf285d64ae7fcfaee1fcd01c045357a8a7411b -r de09a4c6bc60c27686245e705947439270e2c69b README.rst --- a/README.rst +++ b/README.rst @@ -1,5 +1,5 @@ -.. image:: https://drone.io/bitbucket.org/hpk42/pytest/status.png - :target: https://drone.io/bitbucket.org/hpk42/pytest/latest +.. image:: https://drone.io/bitbucket.org/pytest-dev/pytest/status.png + :target: https://drone.io/bitbucket.org/pytest-dev/pytest/latest .. image:: https://pypip.in/v/pytest/badge.png :target: https://pypi.python.org/pypi/pytest @@ -7,9 +7,9 @@ Changelog: http://pytest.org/latest/changelog.html -Issues: https://bitbucket.org/hpk42/pytest/issues?status=open +Issues: https://bitbucket.org/pytest-dev/pytest/issues?status=open -CI: https://drone.io/bitbucket.org/hpk42/pytest +CI: https://drone.io/bitbucket.org/pytest-dev/pytest The ``pytest`` testing tool makes it easy to write small tests, yet scales to support complex functional testing. It provides @@ -44,11 +44,11 @@ and report bugs at: - http://bitbucket.org/hpk42/pytest/issues/ + http://bitbucket.org/pytest-dev/pytest/issues/ and checkout or fork repo at: - http://bitbucket.org/hpk42/pytest/ + http://bitbucket.org/pytest-dev/pytest/ Copyright Holger Krekel and others, 2004-2014 diff -r 1abf285d64ae7fcfaee1fcd01c045357a8a7411b -r de09a4c6bc60c27686245e705947439270e2c69b _pytest/python.py --- a/_pytest/python.py +++ b/_pytest/python.py @@ -1047,7 +1047,7 @@ if ExpectedException is AssertionError: # we want to catch a AssertionError # replace our subclass with the builtin one - # see https://bitbucket.org/hpk42/pytest/issue/176/pytestraises + # see https://bitbucket.org/pytest-dev/pytest/issue/176/pytestraises from _pytest.assertion.util import BuiltinAssertionError \ as ExpectedException msg = ("exceptions must be old-style classes or" diff -r 1abf285d64ae7fcfaee1fcd01c045357a8a7411b -r de09a4c6bc60c27686245e705947439270e2c69b doc/en/Makefile --- a/doc/en/Makefile +++ b/doc/en/Makefile @@ -42,7 +42,7 @@ clean: -rm -rf $(BUILDDIR)/* -SITETARGET=dev +SITETARGET=latest install: html # for access talk to someone with login rights to diff -r 1abf285d64ae7fcfaee1fcd01c045357a8a7411b -r de09a4c6bc60c27686245e705947439270e2c69b doc/en/adopt.txt --- a/doc/en/adopt.txt +++ b/doc/en/adopt.txt @@ -9,7 +9,7 @@ In 2015 we are trying this for the first time. In February and March we will gather volunteers on both sides, in April we will do the work, and in May we will evaluate how it went. This effort is being coordinated by Brianna Laugher. If you have any questions or comments, you can raise them on the `issue tracker`_ or the `pytest-dev mailing list`_. -.. _`issue tracker`: https://bitbucket.org/hpk42/pytest/issue/676/adopt-pytest-month-2015 +.. _`issue tracker`: https://bitbucket.org/pytest-dev/pytest/issue/676/adopt-pytest-month-2015 .. _`pytest-dev mailing list`: https://mail.python.org/mailman/listinfo/pytest-dev .. _``: diff -r 1abf285d64ae7fcfaee1fcd01c045357a8a7411b -r de09a4c6bc60c27686245e705947439270e2c69b doc/en/announce/release-2.6.0.txt --- a/doc/en/announce/release-2.6.0.txt +++ b/doc/en/announce/release-2.6.0.txt @@ -21,7 +21,7 @@ Note also that 2.6.0 departs with the "zero reported bugs" policy because it has been too hard to keep up with it, unfortunately. Instead we are for now rather bound to work on "upvoted" issues in -the https://bitbucket.org/hpk42/pytest/issues?status=new&status=open&sort=-votes +the https://bitbucket.org/pytest-dev/pytest/issues?status=new&status=open&sort=-votes issue tracker. See docs at: diff -r 1abf285d64ae7fcfaee1fcd01c045357a8a7411b -r de09a4c6bc60c27686245e705947439270e2c69b doc/en/contact.txt --- a/doc/en/contact.txt +++ b/doc/en/contact.txt @@ -29,7 +29,7 @@ - `merlinux.eu`_ offers pytest and tox-related professional teaching and consulting. -.. _`pytest issue tracker`: http://bitbucket.org/hpk42/pytest/issues/ +.. _`pytest issue tracker`: http://bitbucket.org/pytest-dev/pytest/issues/ .. _`old issue tracker`: http://bitbucket.org/hpk42/py-trunk/issues/ .. _`merlinux.eu`: http://merlinux.eu diff -r 1abf285d64ae7fcfaee1fcd01c045357a8a7411b -r de09a4c6bc60c27686245e705947439270e2c69b doc/en/nose.txt --- a/doc/en/nose.txt +++ b/doc/en/nose.txt @@ -39,13 +39,13 @@ it doesn't seem useful to duplicate the unittest-API like nose does. If you however rather think pytest should support the unittest-spelling on plain classes please post `to this issue - <https://bitbucket.org/hpk42/pytest/issue/377/>`_. + <https://bitbucket.org/pytest-dev/pytest/issue/377/>`_. - nose imports test modules with the same import path (e.g. ``tests.test_mod``) but different file system paths (e.g. ``tests/test_mode.py`` and ``other/tests/test_mode.py``) by extending sys.path/import semantics. pytest does not do that - but there is discussion in `issue268 <https://bitbucket.org/hpk42/pytest/issue/268>`_ for adding some support. Note that + but there is discussion in `issue268 <https://bitbucket.org/pytest-dev/pytest/issue/268>`_ for adding some support. Note that `nose2 choose to avoid this sys.path/import hackery <https://nose2.readthedocs.org/en/latest/differences.html#test-discovery-and-loading>`_. - nose-style doctests are not collected and executed correctly, diff -r 1abf285d64ae7fcfaee1fcd01c045357a8a7411b -r de09a4c6bc60c27686245e705947439270e2c69b doc/en/plugins.txt --- a/doc/en/plugins.txt +++ b/doc/en/plugins.txt @@ -9,7 +9,7 @@ * `external plugins`_: modules discovered through `setuptools entry points`_ * `conftest.py plugins`_: modules auto-discovered in test directories -.. _`pytest/plugin`: http://bitbucket.org/hpk42/pytest/src/tip/pytest/plugin/ +.. _`pytest/plugin`: http://bitbucket.org/pytest-dev/pytest/src/tip/pytest/plugin/ .. _`conftest.py plugins`: .. _`conftest.py`: .. _`localplugin`: @@ -120,43 +120,9 @@ .. _`pytest- pypi.python.org search`: http://pypi.python.org/pypi?%3Aaction=search&term=pytest-&submit=search -External plugin development ---------------------------- - -Pytest community cares about pytest users, in particular, it's crucial for the community -to keep all pieces of the pytest ecosystem well supported. External plugins are important for -pytest users, as they implement many useful, and sometimes critical features which the pytest core does -not implement. - -To simplify the plugin development and/or support, it was decided to create teams(companies) on popular code hosting -services (at the moment it's github and bitbucket): - -* `<https://github.com/pytest-dev>`_: - probably the most popular hosting for pytest plugins - the name ``pytest-dev`` is choosen because ``pytest`` was already taken by - some unknown person, who's not active on the github or just doesn't check the email used to register - that organization. -* `<https://bitbucket.org/pytest-dev>`_: - pytest is hosted on the bitbucket, also a lot of pytest plugins are hosted there. - -More code hosting services can be added in the future. - -Community encourages pytest plugin developers to move their plugins under those organizations (eg transfer ownership), -paying with a better support, faster feedback, better discoverability, etc. - -Generic workflow of the ownership transfer looks like: - -* If not a member already, developer asks for a membership in the `pytest plugin developers community` organizations listed above, sending an email to `<pytest-...@python.org>`_. - -* Developer transfers the ownership of his plugin repository to the organization listed above. - -* Existing organization members will make sure proper write permissions are set up for developer who transfered the ownership to the organization. - - Writing a plugin by looking at examples --------------------------------------- -.. _`Distribute`: http://pypi.python.org/pypi/distribute .. _`setuptools`: http://pypi.python.org/pypi/setuptools If you want to write a plugin, there are many real-life examples @@ -169,6 +135,10 @@ All of these plugins implement the documented `well specified hooks`_ to extend and add functionality. +You can also :doc:`contribute your plugin to pytest-dev<submitplugin>` +once it has some happy users other than yourself. + + .. _`setuptools entry points`: Making your plugin installable by others @@ -177,10 +147,10 @@ If you want to make your plugin externally available, you may define a so-called entry point for your distribution so that ``pytest`` finds your plugin module. Entry points are -a feature that is provided by `setuptools`_ or `Distribute`_. -pytest looks up the ``pytest11`` entrypoint to discover its +a feature that is provided by `setuptools`_. pytest looks up +the ``pytest11`` entrypoint to discover its plugins and you can thus make your plugin available by defining -it in your setuptools/distribute-based setup-invocation: +it in your setuptools-invocation: .. sourcecode:: python @@ -296,7 +266,7 @@ You can find the source code for the following plugins -in the `pytest repository <http://bitbucket.org/hpk42/pytest/>`_. +in the `pytest repository <http://bitbucket.org/pytest-dev/pytest/>`_. .. autosummary:: @@ -435,7 +405,7 @@ For an example, see `newhooks.py`_ from :ref:`xdist`. -.. _`newhooks.py`: https://bitbucket.org/hpk42/pytest-xdist/src/52082f70e7dd04b00361091b8af906c60fd6700f/xdist/newhooks.py?at=default +.. _`newhooks.py`: https://bitbucket.org/pytest-dev/pytest-xdist/src/52082f70e7dd04b00361091b8af906c60fd6700f/xdist/newhooks.py?at=default Using hooks from 3rd party plugins diff -r 1abf285d64ae7fcfaee1fcd01c045357a8a7411b -r de09a4c6bc60c27686245e705947439270e2c69b doc/en/plugins_index/index.txt --- a/doc/en/plugins_index/index.txt +++ b/doc/en/plugins_index/index.txt @@ -30,7 +30,7 @@ `pytest-bugzilla <http://pypi.python.org/pypi/pytest-bugzilla>`_ .. image:: http://pytest-plugs.herokuapp.com/status/pytest-bugzilla-latest?py=py27&pytest=2.6.4.dev1 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-bugzilla-latest?py=py34&pytest=2.6.4.dev1 .. image:: github.png py.test bugzilla integration plugin :target: http://pytest-plugs.herokuapp.com/output/pytest-bugzilla-latest?py=py27&pytest=2.6.4.dev1 :target: http://pytest-plugs.herokuapp.com/output/pytest-bugzilla-latest?py=py34&pytest=2.6.4.dev1 :target: http://github.com/nibrahim/pytest_bugzilla `pytest-cache <http://pypi.python.org/pypi/pytest-cache>`_ .. image:: http://pytest-plugs.herokuapp.com/status/pytest-cache-latest?py=py27&pytest=2.6.4.dev1 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-cache-latest?py=py34&pytest=2.6.4.dev1 .. image:: bitbucket.png pytest plugin with mechanisms for caching across test runs - :target: http://pytest-plugs.herokuapp.com/output/pytest-cache-latest?py=py27&pytest=2.6.4.dev1 :target: http://pytest-plugs.herokuapp.com/output/pytest-cache-latest?py=py34&pytest=2.6.4.dev1 :target: http://bitbucket.org/hpk42/pytest-cache/ + :target: http://pytest-plugs.herokuapp.com/output/pytest-cache-latest?py=py27&pytest=2.6.4.dev1 :target: http://pytest-plugs.herokuapp.com/output/pytest-cache-latest?py=py34&pytest=2.6.4.dev1 :target: http://bitbucket.org/pytest-dev/pytest-cache/ `pytest-capturelog <http://pypi.python.org/pypi/pytest-capturelog>`_ .. image:: http://pytest-plugs.herokuapp.com/status/pytest-capturelog-latest?py=py27&pytest=2.6.4.dev1 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-capturelog-latest?py=py34&pytest=2.6.4.dev1 .. image:: bitbucket.png py.test plugin to capture log messages :target: http://pytest-plugs.herokuapp.com/output/pytest-capturelog-latest?py=py27&pytest=2.6.4.dev1 :target: http://pytest-plugs.herokuapp.com/output/pytest-capturelog-latest?py=py34&pytest=2.6.4.dev1 :target: http://bitbucket.org/memedough/pytest-capturelog/overview `pytest-codecheckers <http://pypi.python.org/pypi/pytest-codecheckers>`_ .. image:: http://pytest-plugs.herokuapp.com/status/pytest-codecheckers-latest?py=py27&pytest=2.6.4.dev1 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-codecheckers-latest?py=py34&pytest=2.6.4.dev1 .. image:: bitbucket.png pytest plugin to add source code sanity checks (pep8 and friends) @@ -64,7 +64,7 @@ `pytest-eradicate <http://pypi.python.org/pypi/pytest-eradicate>`_ .. image:: http://pytest-plugs.herokuapp.com/status/pytest-eradicate-latest?py=py27&pytest=2.6.4.dev1 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-eradicate-latest?py=py34&pytest=2.6.4.dev1 .. image:: github.png pytest plugin to check for commented out code :target: http://pytest-plugs.herokuapp.com/output/pytest-eradicate-latest?py=py27&pytest=2.6.4.dev1 :target: http://pytest-plugs.herokuapp.com/output/pytest-eradicate-latest?py=py34&pytest=2.6.4.dev1 :target: https://github.com/spil-johan/pytest-eradicate `pytest-figleaf <http://pypi.python.org/pypi/pytest-figleaf>`_ .. image:: http://pytest-plugs.herokuapp.com/status/pytest-figleaf-latest?py=py27&pytest=2.6.4.dev1 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-figleaf-latest?py=py34&pytest=2.6.4.dev1 .. image:: bitbucket.png py.test figleaf coverage plugin - :target: http://pytest-plugs.herokuapp.com/output/pytest-figleaf-latest?py=py27&pytest=2.6.4.dev1 :target: http://pytest-plugs.herokuapp.com/output/pytest-figleaf-latest?py=py34&pytest=2.6.4.dev1 :target: http://bitbucket.org/hpk42/pytest-figleaf + :target: http://pytest-plugs.herokuapp.com/output/pytest-figleaf-latest?py=py27&pytest=2.6.4.dev1 :target: http://pytest-plugs.herokuapp.com/output/pytest-figleaf-latest?py=py34&pytest=2.6.4.dev1 :target: http://bitbucket.org/pytest-dev/pytest-figleaf `pytest-fixture-tools <http://pypi.python.org/pypi/pytest-fixture-tools>`_ .. image:: http://pytest-plugs.herokuapp.com/status/pytest-fixture-tools-latest?py=py27&pytest=2.6.4.dev1 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-fixture-tools-latest?py=py34&pytest=2.6.4.dev1 ? Plugin for pytest which provides tools for fixtures :target: http://pytest-plugs.herokuapp.com/output/pytest-fixture-tools-latest?py=py27&pytest=2.6.4.dev1 :target: http://pytest-plugs.herokuapp.com/output/pytest-fixture-tools-latest?py=py34&pytest=2.6.4.dev1 `pytest-flakes <http://pypi.python.org/pypi/pytest-flakes>`_ .. image:: http://pytest-plugs.herokuapp.com/status/pytest-flakes-latest?py=py27&pytest=2.6.4.dev1 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-flakes-latest?py=py34&pytest=2.6.4.dev1 .. image:: github.png pytest plugin to check source code with pyflakes @@ -114,7 +114,7 @@ `pytest-paste-config <http://pypi.python.org/pypi/pytest-paste-config>`_ .. image:: http://pytest-plugs.herokuapp.com/status/pytest-paste-config-latest?py=py27&pytest=2.6.4.dev1 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-paste-config-latest?py=py34&pytest=2.6.4.dev1 ? Allow setting the path to a paste config file :target: http://pytest-plugs.herokuapp.com/output/pytest-paste-config-latest?py=py27&pytest=2.6.4.dev1 :target: http://pytest-plugs.herokuapp.com/output/pytest-paste-config-latest?py=py34&pytest=2.6.4.dev1 `pytest-pep8 <http://pypi.python.org/pypi/pytest-pep8>`_ .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pep8-latest?py=py27&pytest=2.6.4.dev1 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pep8-latest?py=py34&pytest=2.6.4.dev1 .. image:: bitbucket.png pytest plugin to check PEP8 requirements - :target: http://pytest-plugs.herokuapp.com/output/pytest-pep8-latest?py=py27&pytest=2.6.4.dev1 :target: http://pytest-plugs.herokuapp.com/output/pytest-pep8-latest?py=py34&pytest=2.6.4.dev1 :target: http://bitbucket.org/hpk42/pytest-pep8/ + :target: http://pytest-plugs.herokuapp.com/output/pytest-pep8-latest?py=py27&pytest=2.6.4.dev1 :target: http://pytest-plugs.herokuapp.com/output/pytest-pep8-latest?py=py34&pytest=2.6.4.dev1 :target: http://bitbucket.org/pytest-dev/pytest-pep8/ `pytest-pipeline <http://pypi.python.org/pypi/pytest-pipeline>`_ .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pipeline-latest?py=py27&pytest=2.6.4.dev1 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-pipeline-latest?py=py34&pytest=2.6.4.dev1 .. image:: github.png Pytest plugin for functional testing of data analysis pipelines :target: http://pytest-plugs.herokuapp.com/output/pytest-pipeline-latest?py=py27&pytest=2.6.4.dev1 :target: http://pytest-plugs.herokuapp.com/output/pytest-pipeline-latest?py=py34&pytest=2.6.4.dev1 :target: https://github.com/bow/pytest_pipeline `pytest-poo <http://pypi.python.org/pypi/pytest-poo>`_ .. image:: http://pytest-plugs.herokuapp.com/status/pytest-poo-latest?py=py27&pytest=2.6.4.dev1 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-poo-latest?py=py34&pytest=2.6.4.dev1 .. image:: github.png Visualize your crappy tests @@ -158,9 +158,9 @@ `pytest-twisted <http://pypi.python.org/pypi/pytest-twisted>`_ .. image:: http://pytest-plugs.herokuapp.com/status/pytest-twisted-latest?py=py27&pytest=2.6.4.dev1 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-twisted-latest?py=py34&pytest=2.6.4.dev1 .. image:: github.png A twisted plugin for py.test. :target: http://pytest-plugs.herokuapp.com/output/pytest-twisted-latest?py=py27&pytest=2.6.4.dev1 :target: http://pytest-plugs.herokuapp.com/output/pytest-twisted-latest?py=py34&pytest=2.6.4.dev1 :target: https://github.com/schmir/pytest-twisted `pytest-xdist <http://pypi.python.org/pypi/pytest-xdist>`_ .. image:: http://pytest-plugs.herokuapp.com/status/pytest-xdist-latest?py=py27&pytest=2.6.4.dev1 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-xdist-latest?py=py34&pytest=2.6.4.dev1 .. image:: bitbucket.png py.test xdist plugin for distributed testing and loop-on-failing modes - :target: http://pytest-plugs.herokuapp.com/output/pytest-xdist-latest?py=py27&pytest=2.6.4.dev1 :target: http://pytest-plugs.herokuapp.com/output/pytest-xdist-latest?py=py34&pytest=2.6.4.dev1 :target: http://bitbucket.org/hpk42/pytest-xdist + :target: http://pytest-plugs.herokuapp.com/output/pytest-xdist-latest?py=py27&pytest=2.6.4.dev1 :target: http://pytest-plugs.herokuapp.com/output/pytest-xdist-latest?py=py34&pytest=2.6.4.dev1 :target: http://bitbucket.org/pytest-dev/pytest-xdist `pytest-xprocess <http://pypi.python.org/pypi/pytest-xprocess>`_ .. image:: http://pytest-plugs.herokuapp.com/status/pytest-xprocess-latest?py=py27&pytest=2.6.4.dev1 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-xprocess-latest?py=py34&pytest=2.6.4.dev1 .. image:: bitbucket.png pytest plugin to manage external processes across test runs - :target: http://pytest-plugs.herokuapp.com/output/pytest-xprocess-latest?py=py27&pytest=2.6.4.dev1 :target: http://pytest-plugs.herokuapp.com/output/pytest-xprocess-latest?py=py34&pytest=2.6.4.dev1 :target: http://bitbucket.org/hpk42/pytest-xprocess/ + :target: http://pytest-plugs.herokuapp.com/output/pytest-xprocess-latest?py=py27&pytest=2.6.4.dev1 :target: http://pytest-plugs.herokuapp.com/output/pytest-xprocess-latest?py=py34&pytest=2.6.4.dev1 :target: http://bitbucket.org/pytest-dev/pytest-xprocess/ `pytest-yamlwsgi <http://pypi.python.org/pypi/pytest-yamlwsgi>`_ .. image:: http://pytest-plugs.herokuapp.com/status/pytest-yamlwsgi-latest?py=py27&pytest=2.6.4.dev1 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-yamlwsgi-latest?py=py34&pytest=2.6.4.dev1 ? Run tests against wsgi apps defined in yaml :target: http://pytest-plugs.herokuapp.com/output/pytest-yamlwsgi-latest?py=py27&pytest=2.6.4.dev1 :target: http://pytest-plugs.herokuapp.com/output/pytest-yamlwsgi-latest?py=py34&pytest=2.6.4.dev1 `pytest-zap <http://pypi.python.org/pypi/pytest-zap>`_ .. image:: http://pytest-plugs.herokuapp.com/status/pytest-zap-latest?py=py27&pytest=2.6.4.dev1 .. image:: http://pytest-plugs.herokuapp.com/status/pytest-zap-latest?py=py34&pytest=2.6.4.dev1 .. image:: github.png OWASP ZAP plugin for py.test. diff -r 1abf285d64ae7fcfaee1fcd01c045357a8a7411b -r de09a4c6bc60c27686245e705947439270e2c69b doc/en/status.txt --- a/doc/en/status.txt +++ b/doc/en/status.txt @@ -1,5 +1,5 @@ pytest development status ================================ -https://drone.io/bitbucket.org/hpk42/pytest +https://drone.io/bitbucket.org/pytest-dev/pytest diff -r 1abf285d64ae7fcfaee1fcd01c045357a8a7411b -r de09a4c6bc60c27686245e705947439270e2c69b doc/en/talks.txt --- a/doc/en/talks.txt +++ b/doc/en/talks.txt @@ -11,8 +11,8 @@ Talks and blog postings --------------------------------------------- -.. _`tutorial1 repository`: http://bitbucket.org/hpk42/pytest-tutorial1/ -.. _`pycon 2010 tutorial PDF`: http://bitbucket.org/hpk42/pytest-tutorial1/raw/tip/pytest-basic.pdf +.. _`tutorial1 repository`: http://bitbucket.org/pytest-dev/pytest-tutorial1/ +.. _`pycon 2010 tutorial PDF`: http://bitbucket.org/pytest-dev/pytest-tutorial1/raw/tip/pytest-basic.pdf - `Introduction to pytest, Andreas Pelme, EuroPython 2014 <https://www.youtube.com/watch?v=LdVJj65ikRY>`_. diff -r 1abf285d64ae7fcfaee1fcd01c045357a8a7411b -r de09a4c6bc60c27686245e705947439270e2c69b doc/en/xdist.txt --- a/doc/en/xdist.txt +++ b/doc/en/xdist.txt @@ -192,6 +192,6 @@ where the configuration file was found. .. _`pytest-xdist`: http://pypi.python.org/pypi/pytest-xdist -.. _`pytest-xdist repository`: http://bitbucket.org/hpk42/pytest-xdist +.. _`pytest-xdist repository`: http://bitbucket.org/pytest-dev/pytest-xdist .. _`pytest`: http://pytest.org diff -r 1abf285d64ae7fcfaee1fcd01c045357a8a7411b -r de09a4c6bc60c27686245e705947439270e2c69b extra/get_issues.py --- a/extra/get_issues.py +++ b/extra/get_issues.py @@ -2,7 +2,7 @@ import py import textwrap -issues_url = "http://bitbucket.org/api/1.0/repositories/hpk42/pytest/issues"; +issues_url = "http://bitbucket.org/api/1.0/repositories/pytest-dev/pytest/issues"; import requests @@ -53,7 +53,7 @@ kind = metadata["kind"] status = issue["status"] id = issue["local_id"] - link = "https://bitbucket.org/hpk42/pytest/issue/%s/"; % id + link = "https://bitbucket.org/pytest-dev/pytest/issue/%s/"; % id print("----") print(status, kind, link) print(title) diff -r 1abf285d64ae7fcfaee1fcd01c045357a8a7411b -r de09a4c6bc60c27686245e705947439270e2c69b testing/test_capture.py --- a/testing/test_capture.py +++ b/testing/test_capture.py @@ -1040,7 +1040,7 @@ def test_pickling_and_unpickling_enocded_file(): - # See https://bitbucket.org/hpk42/pytest/pull-request/194 + # See https://bitbucket.org/pytest-dev/pytest/pull-request/194 # pickle.loads() raises infinite recursion if # EncodedFile.__getattr__ is not implemented properly ef = capture.EncodedFile(None, None) Repository URL: https://bitbucket.org/pytest-dev/pytest/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email. _______________________________________________ pytest-commit mailing list pytest-commit@python.org https://mail.python.org/mailman/listinfo/pytest-commit
