Switch to src-based project layout

Author: CoolCat467

src/trio_asyncio.egg-info/PKG-INFO

@@ -0,0 +1,133 @@
+Metadata-Version: 2.4
+Name: trio_asyncio
+Version: 0.15.0+dev
+Summary: A re-implementation of the asyncio mainloop on top of Trio
+Author-email: Matthias Urlichs <matthias@urlichs.de>
+License-Expression: MIT OR Apache-2.0
+Project-URL: Homepage, https://github.com/python-trio/trio-asyncio
+Project-URL: Documentation, http://trio-asyncio.readthedocs.io
+Project-URL: Changelog, https://trio-asyncio.readthedocs.io/en/latest/history.html
+Keywords: async,io,trio,asyncio,trio-asyncio
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Operating System :: MacOS :: MacOS X
+Classifier: Operating System :: POSIX :: BSD
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Programming Language :: Python :: Implementation :: CPython
+Classifier: Programming Language :: Python :: Implementation :: PyPy
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: System :: Networking
+Classifier: Framework :: Trio
+Classifier: Framework :: AsyncIO
+Requires-Python: >=3.9
+Description-Content-Type: text/x-rst
+License-File: LICENSE
+License-File: LICENSE.APACHE2
+License-File: LICENSE.MIT
+Requires-Dist: trio>=0.22.0
+Requires-Dist: outcome
+Requires-Dist: sniffio>=1.3.0
+Requires-Dist: exceptiongroup>=1.0.0; python_version < "3.11"
+Requires-Dist: greenlet
+Provides-Extra: tests
+Requires-Dist: pytest>=5.4; extra == "tests"
+Requires-Dist: pytest-trio>=0.6; extra == "tests"
+Dynamic: license-file
+
+.. image:: https://img.shields.io/pypi/v/trio-asyncio.svg
+   :target: https://pypi.org/project/trio-asyncio
+   :alt: Latest PyPI version
+
+.. image:: https://img.shields.io/badge/chat-join%20now-blue.svg
+   :target: https://gitter.im/python-trio/general
+   :alt: Join chatroom
+
+.. image:: https://img.shields.io/badge/docs-read%20now-blue.svg
+   :target: https://trio-asyncio.readthedocs.io/en/latest/?badge=latest
+   :alt: Documentation status
+
+.. image:: https://github.com/python-trio/trio-asyncio/actions/workflows/ci.yml/badge.svg
+   :target: https://github.com/python-trio/trio-asyncio/actions/workflows/ci.yml
+   :alt: Automated test status
+
+.. image:: https://codecov.io/gh/python-trio/trio-asyncio/branch/master/graph/badge.svg
+   :target: https://codecov.io/gh/python-trio/trio-asyncio
+   :alt: Test coverage
+
+
+==============
+ trio-asyncio
+==============
+
+**trio-asyncio** is a re-implementation of the ``asyncio`` mainloop on top of
+Trio.
+
+trio-asyncio requires at least Python 3.9. It is tested on recent versions of
+3.9 through 3.13.
+
++++++++++++
+ Rationale
++++++++++++
+
+Trio has native concepts of tasks and task cancellation. Asyncio is based
+on callbacks and chaining Futures, albeit with nicer syntax, making
+handling failures and timeouts fundamentally less reliable, especially in
+larger programs. Thus, you *really* want to base your async project on Trio.
+
+On the other hand, there are quite a few asyncio-enhanced libraries. You
+*really* don't want to re-invent any wheels in your project.
+
+Thus, being able to use asyncio libraries from Trio is useful.
+trio-asyncio enables you to do that and more.
+
+--------------------------------------
+ Transparent vs. explicit translation
+--------------------------------------
+
+``trio_asyncio`` does not try to magically allow calling ``await
+trio_code()`` from asyncio or vice versa. There are multiple reasons for
+this; the executive summary is that cross-domain calls can't be made to
+work correctly, and any such call is likely to result in an irrecoverable
+error. You need to keep your code's ``asyncio`` and ``trio`` domains
+rigidly separate.
+
+Fortunately, this is not difficult.
+
++++++++
+ Usage
++++++++
+
+Trio-Asyncio's documentation is too large for a README.
+
+For further information, `see the manual on readthedocs <http://trio-asyncio.readthedocs.io/en/latest/>`_.
+
+++++++++++++++
+ Contributing
+++++++++++++++
+
+Like Trio, trio-asyncio is licensed under both the MIT and Apache licenses.
+Submitting a patch or pull request implies your acceptance of these licenses.
+
+Testing is done with ``pytest``. Test coverage is pretty thorough; please
+keep it that way when adding new code.
+
+See the `Trio contributor guide
+<https://trio.readthedocs.io/en/stable/contributing.html>`__ for much
+more detail on how to get involved.
+
+Contributors are requested to follow our `code of conduct
+<https://trio.readthedocs.io/en/stable/code-of-conduct.html>`__ in all
+project spaces.
+
+++++++++
+ Author
+++++++++
+
+Matthias Urlichs <matthias@urlichs.de> originally wrote trio-asyncio.
+It is now maintained by the `Trio project <https://github.com/python-trio>`_.

