linq-python 0.52.2__tar.gz → 0.53.0__tar.gz

linq_python-0.53.0/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "0.53.0"
+}

{linq_python-0.52.2 → linq_python-0.53.0}/CHANGELOG.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## [0.53.0](https://github.com/linq-team/linq-python/compare/v0.52.3...v0.53.0) (2026-09-11)
+
+
+### Features
+
+* clarify sticker behavior for animated images and simplify docs ([d509801](https://github.com/linq-team/linq-python/commit/d509801aa648c190961b9772367e7030883b7d1b))
+
+## [0.52.3](https://github.com/linq-team/linq-python/compare/v0.52.2...v0.52.3) (2026-09-11)
+
+
+### Bug Fixes
+
+* clarify location sharing stop endpoint behavior ([7c606b2](https://github.com/linq-team/linq-python/commit/7c606b2b0c3f8e5e16927e08d9c954f7abfe71d1))
+
 ## [0.52.2](https://github.com/linq-team/linq-python/compare/v0.52.1...v0.52.2) (2026-09-11)
 
 

{linq_python-0.52.2 → linq_python-0.53.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.3
 Name: linq-python
-Version: 0.52.2
+Version: 0.53.0
 Summary: The official Python library for the linq-api-v3 API
 Project-URL: Homepage, https://github.com/linq-team/linq-python
 Project-URL: Repository, https://github.com/linq-team/linq-python

{linq_python-0.52.2 → linq_python-0.53.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "linq-python"
-version = "0.52.2"
+version = "0.53.0"
 description = "The official Python library for the linq-api-v3 API"
 dynamic = ["readme"]
 license = "Apache-2.0"

{linq_python-0.52.2 → linq_python-0.53.0}/src/linq/_version.py

@@ -1,4 +1,4 @@
 # File generated from our OpenAPI spec by Stainless. See CONTRIBUTING.md for details.
 
 __title__ = "linq"
-__version__ = "0.52.2"  # x-release-please-version
+__version__ = "0.53.0"  # x-release-please-version

{linq_python-0.52.2 → linq_python-0.53.0}/src/linq/resources/chats/location.py

@@ -201,33 +201,19 @@ class LocationResource(SyncAPIResource):
         extra_body: Body | None = None,
         timeout: float | httpx.Timeout | None | NotGiven = not_given,
     ) -> StopChatLocationSharingResponse:
-        """
-        End the location share a contact started with you, as though they had stopped it
-        themselves. Their device stops listing you as someone they share with, so they
-        can start a fresh share cleanly.
-
-        Use this to recover when a share has gone stale — coordinates that stop
-        advancing, or a share you believe has ended but is still reported as active.
-        Without it the only remedy is asking the contact to stop and re-share, which is
-        confusing for them because their phone still shows everything as working.
-
-        This is not reversible from the API. Sharing can only resume when the contact
-        starts a new share, so prompt them to re-share afterwards. Request a new one
-        with `POST /v3/chats/{chatId}/location/request`.
+        """Stop a contact's location share with you.
 
-        Apple keeps one location-sharing relationship per person rather than per chat,
-        so this ends that contact's share everywhere, not only in this chat.
+        `handle` is required and names whose
+        share to end.
 
-        `handle` names whose share to end, and is always required — a group chat can
-        have several people sharing, and this is not an operation to infer a target for.
+        Returns `202` when the request is accepted. The stop is carried out on the
+        contact's device, and the `location.sharing.stopped` webhook fires once sharing
+        has ended.
 
-        **This returns `202`, not `200`.** The removal happens on the device that holds
-        the sharing relationship, so a success here means the request was accepted, not
-        that sharing has ended. Wait for the `location.sharing.stopped` webhook to
-        confirm it — that webhook is what tells you the contact's device has actually
-        let go.
+        Sharing is per contact, so this ends that contact's share in every chat you have
+        with them.
 
-        Returns `404` if the contact is not currently sharing.
+        Returns `404` if the contact isn't currently sharing.
 
         Args:
           handle: Phone number (E.164 format) or email address of the contact whose share to end
@@ -430,33 +416,19 @@ class AsyncLocationResource(AsyncAPIResource):
         extra_body: Body | None = None,
         timeout: float | httpx.Timeout | None | NotGiven = not_given,
     ) -> StopChatLocationSharingResponse:
-        """
-        End the location share a contact started with you, as though they had stopped it
-        themselves. Their device stops listing you as someone they share with, so they
-        can start a fresh share cleanly.
-
-        Use this to recover when a share has gone stale — coordinates that stop
-        advancing, or a share you believe has ended but is still reported as active.
-        Without it the only remedy is asking the contact to stop and re-share, which is
-        confusing for them because their phone still shows everything as working.
-
-        This is not reversible from the API. Sharing can only resume when the contact
-        starts a new share, so prompt them to re-share afterwards. Request a new one
-        with `POST /v3/chats/{chatId}/location/request`.
+        """Stop a contact's location share with you.
 
-        Apple keeps one location-sharing relationship per person rather than per chat,
-        so this ends that contact's share everywhere, not only in this chat.
+        `handle` is required and names whose
+        share to end.
 
-        `handle` names whose share to end, and is always required — a group chat can
-        have several people sharing, and this is not an operation to infer a target for.
+        Returns `202` when the request is accepted. The stop is carried out on the
+        contact's device, and the `location.sharing.stopped` webhook fires once sharing
+        has ended.
 
-        **This returns `202`, not `200`.** The removal happens on the device that holds
-        the sharing relationship, so a success here means the request was accepted, not
-        that sharing has ended. Wait for the `location.sharing.stopped` webhook to
-        confirm it — that webhook is what tells you the contact's device has actually
-        let go.
+        Sharing is per contact, so this ends that contact's share in every chat you have
+        with them.
 
-        Returns `404` if the contact is not currently sharing.
+        Returns `404` if the contact isn't currently sharing.
 
         Args:
           handle: Phone number (E.164 format) or email address of the contact whose share to end

{linq_python-0.52.2 → linq_python-0.53.0}/src/linq/resources/messages/messages.py

@@ -515,10 +515,11 @@ class MessagesResource(SyncAPIResource):
         `sticker` is peeled onto the bubble itself, and can be dragged, resized and
         rotated. Both accept an emoji; they do not look alike.
 
-        **Stickers** are iMessage-only and cannot be removed — iMessage has no unpeel
-        operation, so `operation: "remove"` with `type: "sticker"` is rejected.
-        Position, size and rotation are optional via `placement`, and can be changed
-        afterwards with `PATCH /v3/messages/{messageId}/reactions/{reactionId}`.
+        **Stickers** are iMessage-only and cannot be removed, so `operation: "remove"`
+        with `type: "sticker"` is rejected. Position, size and rotation are optional via
+        `placement`, and can be changed afterwards with
+        `PATCH /v3/messages/{messageId}/reactions/{reactionId}`. An animated image peels
+        as an animated sticker, in whatever shape the file already has.
 
         Args:
           operation: Whether to add or remove the reaction
@@ -541,8 +542,7 @@ class MessagesResource(SyncAPIResource):
               use type "sticker" with `emoji`.
 
           emoji: A single emoji to peel onto the message as a sticker. Only valid when type is
-              "sticker", and it is rendered on the device so it matches the glyph a person
-              would peel by hand.
+              "sticker".
 
               Exactly one of `emoji`, `url` or `attachment_id` is required when type is
               "sticker".
@@ -561,9 +561,8 @@ class MessagesResource(SyncAPIResource):
           url: Linq attachment URL of the sticker image — the `download_url` returned by
               `POST /v3/attachments`. Only valid when type is "sticker".
 
-              Unlike a media part, this does **not** accept an arbitrary host: reactions have
-              no download step, so the image must already be stored. To send a sticker from
-              elsewhere, upload it with `POST /v3/attachments` first and pass `attachment_id`.
+              The image must already be stored with us. To send a sticker from elsewhere,
+              upload it with `POST /v3/attachments` first and pass `attachment_id`.
 
               Exactly one of `emoji`, `url` or `attachment_id` is required when type is
               "sticker".
@@ -1303,10 +1302,11 @@ class AsyncMessagesResource(AsyncAPIResource):
         `sticker` is peeled onto the bubble itself, and can be dragged, resized and
         rotated. Both accept an emoji; they do not look alike.
 
-        **Stickers** are iMessage-only and cannot be removed — iMessage has no unpeel
-        operation, so `operation: "remove"` with `type: "sticker"` is rejected.
-        Position, size and rotation are optional via `placement`, and can be changed
-        afterwards with `PATCH /v3/messages/{messageId}/reactions/{reactionId}`.
+        **Stickers** are iMessage-only and cannot be removed, so `operation: "remove"`
+        with `type: "sticker"` is rejected. Position, size and rotation are optional via
+        `placement`, and can be changed afterwards with
+        `PATCH /v3/messages/{messageId}/reactions/{reactionId}`. An animated image peels
+        as an animated sticker, in whatever shape the file already has.
 
         Args:
           operation: Whether to add or remove the reaction
@@ -1329,8 +1329,7 @@ class AsyncMessagesResource(AsyncAPIResource):
               use type "sticker" with `emoji`.
 
           emoji: A single emoji to peel onto the message as a sticker. Only valid when type is
-              "sticker", and it is rendered on the device so it matches the glyph a person
-              would peel by hand.
+              "sticker".
 
               Exactly one of `emoji`, `url` or `attachment_id` is required when type is
               "sticker".
@@ -1349,9 +1348,8 @@ class AsyncMessagesResource(AsyncAPIResource):
           url: Linq attachment URL of the sticker image — the `download_url` returned by
               `POST /v3/attachments`. Only valid when type is "sticker".
 
-              Unlike a media part, this does **not** accept an arbitrary host: reactions have
-              no download step, so the image must already be stored. To send a sticker from
-              elsewhere, upload it with `POST /v3/attachments` first and pass `attachment_id`.
+              The image must already be stored with us. To send a sticker from elsewhere,
+              upload it with `POST /v3/attachments` first and pass `attachment_id`.
 
               Exactly one of `emoji`, `url` or `attachment_id` is required when type is
               "sticker".

{linq_python-0.52.2 → linq_python-0.53.0}/src/linq/types/media_part_param.py

@@ -26,10 +26,12 @@ class MediaPartParam(TypedDict, total=False):
     The recipient can peel it off and place it on any message in the conversation,
     and it renders without a bubble.
 
-    An opaque photo is cut out automatically — the subject is lifted from its
-    background, the same way "Add Sticker" does on iOS. An image that already has
-    transparency is sent as-is. If no subject can be found, the image sends as an
-    ordinary photo.
+    An ordinary photo is cut out automatically — the subject is lifted from its
+    background. An image that has already been cut out is sent as-is. If no subject
+    can be found, the image sends as an ordinary photo.
+
+    An animated image sends as an animated sticker, in whatever shape the file
+    already has — the cut-out does not apply to it.
 
     **iMessage only.** On SMS/RCS the flag is ignored and the image sends as a
     photo.

{linq_python-0.52.2 → linq_python-0.53.0}/src/linq/types/message_add_reaction_params.py

@@ -42,8 +42,7 @@ class MessageAddReactionParams(TypedDict, total=False):
     emoji: str
     """A single emoji to peel onto the message as a sticker.
 
-    Only valid when type is "sticker", and it is rendered on the device so it
-    matches the glyph a person would peel by hand.
+    Only valid when type is "sticker".
 
     Exactly one of `emoji`, `url` or `attachment_id` is required when type is
     "sticker".
@@ -71,9 +70,8 @@ class MessageAddReactionParams(TypedDict, total=False):
     Linq attachment URL of the sticker image — the `download_url` returned by
     `POST /v3/attachments`. Only valid when type is "sticker".
 
-    Unlike a media part, this does **not** accept an arbitrary host: reactions have
-    no download step, so the image must already be stored. To send a sticker from
-    elsewhere, upload it with `POST /v3/attachments` first and pass `attachment_id`.
+    The image must already be stored with us. To send a sticker from elsewhere,
+    upload it with `POST /v3/attachments` first and pass `attachment_id`.
 
     Exactly one of `emoji`, `url` or `attachment_id` is required when type is
     "sticker".

{linq_python-0.52.2 → linq_python-0.53.0}/uv.lock

@@ -530,7 +530,7 @@ wheels = [
 
 [[package]]
 name = "linq-python"
-version = "0.52.1"
+version = "0.52.3"
 source = { editable = "." }
 dependencies = [
     { name = "anyio" },

linq_python-0.52.2/.release-please-manifest.json

@@ -1,3 +0,0 @@
-{
-  ".": "0.52.2"
-}