rabbitmq-amqp-python-client 2.0.0a1__tar.gz → 2.0.0a2__tar.gz

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/.github/workflows/publish-pypi.yaml

@@ -25,14 +25,13 @@ jobs:
       id-token: write
     steps:
       - uses: actions/checkout@v3
-      - name: build with poetry
-        env:
-          REPO: ${{ inputs.pypi_repository_url }}
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: build
         run: |
-          curl -sSL https://install.python-poetry.org | python3 -
-          export PATH="/home/runner/.local/bin:$PATH"
-          poetry config repositories.test-pypi $REPO
-          poetry build
+          python3 -m pip install build
+          python3 -m build
       # retrieve your distributions here
       - name: Publish package distributions to PyPI
         uses: pypa/gh-action-pypi-publish@release/v1

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/Makefile

@@ -21,7 +21,7 @@ lint:
 	$(PYTHON) -m ruff format --check .
 
 typecheck:
-	$(PYTHON) -m mypy src
+	$(PYTHON) -m mypy rabbitmq_amqp_python_client
 	MYPYPATH=. $(PYTHON) -m mypy docs/examples
 
 build:

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: rabbitmq-amqp-python-client
-Version: 2.0.0a1
+Version: 2.0.0a2
 Summary: A from-scratch AMQP 1.0 client for RabbitMQ, built directly against the wire protocol.
 Author: RabbitMQ Team
 License: Apache-2.0
@@ -42,7 +42,7 @@ pip install -e ".[dev]"
 ## Quick start
 
 ```python
-from src import Connection, ConnectionParameters, Context, Message
+from rabbitmq_amqp_python_client import Connection, ConnectionParameters, Context, Message
 
 connection = Connection(ConnectionParameters())  # localhost:5672, guest/guest
 try:
@@ -84,7 +84,7 @@ PYTHONPATH=. .venv/bin/python docs/examples/basic_connection.py
 make install          # create .venv and install the package with its dev extras
 make format           # ruff format, then ruff check --fix
 make lint             # ruff check and ruff format --check
-make typecheck        # mypy src, in strict mode
+make typecheck        # mypy rabbitmq_amqp_python_client, in strict mode
 make test-unit        # the unit suite; no broker needed
 make test-integration # the integration suite; needs a broker on localhost:5672
 make test             # both suites
@@ -98,7 +98,7 @@ MYPYPATH=. .venv/bin/python -m mypy docs/examples/*.py
 
 ## Project layout
 
-`src/` holds the client: `wire/` is the protocol
+`rabbitmq_amqp_python_client/` holds the client: `wire/` is the protocol
 layer (type codec, frames, performatives, messages, SASL) and knows nothing
 above itself, and `connection.py`, `session.py`, `link.py`, `management.py`,
 `publisher.py`, `consumer.py` and `reconnection.py` build the public API on top

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/README.md

@@ -26,7 +26,7 @@ pip install -e ".[dev]"
 ## Quick start
 
 ```python
-from src import Connection, ConnectionParameters, Context, Message
+from rabbitmq_amqp_python_client import Connection, ConnectionParameters, Context, Message
 
 connection = Connection(ConnectionParameters())  # localhost:5672, guest/guest
 try:
@@ -68,7 +68,7 @@ PYTHONPATH=. .venv/bin/python docs/examples/basic_connection.py
 make install          # create .venv and install the package with its dev extras
 make format           # ruff format, then ruff check --fix
 make lint             # ruff check and ruff format --check
-make typecheck        # mypy src, in strict mode
+make typecheck        # mypy rabbitmq_amqp_python_client, in strict mode
 make test-unit        # the unit suite; no broker needed
 make test-integration # the integration suite; needs a broker on localhost:5672
 make test             # both suites
