sg-python-api 0.1.1__tar.gz → 0.1.2__tar.gz

{sg_python_api-0.1.1 → sg_python_api-0.1.2}/COMPATIBILITY.md

@@ -24,7 +24,7 @@ the *readiness check*.
 ## Supported scope
 
 The package provides the `shotgun_api3` import name and targets the documented synchronous API of
-Autodesk's Python client `3.10.2`, including its method signatures, return shapes, errors, filters,
+Autodesk's Python client `3.10.3`, including its method signatures, return shapes, errors, filters,
 paging, schema, file, activity, navigation, and scheduling operations. It also provides the
 `shotgun_api3.lib.mockgun` and `shotgun_api3.lib.sgtimezone` modules and native async extensions.
 
@@ -112,7 +112,7 @@ operation repeats the check; the client never pages with an invalid size.
 | ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Download setup errors          | Setup RPC faults keep their specific types. Setup or transfer HTTP failures and invalid download URLs raise `ShotgunFileDownloadError` with a generic message and no underlying exception details. Configuration and security failures keep their existing types. |
 | Multi-target thumbnail sharing | The client waits for source readiness before sharing and does not upload the source again.                                                                                                                                                                        |
-| Legacy form uploads            | A successful response from the legacy form-upload route is unsupported. Hosted direct and multipart routes are supported.                                                                                                                                         |
+| Legacy form uploads            | Servers requiring legacy form uploads are unsupported. The client raises `ShotgunError` before any upload request; capability reads may occur. Hosted direct and multipart routes are supported.                                                                  |
 | Datetime-shaped strings        | Invalid values remain unchanged strings. On platforms without pre-1970 time conversion, valid pre-epoch values use the process standard offset without historical daylight-saving accuracy.                                                                       |
 | Request diagnostics            | Structured observers omit credentials and bodies. Application `httpx2` INFO logging can include signed URLs; set that logger to WARNING.                                                                                                                          |
 | User agent                     | The default includes an `sg-python-api` marker. `add_user_agent()` preserves it, `reset_user_agent()` restores the default, and assigning `sg.config.user_agents` replaces every entry.                                                                           |

