update URLs for python-trio org

python-trio · Aug 3, 2023 · 89f2749 · 89f2749
1 parent 6209783
commit 89f2749
Show file tree

Hide file tree

Showing 8 changed files with 18 additions and 18 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -10,7 +10,7 @@
   `closed` attribute would be `None`, and `send_message()` would be silently
   ignored (wsproto < 0.2.0) or leak a `LocalProtocolError` (wsproto >= 0.2.0)
   rather than raise `ConnectionClosed`
-  ([#158](https://github.com/HyperionGray/trio-websocket/issues/158))
+  ([#158](https://github.com/python-trio/trio-websocket/issues/158))
 
 ## trio-websocket 0.10.1 (2023-03-18)
 ### Fixed
@@ -20,7 +20,7 @@
   defined to cover connections "closed or in the process of closing".
   Notably, this fixes `send_message()` leaking a wsproto `LocalProtocolError`
   with wsproto >= 1.2.0.
-  ([#175](https://github.com/HyperionGray/trio-websocket/issues/175))
+  ([#175](https://github.com/python-trio/trio-websocket/issues/175))
 
 Released as a minor version increment, since code calling `send_message()`
 is expected to handle `ConnectionClosed` anyway.
@@ -34,12 +34,12 @@ is expected to handle `ConnectionClosed` anyway.
 ## trio-websocket 0.9.2 (2021-02-05)
 ### Fixed
 - the server will now correctly close the TCP stream on a CloseConnection event
-  ([#115](https://github.com/HyperionGray/trio-websocket/issues/115))
+  ([#115](https://github.com/python-trio/trio-websocket/issues/115))
 
 ## trio-websocket 0.9.1 (2020-12-06)
 ### Fixed
 - fix client open_websocket_url() when the URL path component is empty
-  ([#148](https://github.com/HyperionGray/trio-websocket/issues/148))
+  ([#148](https://github.com/python-trio/trio-websocket/issues/148))
 
 ## trio-websocket 0.9.0 (2020-11-25)
 
@@ -58,7 +58,7 @@ is expected to handle `ConnectionClosed` anyway.
 ## trio-websocket 0.8.1 (2020-09-22)
 ### Fixed
 - reader task no longer raises unhandled exception on ClosedResourceError
-  ([#134](https://github.com/HyperionGray/trio-websocket/issues/134))
+  ([#134](https://github.com/python-trio/trio-websocket/issues/134))
 - minor issues in example code, documentation, and type-hinting
 
 ## ...
diff --git a/README.md b/README.md
@@ -15,7 +15,7 @@ available here](https://trio-websocket.readthedocs.io).
 
 [![PyPI](https://img.shields.io/pypi/v/trio-websocket.svg?style=flat-square)](https://pypi.org/project/trio-websocket/)
 ![Python Versions](https://img.shields.io/pypi/pyversions/trio-websocket.svg?style=flat-square)
-[![Build Status](https://img.shields.io/github/actions/workflow/status/HyperionGray/trio-websocket/ci.yml)](https://github.com/HyperionGray/trio-websocket/actions/workflows/ci.yml)
+[![Build Status](https://img.shields.io/github/actions/workflow/status/python-trio/trio-websocket/ci.yml)](https://github.com/python-trio/trio-websocket/actions/workflows/ci.yml)
 [![Read the Docs](https://img.shields.io/readthedocs/trio-websocket.svg)](https://trio-websocket.readthedocs.io)
 
 ## Alternatives

diff --git a/docs/contributing.rst b/docs/contributing.rst
@@ -11,7 +11,7 @@ install additional dependencies that are used for testing and documentation. The
 following sequence of commands will clone the repository, create a virtual
 environment, and install the developer dependencies::
 
-    $ git clone git@github.com:HyperionGray/trio-websocket.git
+    $ git clone git@github.com:python-trio/trio-websocket.git
     $ cd trio-websocket
     $ python3 -m venv venv
     $ source venv/bin/activate
@@ -182,7 +182,7 @@ To release a new version of this library, we follow this process:
 2. Commit ``_version.py``.
 3. Create a tag, e.g. ``git tag 1.2.0``.
 4. Push the commit and the tag, e.g. ``git push && git push origin 1.2.0``.
-5. Wait for `Github CI <https://github.com/HyperionGray/trio-websocket/actions/>`__ to
+5. Wait for `Github CI <https://github.com/python-trio/trio-websocket/actions/>`__ to
    finish building and ensure that the build is successful.
 6. Wait for `Read The Docs <https://trio-websocket.readthedocs.io/en/latest/>`__
    to finish building and ensure that the build is successful.

diff --git a/docs/getting_started.rst b/docs/getting_started.rst
@@ -13,7 +13,7 @@ PyPI.
 
     $ pip3 install trio-websocket
 
-You can also install from source. Visit `the project's GitHub page <https://github.com/hyperiongray/trio-websocket/>`__, where you can clone the repository or download a Zip file.
+You can also install from source. Visit `the project's GitHub page <https://github.com/python-trio/trio-websocket/>`__, where you can clone the repository or download a Zip file.
 Change into the project directory and run the following command.
 
 ::

diff --git a/docs/index.rst b/docs/index.rst
@@ -8,19 +8,19 @@ correctness, and ergonomics. It is based on `wsproto
 <https://sans-io.readthedocs.io/>`__ state machine that implements most aspects
 of the WebSocket protocol, including framing, codecs, and events. The
 respository is hosted `on GitHub
-<https://github.com/hyperiongray/trio-websocket/>`__. This library passes `the
+<https://github.com/python-trio/trio-websocket/>`__. This library passes `the
 Autobahn Test Suite <https://github.com/crossbario/autobahn-testsuite>`__.
 
 .. image:: https://img.shields.io/pypi/v/trio-websocket.svg?style=flat-square
     :alt: PyPI
     :target: https://pypi.org/project/trio-websocket/
 .. image:: https://img.shields.io/pypi/pyversions/trio-websocket.svg?style=flat-square
     :alt: Python Versions
-.. image:: https://img.shields.io/github/license/HyperionGray/trio-websocket.svg?style=flat-square
+.. image:: https://img.shields.io/github/license/python-trio/trio-websocket.svg?style=flat-square
     :alt: MIT License
-.. image:: https://img.shields.io/github/actions/workflow/status/HyperionGray/trio-websocket/ci.yml
+.. image:: https://img.shields.io/github/actions/workflow/status/python-trio/trio-websocket/ci.yml
     :alt: Build Status
-    :target: https://github.com/HyperionGray/trio-websocket/actions/workflows/ci.yml
+    :target: https://github.com/python-trio/trio-websocket/actions/workflows/ci.yml
 
 .. toctree::
    :maxdepth: 2

diff --git a/docs/recipes.rst b/docs/recipes.rst
@@ -57,5 +57,5 @@ connection is dropped unexpectedly or takes too long to respond, then
 wish to implement additional logic to automatically reconnect.
 
 A heartbeat feature can be enabled in the `example client
-<https://github.com/HyperionGray/trio-websocket/blob/master/examples/client.py>`__.
+<https://github.com/python-trio/trio-websocket/blob/master/examples/client.py>`__.
 with the ``--heartbeat`` flag.
diff --git a/docs/servers.rst b/docs/servers.rst
@@ -34,7 +34,7 @@ revisiting the :ref:`server-example`.
 .. note::
 
     A more complete example is included `in the repository
-    <https://github.com/HyperionGray/trio-websocket/blob/master/examples/server.py>`__.
+    <https://github.com/python-trio/trio-websocket/blob/master/examples/server.py>`__.
 
 As explained in the tutorial, a WebSocket server needs a handler function and a
 host/port to bind to. The handler function receives a

diff --git a/setup.py b/setup.py
@@ -19,7 +19,7 @@
     description='WebSocket library for Trio',
     long_description=long_description,
     long_description_content_type='text/markdown',
-    url='https://github.com/HyperionGray/trio-websocket',
+    url='https://github.com/python-trio/trio-websocket',
     author='Mark E. Haase',
     author_email='mehaase@gmail.com',
     classifiers=[
@@ -45,7 +45,7 @@
         'wsproto>=0.14',
     ],
     project_urls={
-        'Bug Reports': 'https://github.com/HyperionGray/trio-websocket/issues',
-        'Source': 'https://github.com/HyperionGray/trio-websocket',
+        'Bug Reports': 'https://github.com/python-trio/trio-websocket/issues',
+        'Source': 'https://github.com/python-trio/trio-websocket',
     },
 )