@@ -82,7 +82,7 @@ MYPYPATH=. .venv/bin/python -m mypy docs/examples/*.py
 
 ## Project layout
 
-`src/` holds the client: `wire/` is the protocol
+`rabbitmq_amqp_python_client/` holds the client: `wire/` is the protocol
 layer (type codec, frames, performatives, messages, SASL) and knows nothing
 above itself, and `connection.py`, `session.py`, `link.py`, `management.py`,
 `publisher.py`, `consumer.py` and `reconnection.py` build the public API on top

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/docs/examples/auto_reconnection.py

@@ -27,7 +27,7 @@ import socket
 import time
 import uuid
 
-from src import (
+from rabbitmq_amqp_python_client import (
     AMQPError,
     Connection,
     ConnectionParameters,

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/docs/examples/basic_connection.py

@@ -4,12 +4,12 @@ Run against a local broker::
 
     PYTHONPATH=. .venv/bin/python docs/examples/basic_connection.py
 
-Constructing a :class:`~src.Connection` dials the TCP
+Constructing a :class:`~rabbitmq_amqp_python_client.Connection` dials the TCP
 socket, exchanges the protocol header, runs SASL and the ``open`` handshake, and
 starts the frame reader — all before ``__init__`` returns. There is no separate
 ``connect()`` step: a constructed connection is already ``OPEN`` and usable.
 
-The default :class:`~src.ConnectionParameters` describe
+The default :class:`~rabbitmq_amqp_python_client.ConnectionParameters` describe
 exactly what a stock broker offers — ``localhost:5672``, ``guest``/``guest``, the
 ``/`` virtual host — so the no-argument form below is the shortest connection
 this client can make. What the broker sent back in its own ``open`` is readable
@@ -24,7 +24,7 @@ from __future__ import annotations
 
 import logging
 
-from src import Connection, ConnectionParameters
+from rabbitmq_amqp_python_client import Connection, ConnectionParameters
 
 logging.basicConfig(level=logging.INFO, format="%(asctime)s %(levelname)-7s %(name)s: %(message)s")
 logger = logging.getLogger("example")

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/docs/examples/console_application.py

@@ -11,11 +11,11 @@ both confirmed and consumed, so this doubles as a scriptable smoke test::
     python3 docs/examples/console_application.py --help
 
 This program adds nothing to the client's public surface: it is built entirely
-out of :class:`~src.Connection`,
-:class:`~src.Management`,
-:class:`~src.Publisher`,
-:class:`~src.Consumer` and
-:class:`~src.RecoveryConfiguration`. It owns exactly one
+out of :class:`~rabbitmq_amqp_python_client.Connection`,
+:class:`~rabbitmq_amqp_python_client.Management`,
+:class:`~rabbitmq_amqp_python_client.Publisher`,
+:class:`~rabbitmq_amqp_python_client.Consumer` and
+:class:`~rabbitmq_amqp_python_client.RecoveryConfiguration`. It owns exactly one
 connection: it is a correctness/smoke-test tool, not a load generator.
 
 Exit codes:
@@ -49,7 +49,7 @@ _SOURCE_ROOT = Path(__file__).resolve().parents[2]
 if _SOURCE_ROOT.is_dir() and str(_SOURCE_ROOT) not in sys.path:
     sys.path.insert(0, str(_SOURCE_ROOT))
 
-from src import (  # noqa: E402 - after the sys.path bootstrap above
+from rabbitmq_amqp_python_client import (  # noqa: E402 - after the sys.path bootstrap above
     AMQPError,
     Connection,
     ConnectionParameters,
@@ -64,7 +64,7 @@ from src import (  # noqa: E402 - after the sys.path bootstrap above
 )
 
 if TYPE_CHECKING:
-    from src.connection import ConnectionState
+    from rabbitmq_amqp_python_client.connection import ConnectionState
 
 # --- exit codes (§7) ----------------------------------------------------
 
@@ -475,7 +475,7 @@ def map_queue_type(options: Options, specification: QueueSpecification) -> Queue
         specification: The builder from ``management.queue(name)``.
 
     Returns:
-        The same builder, ready to :meth:`~src.QueueSpecification.declare`.
+        The same builder, ready to :meth:`~rabbitmq_amqp_python_client.QueueSpecification.declare`.
 
     Raises:
         OptionsError: If ``queue_type`` is not one of :data:`QUEUE_TYPES`.

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/docs/examples/consumer_example.py

@@ -8,7 +8,7 @@ A consumer is a receiver link plus a ``message_handler``. The link is granted
 ``initial_credits`` when it attaches, and the client re-grants one credit every
 time a delivery is settled, so at most that many messages are ever outstanding.
 The handler runs on the client's delivery thread and is handed a
-:class:`~src.Context` alongside the message; calling
+:class:`~rabbitmq_amqp_python_client.Context` alongside the message; calling
 ``context.accept()`` settles the delivery as ``accepted``, which is what tells
 the broker it may drop it. ``discard()`` and ``requeue()`` are the other two
 choices, and doing nothing leaves the delivery unsettled — visible as
@@ -28,7 +28,7 @@ import logging
 import queue
 import uuid
 
-from src import (
+from rabbitmq_amqp_python_client import (
     Connection,
     ConnectionParameters,
     Context,

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/docs/examples/direct_reply_to_example.py

@@ -12,7 +12,7 @@ dynamically generates a private, per-attach pseudo-queue address
 reply puts that address in an outgoing request's ``properties.reply_to``;
 whoever answers just needs to publish to it — no dedicated, exclusive reply
 queue to declare and clean up per requester. Like a presettled consumer, its
-``Context`` methods all raise :class:`~src.ConsumerError`: the broker considers
+``Context`` methods all raise :class:`~rabbitmq_amqp_python_client.ConsumerError`: the broker considers
 every delivery on this link already settled the instant it sends it.
 
 This script plays both roles, on two separate connections:
@@ -22,7 +22,7 @@ This script plays both roles, on two separate connections:
 * the **responder** (``responder_connection``) declares an ordinary request
   queue, consumes it with a normal ``ExplicitSettle`` consumer, and replies to
   whatever address arrived in the request's ``reply_to`` — an ordinary
-  anonymous :class:`~src.Publisher` (step_020_publishers.md §3.3) also sends
+  anonymous :class:`~rabbitmq_amqp_python_client.Publisher` (step_020_publishers.md §3.3) also sends
   the request itself, targeting the request queue.
 
 Because the pseudo-queue is scoped to the exact connection and session that
@@ -43,7 +43,7 @@ import socket
 import time
 import uuid
 
-from src import (
+from rabbitmq_amqp_python_client import (
     Connection,
     ConnectionParameters,
     ConnectionState,
@@ -55,7 +55,7 @@ from src import (
     RecoveryConfiguration,
     queue_address,
 )
-from src.wire import Properties
+from rabbitmq_amqp_python_client.wire import Properties
 
 #: How long the example waits for a reply it expects.
 TIMEOUT_SECONDS = 15.0

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/docs/examples/management_example.py

@@ -14,7 +14,7 @@ request message out and one response message back, correlated by
 The script walks the whole surface once:
 
 1. ``queue(name).declare()`` declares a classic queue and returns a
-   :class:`~src.QueueInfo` parsed from the broker's
+   :class:`~rabbitmq_amqp_python_client.QueueInfo` parsed from the broker's
    answer, so the queue's real settings are readable straight away;
 2. ``exchange(name).type(ExchangeType.TOPIC).declare()`` declares a topic
    exchange;
@@ -26,7 +26,7 @@ The script walks the whole surface once:
 
 Declaring is idempotent as long as the arguments match: re-declaring the same
 queue is a successful no-op, while re-declaring it with different arguments is a
-:class:`~src.ManagementError`.
+:class:`~rabbitmq_amqp_python_client.ManagementError`.
 """
 
 from __future__ import annotations
@@ -34,7 +34,7 @@ from __future__ import annotations
 import logging
 import uuid
 
-from src import (
+from rabbitmq_amqp_python_client import (
     Connection,
     ConnectionParameters,
     ExchangeType,

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/docs/examples/performance_test.py

@@ -13,10 +13,10 @@ summary::
     python3 docs/examples/performance_test.py --help
 
 This program adds nothing to the client's public surface: it is built entirely
-out of :class:`~src.Connection`,
-:class:`~src.Management`,
-:class:`~src.Publisher` and
-:class:`~src.Consumer`. It owns exactly one connection,
+out of :class:`~rabbitmq_amqp_python_client.Connection`,
+:class:`~rabbitmq_amqp_python_client.Management`,
+:class:`~rabbitmq_amqp_python_client.Publisher` and
+:class:`~rabbitmq_amqp_python_client.Consumer`. It owns exactly one connection,
 one publisher and one consumer: it measures what one such pair can sustain, not
 a cluster-wide ceiling (§10).
 
@@ -57,7 +57,7 @@ _SOURCE_ROOT = Path(__file__).resolve().parents[2]
 if _SOURCE_ROOT.is_dir() and str(_SOURCE_ROOT) not in sys.path:
     sys.path.insert(0, str(_SOURCE_ROOT))
 
-from src import (  # noqa: E402 - after the sys.path bootstrap above
+from rabbitmq_amqp_python_client import (  # noqa: E402 - after the sys.path bootstrap above
     AMQPError,
     ApplicationProperties,
     Connection,
@@ -931,7 +931,7 @@ def map_queue_type(options: Options, specification: QueueSpecification) -> Queue
         specification: The builder from ``management.queue(name)``.
 
     Returns:
-        The same builder, ready to :meth:`~src.QueueSpecification.declare`.
+        The same builder, ready to :meth:`~rabbitmq_amqp_python_client.QueueSpecification.declare`.
 
     Raises:
         OptionsError: If ``queue_type`` is not one of :data:`QUEUE_TYPES`.

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/docs/examples/presettled_consumer_example.py

@@ -13,9 +13,9 @@ consumer dies holding one.
 
 Two consequences show up directly in the API and are asserted below:
 
-* the handler must not touch its :class:`~src.Context`.
+* the handler must not touch its :class:`~rabbitmq_amqp_python_client.Context`.
   There is nothing left to settle, so ``accept()``/``discard()``/``requeue()``
-  each raise :class:`~src.ConsumerError`. A presettled
+  each raise :class:`~rabbitmq_amqp_python_client.ConsumerError`. A presettled
   handler only reads the message. ``context.is_presettled`` says which mode it
   is running in, for a handler shared between both;
 * ``consumer.unsettled_message_count`` stays at ``0`` for the consumer's whole
@@ -38,7 +38,7 @@ import socket
 import time
 import uuid
 
-from src import (
+from rabbitmq_amqp_python_client import (
     Connection,
     ConnectionParameters,
     ConnectionState,

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/docs/examples/publisher_example.py

@@ -18,7 +18,7 @@ how that address is chosen. All three forms appear here:
    two different addresses, one link.
 
 Every ``publish`` blocks until the broker settles the message and returns a
-:class:`~src.PublishResult` pairing the message with its
+:class:`~rabbitmq_amqp_python_client.PublishResult` pairing the message with its
 outcome. ``RELEASED`` is worth noticing: it is not an error and not a rejection,
 it is the broker saying the message routed nowhere — which is exactly what
 happens when an exchange has no binding matching the routing key.
@@ -32,7 +32,7 @@ from __future__ import annotations
 import logging
 import uuid
 
-from src import (
+from rabbitmq_amqp_python_client import (
     Connection,
     ConnectionParameters,
     ExchangeType,

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/docs/examples/quorum_single_active_consumer.py

@@ -26,7 +26,7 @@ import logging
 import queue
 import uuid
 
-from src import (
+from rabbitmq_amqp_python_client import (
     Connection,
     ConnectionParameters,
     Consumer,

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/docs/examples/rejection_reason_example.py

@@ -19,7 +19,7 @@ A rejection is **not** an error here: ``publish`` returns normally with
 publish attempt itself succeeded — it is the routing that did not. Anything the
 broker said about why is parsed out of the ``rejected`` disposition's
 ``error.info`` map into
-:class:`~src.RejectionDetails`:
+:class:`~rabbitmq_amqp_python_client.RejectionDetails`:
 
 * ``reason`` — the broker's explanation, e.g. ``maximum queue length exceeded``;
 * ``rejected_by_queue`` — which queue rejected it, which matters when the
@@ -36,7 +36,7 @@ from __future__ import annotations
 import logging
 import uuid
 
-from src import (
+from rabbitmq_amqp_python_client import (
     Connection,
     ConnectionParameters,
     Message,

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/docs/examples/stream_filtering.py

@@ -32,7 +32,7 @@ import logging
 import queue
 import uuid
 
-from src import (
+from rabbitmq_amqp_python_client import (
     ApplicationProperties,
     Connection,
     ConnectionParameters,
@@ -44,7 +44,7 @@ from src import (
     StreamOffsetSpecification,
     Symbol,
 )
-from src.constants import STREAM_FILTER_VALUE_ANNOTATION
+from rabbitmq_amqp_python_client.constants import STREAM_FILTER_VALUE_ANNOTATION
 
 #: How long the example waits for the deliveries a filter should let through.
 TIMEOUT_SECONDS = 15.0

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/docs/examples/tls_connection.py

@@ -24,7 +24,7 @@ import logging
 import pathlib
 import ssl
 
-from src import Connection, ConnectionParameters
+from rabbitmq_amqp_python_client import Connection, ConnectionParameters
 
 logging.basicConfig(level=logging.INFO, format="%(asctime)s %(levelname)-7s %(name)s: %(message)s")
 logger = logging.getLogger("example")

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "rabbitmq-amqp-python-client"
-version = "2.0.0-alpha.1"
+version = "2.0.0-alpha.2"
 description = "A from-scratch AMQP 1.0 client for RabbitMQ, built directly against the wire protocol."
 readme = "README.md"
 requires-python = ">=3.10"

{rabbitmq_amqp_python_client-2.0.0a1/src → rabbitmq_amqp_python_client-2.0.0a2/rabbitmq_amqp_python_client}/__init__.py

@@ -4,7 +4,7 @@ Everything an application needs is exported here: the connection and its
 parameters, the management API and its specifications, the publisher and
 consumer builders, the reconnection policy, and the message types needed to
 compose a message and read an outcome. The lower layers remain importable from
-their own modules — :mod:`~src.wire` in particular holds
+their own modules — :mod:`~rabbitmq_amqp_python_client.wire` in particular holds
 the rest of the protocol types. See ``docs/examples`` for usage.
 """
 

{rabbitmq_amqp_python_client-2.0.0a1/src → rabbitmq_amqp_python_client-2.0.0a2/rabbitmq_amqp_python_client}/logging_utils.py

@@ -1,8 +1,8 @@
 """Logging helpers.
 
 The client logs through the standard :mod:`logging` package under the
-``src`` logger namespace. Applications configure
-levels/handlers the normal way (``logging.getLogger("src")``);
+``rabbitmq_amqp_python_client`` logger namespace. Applications configure
+levels/handlers the normal way (``logging.getLogger("rabbitmq_amqp_python_client")``);
 this module only centralizes the child-logger naming convention.
 """
 
@@ -10,7 +10,7 @@ from __future__ import annotations
 
 import logging
 
-ROOT_LOGGER_NAME = "src"
+ROOT_LOGGER_NAME = "rabbitmq_amqp_python_client"
 
 
 def get_logger(component: str) -> logging.Logger:
@@ -21,6 +21,6 @@ def get_logger(component: str) -> logging.Logger:
             or ``"consumer"``.
 
     Returns:
-        A logger named ``src.<component>``.
+        A logger named ``rabbitmq_amqp_python_client.<component>``.
     """
     return logging.getLogger(f"{ROOT_LOGGER_NAME}.{component}")

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/tests/integration/test_client_interpolation_integration.py

@@ -28,9 +28,9 @@ import uuid
 import pika
 import pytest
 
-from src import Connection, ConnectionParameters, OutcomeState
-from src.management import QueueInfo
-from src.wire import ApplicationProperties, Message, Properties
+from rabbitmq_amqp_python_client import Connection, ConnectionParameters, OutcomeState
+from rabbitmq_amqp_python_client.management import QueueInfo
+from rabbitmq_amqp_python_client.wire import ApplicationProperties, Message, Properties
 
 pytestmark = pytest.mark.integration
 

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/tests/integration/test_client_stream_interpolation_integration.py

@@ -45,10 +45,10 @@ from rstream import Consumer as RstreamConsumer
 from rstream import Producer as RstreamProducer
 from rstream import Properties as RstreamProperties
 
-from src import Connection, ConnectionParameters, OutcomeState
-from src.consumer import StreamOffsetSpecification
-from src.management import QueueInfo
-from src.wire import ApplicationProperties, Message, Properties
+from rabbitmq_amqp_python_client import Connection, ConnectionParameters, OutcomeState
+from rabbitmq_amqp_python_client.consumer import StreamOffsetSpecification
+from rabbitmq_amqp_python_client.management import QueueInfo
+from rabbitmq_amqp_python_client.wire import ApplicationProperties, Message, Properties
 
 pytestmark = pytest.mark.integration
 

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/tests/integration/test_connection_integration.py

@@ -8,7 +8,7 @@ import time
 
 import pytest
 
-from src import (
+from rabbitmq_amqp_python_client import (
     AuthenticationError,
     Connection,
     ConnectionParameters,

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/tests/integration/test_consumer_integration.py

@@ -22,7 +22,7 @@ import uuid
 
 import pytest
 
-from src import (
+from rabbitmq_amqp_python_client import (
     Connection,
     ConnectionParameters,
     ConsumerError,
@@ -30,8 +30,8 @@ from src import (
     OutcomeState,
     StreamOffsetSpecification,
 )
-from src.constants import STREAM_FILTER_VALUE_ANNOTATION
-from src.wire import (
+from rabbitmq_amqp_python_client.constants import STREAM_FILTER_VALUE_ANNOTATION
+from rabbitmq_amqp_python_client.wire import (
     ApplicationProperties,
     Message,
     MessageAnnotations,

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/tests/integration/test_management_integration.py

@@ -13,7 +13,7 @@ import uuid
 
 import pytest
 
-from src import (
+from rabbitmq_amqp_python_client import (
     ClassicQueueMode,
     ClassicQueueVersion,
     Connection,
@@ -28,15 +28,15 @@ from src import (
     ReceiverLink,
     SenderLink,
 )
-from src.constants import EXCHANGE_ADDRESS_WITH_KEY_TEMPLATE
-from src.management import (
+from rabbitmq_amqp_python_client.constants import EXCHANGE_ADDRESS_WITH_KEY_TEMPLATE
+from rabbitmq_amqp_python_client.management import (
     STATUS_BAD_REQUEST,
     STATUS_CONFLICT,
     STATUS_NOT_FOUND,
     encode_path_segment,
     queue_path,
 )
-from src.wire import Accepted, Message, Source, Target
+from rabbitmq_amqp_python_client.wire import Accepted, Message, Source, Target
 
 pytestmark = pytest.mark.integration
 

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/tests/integration/test_performance_test_integration.py

@@ -21,8 +21,8 @@ from pathlib import Path
 import performance_test as app
 import pytest
 
-from src import Connection, ConnectionParameters
-from src.wire import Message
+from rabbitmq_amqp_python_client import Connection, ConnectionParameters
+from rabbitmq_amqp_python_client.wire import Message
 
 pytestmark = pytest.mark.integration
 

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/tests/integration/test_publisher_integration.py

@@ -5,7 +5,7 @@ message, ``released`` for an exchange with no bindings, and ``rejected`` with
 structured details for a quorum queue whose ``x-overflow`` is
 ``reject-publish`` (step_070 §6). Consumers are a later step, so the one test
 that has to prove a message really landed attaches a raw
-:class:`~src.ReceiverLink` itself.
+:class:`~rabbitmq_amqp_python_client.ReceiverLink` itself.
 """
 
 from __future__ import annotations
@@ -16,7 +16,7 @@ import uuid
 
 import pytest
 
-from src import (
+from rabbitmq_amqp_python_client import (
     Connection,
     ConnectionParameters,
     ExchangeType,
@@ -27,7 +27,7 @@ from src import (
     exchange_address,
     queue_address,
 )
-from src.wire import Accepted, Message, Properties, Source
+from rabbitmq_amqp_python_client.wire import Accepted, Message, Properties, Source
 
 pytestmark = pytest.mark.integration
 

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/tests/integration/test_reconnection_integration.py

@@ -27,7 +27,7 @@ import uuid
 
 import pytest
 
-from src import (
+from rabbitmq_amqp_python_client import (
     AMQPError,
     Connection,
     ConnectionParameters,
@@ -36,7 +36,7 @@ from src import (
     ManagementError,
     RecoveryConfiguration,
 )
-from src.wire import Message
+from rabbitmq_amqp_python_client.wire import Message
 
 pytestmark = pytest.mark.integration
 

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/tests/integration/test_session_link_integration.py

@@ -6,7 +6,7 @@ import uuid
 
 import pytest
 
-from src import (
+from rabbitmq_amqp_python_client import (
     Connection,
     ConnectionParameters,
     ConsumerError,
@@ -15,7 +15,7 @@ from src import (
     ReceiverLink,
     SenderLink,
 )
-from src.wire import (
+from rabbitmq_amqp_python_client.wire import (
     Accepted,
     ApplicationProperties,
     Message,
@@ -242,7 +242,7 @@ class TestSettlement:
         second.detach()
 
     def test_a_rejected_message_is_not_redelivered(self, session, queue_address):
-        from src.wire import Error
+        from rabbitmq_amqp_python_client.wire import Error
 
         sender = _sender(session, queue_address)
         sender.send_transfer(b"tag-1", Message("reject me"), settled=True)

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/tests/integration/test_tls_integration.py

@@ -10,7 +10,7 @@ import ssl
 
 import pytest
 
-from src import AuthenticationError, Connection, ConnectionParameters, ConnectionState
+from rabbitmq_amqp_python_client import AuthenticationError, Connection, ConnectionParameters, ConnectionState
 
 from .conftest import BROKER_HOST, BROKER_TLS_PORT, CA_CERTIFICATE, CLIENT_CERTIFICATE, CLIENT_KEY
 

{rabbitmq_amqp_python_client-2.0.0a1 → rabbitmq_amqp_python_client-2.0.0a2}/tests/unit/conftest.py

@@ -7,9 +7,9 @@ import socket
 
 import pytest
 
-from src import connection as connection_module
-from src.connection import Connection, ConnectionParameters
-from src.reconnection import RecoveryConfiguration
+from rabbitmq_amqp_python_client import connection as connection_module
+from rabbitmq_amqp_python_client.connection import Connection, ConnectionParameters
+from rabbitmq_amqp_python_client.reconnection import RecoveryConfiguration
 from tests.unit.fake_broker import BrokerFarm, FakeBroker