{sg_python_api-0.1.1 → sg_python_api-0.1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: sg-python-api
-Version: 0.1.1
+Version: 0.1.2
 Summary: Python client for Autodesk Flow Production Tracking
 Project-URL: Documentation, https://github.com/dactylo/sg-python-api/tree/main/docs
 Project-URL: Homepage, https://github.com/dactylo/sg-python-api
@@ -44,9 +44,9 @@ This documentation uses SG for Flow Production Tracking, formerly named Shotgun
   for application tests.
 
 sg-python-api is an independent implementation of the documented API of Autodesk's Python client
-`3.10.2`. Some behavior differs on purpose, so validate your application's workflows against a test
-site before replacing its production client. The [migration guide](https://github.com/dactylo/sg-python-api/blob/v0.1.1/docs/migration-guide.md) walks
-through the switch, and the [compatibility reference](https://github.com/dactylo/sg-python-api/blob/v0.1.1/COMPATIBILITY.md) lists the differences.
+`3.10.3`. Some behavior differs on purpose, so validate your application's workflows against a test
+site before replacing its production client. The [migration guide](https://github.com/dactylo/sg-python-api/blob/v0.1.2/docs/migration-guide.md) walks
+through the switch, and the [compatibility reference](https://github.com/dactylo/sg-python-api/blob/v0.1.2/COMPATIBILITY.md) lists the differences.
 
 ## Installation
 
@@ -55,7 +55,7 @@ requests to a remote site require HTTPS.
 
 `sg-python-api` and Autodesk's `shotgun-api3` both install the `shotgun_api3` package, so install
 exactly one of them in a Python environment. If the official client is already installed, follow
-the [migration steps](https://github.com/dactylo/sg-python-api/blob/v0.1.1/docs/migration-guide.md#install-the-replacement) to replace it.
+the [migration steps](https://github.com/dactylo/sg-python-api/blob/v0.1.2/docs/migration-guide.md#install-the-replacement) to replace it.
 
 From a checkout, install into the Python environment that runs your application:
 
@@ -130,23 +130,23 @@ operation fails. Without the `async` extra, importing `AsyncShotgun` raises `Imp
 
 Share an `AsyncShotgun` only among tasks on one event loop, and cancel its work by cancelling the
 task. A cancelled write may already have reached the server, so check its outcome before repeating
-it. The [async reference](https://github.com/dactylo/sg-python-api/blob/v0.1.1/COMPATIBILITY.md#async-extension-surfaces) covers shutdown and
+it. The [async reference](https://github.com/dactylo/sg-python-api/blob/v0.1.2/COMPATIBILITY.md#async-extension-surfaces) covers shutdown and
 cancellation in detail.
 
 ## Documentation
 
 | If you want to...                                     | Read                                                                               |
 | ----------------------------------------------------- | ---------------------------------------------------------------------------------- |
-| Replace Autodesk's client in an existing application  | [Migration guide](https://github.com/dactylo/sg-python-api/blob/v0.1.1/docs/migration-guide.md)                                         |
-| Check what behaves differently from Autodesk's client | [Compatibility](https://github.com/dactylo/sg-python-api/blob/v0.1.1/COMPATIBILITY.md)                                                  |
-| Tune pooling and page prefetch, or observe requests   | [Configuration extensions](https://github.com/dactylo/sg-python-api/blob/v0.1.1/COMPATIBILITY.md#configuration-and-observer-extensions) |
-| Confirm which client loads and run a smoke test       | [Testing an installation](https://github.com/dactylo/sg-python-api/blob/v0.1.1/docs/testing.md)                                         |
-| Compare measured latency and transfer memory          | [Benchmarks](https://github.com/dactylo/sg-python-api/blob/v0.1.1/docs/benchmarks.md)                                                   |
-| See changes by version                                | [Changelog](https://github.com/dactylo/sg-python-api/blob/v0.1.1/CHANGELOG.md)                                                          |
+| Replace Autodesk's client in an existing application  | [Migration guide](https://github.com/dactylo/sg-python-api/blob/v0.1.2/docs/migration-guide.md)                                         |
+| Check what behaves differently from Autodesk's client | [Compatibility](https://github.com/dactylo/sg-python-api/blob/v0.1.2/COMPATIBILITY.md)                                                  |
+| Tune pooling and page prefetch, or observe requests   | [Configuration extensions](https://github.com/dactylo/sg-python-api/blob/v0.1.2/COMPATIBILITY.md#configuration-and-observer-extensions) |
+| Confirm which client loads and run a smoke test       | [Testing an installation](https://github.com/dactylo/sg-python-api/blob/v0.1.2/docs/testing.md)                                         |
+| Compare measured latency and transfer memory          | [Benchmarks](https://github.com/dactylo/sg-python-api/blob/v0.1.2/docs/benchmarks.md)                                                   |
+| See changes by version                                | [Changelog](https://github.com/dactylo/sg-python-api/blob/v0.1.2/CHANGELOG.md)                                                          |
 
 ## Development
 
-See the [development guide](https://github.com/dactylo/sg-python-api/blob/v0.1.1/docs/development.md) for the required tools, CI, and dependency locks.
+See the [development guide](https://github.com/dactylo/sg-python-api/blob/v0.1.2/docs/development.md) for the required tools, CI, and dependency locks.
 With those tools installed, run:
 
 ```sh
@@ -159,6 +159,6 @@ make check
 
 ## License
 
-sg-python-api is available under the [MIT License](https://github.com/dactylo/sg-python-api/blob/v0.1.1/LICENSE). It is an independent project and is
+sg-python-api is available under the [MIT License](https://github.com/dactylo/sg-python-api/blob/v0.1.2/LICENSE). It is an independent project and is
 not affiliated with or endorsed by Autodesk. Flow Production Tracking is a product of Autodesk,
 Inc.

{sg_python_api-0.1.1 → sg_python_api-0.1.2}/README.md

@@ -20,7 +20,7 @@ This documentation uses SG for Flow Production Tracking, formerly named Shotgun
   for application tests.
 
 sg-python-api is an independent implementation of the documented API of Autodesk's Python client
-`3.10.2`. Some behavior differs on purpose, so validate your application's workflows against a test
+`3.10.3`. Some behavior differs on purpose, so validate your application's workflows against a test
 site before replacing its production client. The [migration guide](docs/migration-guide.md) walks
 through the switch, and the [compatibility reference](COMPATIBILITY.md) lists the differences.
 

{sg_python_api-0.1.1 → sg_python_api-0.1.2}/docs/development.md

@@ -119,7 +119,7 @@ invalidate the evidence. Both scripts need network access and a
 
 Run `scripts/run_conformance.sh` with the same `PATH` and with `SG_TEST_SITE`, `SG_TEST_SCRIPT`,
 `SG_TEST_KEY`, `SG_TEST_HUMAN_LOGIN`, and `SG_TEST_HUMAN_PASSWORD` set. It clones Autodesk's suite
-at `v3.10.2`, runs it against the validated wheel, and appends a tally to
+at `v3.10.3`, runs it against the validated wheel, and appends a tally to
 `dist/conformance-results.md`.
 
 The configured human user must already exist and authenticate with a legacy login passphrase and

{sg_python_api-0.1.1 → sg_python_api-0.1.2}/docs/migration-guide.md

@@ -2,7 +2,7 @@
 
 This guide is for applications that use Autodesk's `shotgun_api3` client and want to switch to
 sg-python-api. sg-python-api keeps the `shotgun_api3` import name and targets the documented API of
-Autodesk's client `3.10.2`, so migration mainly concerns installation, network policy, and failure
+Autodesk's client `3.10.3`, so migration mainly concerns installation, network policy, and failure
 handling. Work in your application's test environment first, so you can validate its actual queries
 and writes before changing a production deployment. For a new integration, start with the
 [README quick start](../README.md#quick-start) instead.

{sg_python_api-0.1.1 → sg_python_api-0.1.2}/pyproject.toml

@@ -10,7 +10,7 @@ requires = [ "editables~=0.3", "hatch-fancy-pypi-readme>=25.1", "hatchling>=1.27
 # ==========================================================
 [project]
 name = "sg-python-api"
-version = "0.1.1"
+version = "0.1.2"
 description = "Python client for Autodesk Flow Production Tracking"
 keywords = [ "api", "flow-production-tracking", "shotgrid", "shotgun", "shotgun-api3" ]
 license = "MIT"
@@ -138,6 +138,7 @@ max_supported_python = "3.15"
 [tool.pyright]
 pythonVersion = "3.11"  # Keep in sync with tool.ruff.target-version
 typeCheckingMode = "strict"
+exclude = [ "dist" ]
 extraPaths = [ ".", "src" ]
 executionEnvironments = [
   { root = "tests", reportPrivateUsage = "none" },

{sg_python_api-0.1.1 → sg_python_api-0.1.2}/scripts/_sdist_contract.py

@@ -22,7 +22,7 @@ if TYPE_CHECKING:
 _ARTIFACT_ARGUMENT_COUNT = 6
 _COMMAND_ARGUMENT_COUNT = 3
 _DIRECT_DOC_PART_COUNT = 2
-_EXPECTED_VERSION = '0.1.1'
+_EXPECTED_VERSION = '0.1.2'
 _REGULAR_MEMBER_TYPES = frozenset({tarfile.AREGTYPE, tarfile.REGTYPE})
 _ROOT_SOURCE_FILES = frozenset(
     {