1 new commit in pytest: https://bitbucket.org/pytest-dev/pytest/commits/26ea4acb80e0/ Changeset: 26ea4acb80e0 Branch: docs_community User: hpk42 Date: 2015-02-27 11:27:40+00:00 Summary: change links to go to the new pytest-dev bitbucket team's repo location Affected #: 14 files
diff -r dc417e256fbe08ec5e838e48c6b6caba06ebe331 -r 26ea4acb80e0879bdbac7994c3f9cedb13a84821 CONTRIBUTING.rst --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -53,7 +53,7 @@ Report bugs ----------- -Report bugs for pytest 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: @@ -71,7 +71,7 @@ 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. @@ -86,7 +86,7 @@ -------- 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. @@ -97,7 +97,7 @@ 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. @@ -121,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. @@ -129,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. @@ -196,7 +196,7 @@ source: YOUR_BITBUCKET_USERNAME/pytest branch: your-branch-name - target: hpk42/pytest + target: pytest-dev/pytest branch: default .. _contribution-using-git: diff -r dc417e256fbe08ec5e838e48c6b6caba06ebe331 -r 26ea4acb80e0879bdbac7994c3f9cedb13a84821 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 dc417e256fbe08ec5e838e48c6b6caba06ebe331 -r 26ea4acb80e0879bdbac7994c3f9cedb13a84821 _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 dc417e256fbe08ec5e838e48c6b6caba06ebe331 -r 26ea4acb80e0879bdbac7994c3f9cedb13a84821 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 dc417e256fbe08ec5e838e48c6b6caba06ebe331 -r 26ea4acb80e0879bdbac7994c3f9cedb13a84821 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 dc417e256fbe08ec5e838e48c6b6caba06ebe331 -r 26ea4acb80e0879bdbac7994c3f9cedb13a84821 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 dc417e256fbe08ec5e838e48c6b6caba06ebe331 -r 26ea4acb80e0879bdbac7994c3f9cedb13a84821 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 dc417e256fbe08ec5e838e48c6b6caba06ebe331 -r 26ea4acb80e0879bdbac7994c3f9cedb13a84821 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`: @@ -266,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:: @@ -405,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 dc417e256fbe08ec5e838e48c6b6caba06ebe331 -r 26ea4acb80e0879bdbac7994c3f9cedb13a84821 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 dc417e256fbe08ec5e838e48c6b6caba06ebe331 -r 26ea4acb80e0879bdbac7994c3f9cedb13a84821 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 dc417e256fbe08ec5e838e48c6b6caba06ebe331 -r 26ea4acb80e0879bdbac7994c3f9cedb13a84821 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 dc417e256fbe08ec5e838e48c6b6caba06ebe331 -r 26ea4acb80e0879bdbac7994c3f9cedb13a84821 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 dc417e256fbe08ec5e838e48c6b6caba06ebe331 -r 26ea4acb80e0879bdbac7994c3f9cedb13a84821 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 dc417e256fbe08ec5e838e48c6b6caba06ebe331 -r 26ea4acb80e0879bdbac7994c3f9cedb13a84821 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