src/trio_asyncio.egg-info/SOURCES.txt

@@ -0,0 +1,58 @@
+.coveragerc
+CODE_OF_CONDUCT.md
+CONTRIBUTING.md
+LICENSE
+LICENSE.APACHE2
+LICENSE.MIT
+MANIFEST.in
+README.rst
+pyproject.toml
+docs/Makefile
+docs/make.bat
+docs/source/conf.py
+docs/source/history.rst
+docs/source/index.rst
+docs/source/principles.rst
+docs/source/usage.rst
+docs/source/_static/.gitkeep
+src/trio_asyncio/__init__.py
+src/trio_asyncio/_adapter.py
+src/trio_asyncio/_async.py
+src/trio_asyncio/_base.py
+src/trio_asyncio/_child.py
+src/trio_asyncio/_deprecate.py
+src/trio_asyncio/_handles.py
+src/trio_asyncio/_loop.py
+src/trio_asyncio/_sync.py
+src/trio_asyncio/_util.py
+src/trio_asyncio/_version.py
+src/trio_asyncio.egg-info/PKG-INFO
+src/trio_asyncio.egg-info/SOURCES.txt
+src/trio_asyncio.egg-info/dependency_links.txt
+src/trio_asyncio.egg-info/requires.txt
+src/trio_asyncio.egg-info/top_level.txt
+tests/__init__.py
+tests/conftest.py
+tests/module_with_deprecations.py
+tests/test_aio_subprocess.py
+tests/test_concurrent.py
+tests/test_deprecate.py
+tests/test_misc.py
+tests/test_sync.py
+tests/test_trio_asyncio.py
+tests/utils.py
+tests/aiotest/__init__.py
+tests/aiotest/conftest.py
+tests/aiotest/test_add_reader.py
+tests/aiotest/test_callback.py
+tests/aiotest/test_coroutine.py
+tests/aiotest/test_network.py
+tests/aiotest/test_thread.py
+tests/aiotest/test_timer.py
+tests/interop/__init__.py
+tests/interop/test_adapter.py
+tests/interop/test_calls.py
+tests/python/__init__.py
+tests/scripts/echo.py
+tests/scripts/echo2.py
+tests/scripts/echo3.py

src/trio_asyncio.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

src/trio_asyncio.egg-info/requires.txt

@@ -0,0 +1,11 @@
+trio>=0.22.0
+outcome
+sniffio>=1.3.0
+greenlet
+
+[:python_version < "3.11"]
+exceptiongroup>=1.0.0
+
+[tests]
+pytest>=5.4
+pytest-trio>=0.6

src/trio_asyncio.egg-info/top_level.txt

@@ -0,0 +1 @@
+trio_asyncio