richpyro 1.0.0__tar.gz

richpyro-1.0.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 devgagan
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

richpyro-1.0.0/MANIFEST.in

@@ -0,0 +1,3 @@
+include README.md
+include LICENSE
+recursive-include src/richpyro py.typed

richpyro-1.0.0/PKG-INFO

@@ -0,0 +1,144 @@
+Metadata-Version: 2.4
+Name: richpyro
+Version: 1.0.0
+Summary: A complete, easy-to-call wrapper for Pyrogram Rich Messages (Bot API 10.1+) — every block, every text style, every button type, with bot/user-account fallback and chat_id safety built in.
+Author: devgagan
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/devgaganin/richpyro
+Project-URL: Repository, https://github.com/devgaganin/richpyro
+Project-URL: Issues, https://github.com/devgaganin/richpyro/issues
+Keywords: telegram,pyrogram,kurigram,telegram-bot,bot-api,rich-message,rich-messages,telegram-api
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+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 :: Communications :: Chat
+Classifier: Topic :: Internet
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Typing :: Typed
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: Kurigram>=2.2.26
+Dynamic: license-file
+
+# richpyro
+
+A complete, easy-to-call wrapper around [kurigram](https://github.com/kurimuzon/kurigram)'s
+**Rich Messages** (Telegram Bot API 10.1+ `InputRichMessage` / `InputRichBlock*` /
+`RichText*`, plus `Client.send_rich_message`, `Message.edit_text(rich_message=...)`
+and `Message.reply_rich`).
+
+Every block type, every text style, every button type — one flat, documented
+function per thing, plus a safe `send()` / `edit()` / `reply()` call surface
+that handles two real Telegram/kurigram footguns automatically so you never
+have to think about them.
+
+```bash
+pip install richpyro
+```
+
+## Why
+
+Rich Messages are powerful but the raw API is deep (~50 constructor types)
+and has two sharp edges that fail silently in production:
+
+1. **Rich Messages only render for bot accounts.** Send `rich_message=...`
+   from a real user/userbot client (a logged-in session, not a bot token)
+   and Telegram silently drops or rejects it — no visible error, your
+   progress bar / status card just stops updating.
+2. **A numeric-string `chat_id` looks like a phone number to kurigram.**
+   `Client.resolve_peer()` strips `+()-` and whitespace from any string
+   `chat_id`; if what's left is all digits, it assumes it's a phone number
+   and calls `contacts.ResolvePhone` — a method **bot accounts cannot call
+   at all** (`[400 BOT_METHOD_INVALID]`), and which fails with
+   `PHONE_NOT_OCCUPIED` for user accounts too unless that string happens to
+   be someone's real registered phone number. This bites silently any time
+   a chat id is passed as `str(chat.id)` instead of `int` — an extremely
+   easy mistake, since chat ids get stringified for DB keys/dict lookups
+   all over a typical bot codebase and then get reused as-is for an API call.
+
+`richpyro.send()` / `.edit()` / `.reply()` check `client.me.is_bot` and
+auto-degrade to an equivalent plain-text message for user-account senders,
+and auto-int-ify any numeric-string `chat_id` before it reaches kurigram
+(`@usernames` pass through untouched). You get both fixes for free just by
+using this library's call surface instead of the raw kurigram methods.
+
+## Quick start
+
+```python
+import richpyro as rp
+
+# simplest possible call — one line, works from a bot OR a user client:
+await rp.quick(client, chat_id, "Processing your request...")
+
+# a structured card with formatting + buttons:
+card = rp.message(
+    rp.para("Hello ", rp.bold(name), "! Choose a plan:"),
+    rp.divider(),
+    rp.para("● ", rp.bold("Day Plan"), " — ₹20 (24 hours)"),
+    rp.buttons(
+        rp.btn("Day Plan ₹20", "pay_day"),
+        rp.url_btn("Learn more", "https://example.com"),
+    ),
+)
+sent = await rp.send(client, chat_id, card)
+...
+await rp.edit(client, chat_id, sent.id, rp.text("Payment confirmed."))
+
+# replying directly to an incoming message (uses its own client):
+await rp.reply(message, card)
+```
+
+Every builder returns a plain kurigram object — you can always drop down to
+raw `types.InputRichMessage(...)` etc. for anything this library doesn't
+wrap yet. richpyro objects and raw kurigram objects mix freely; nothing here
+subclasses kurigram, it only constructs.
+
+## What's covered
+
+**Text formatting** — `bold`, `italic`, `underline`, `strike`, `spoiler`,
+`code`, `link`, `user_mention`, `mention`, `custom_emoji`, `hashtag`,
+`bot_command`, `phone_number`, `email`, `cashtag`, `bank_card`, `date_time`,
+`subscript`, `superscript`, `anchor_target`, `anchor_link`, `footnote_ref`,
+`footnote_link`, `marked`, `math_inline`, `inline_button`.
+
+**Buttons** — `btn` (callback), `url_btn`, `webapp_btn`, `login_btn`,
+`switch_inline_btn`, `switch_inline_here_btn`, `switch_inline_chosen_btn`,
+`copy_btn`, `disabled_btn`, plus `buttons(...)` to lay out a row and
+`Style` (`DEFAULT` / `PRIMARY` / `DANGER` / `SUCCESS` / `LINK`).
+
+**Blocks** — `para`, `heading`, `divider`, `footer`, `anchor_block`,
+`photo_block`, `video_block`, `animation_block`, `audio_block`,
+`document_block`, `voice_block` (with matching `*_media` input helpers and
+`caption(...)`), `collage`, `slideshow`, `list_item` / `bullet_list`,
+`table_cell` / `table`, `details`, `blockquote`, `expandable_quote`,
+`pull_quote`, `preformatted`, `map_block`, `math_block`, `thinking`.
+
+**Message assembly** — `message(*blocks)` (the main entry point),
+`html_message`, `markdown_message`, `text(...)` (the single-line shortcut
+for the common case).
+
+**Safe send surface** — `send`, `edit`, `reply`, `quick`, `quick_edit`,
+`is_bot_client`, and `flatten_message` (the plain-text renderer used
+automatically for the bot → user-account fallback, also handy standalone
+for logs/previews).
+
+## Requirements
+
+- Python 3.9+
+- [Kurigram](https://pypi.org/project/Kurigram/) 2.2.26+ (the actively
+  maintained Pyrogram fork with Rich Messages support — still `import pyrogram`)
+
+## License
+
+MIT — see [LICENSE](LICENSE).
+
+## Author
+
+coded by **devgagan** — [github.com/devgaganin](https://github.com/devgaganin)

richpyro-1.0.0/README.md

@@ -0,0 +1,115 @@
+# richpyro
+
+A complete, easy-to-call wrapper around [kurigram](https://github.com/kurimuzon/kurigram)'s
+**Rich Messages** (Telegram Bot API 10.1+ `InputRichMessage` / `InputRichBlock*` /
+`RichText*`, plus `Client.send_rich_message`, `Message.edit_text(rich_message=...)`
+and `Message.reply_rich`).
+
+Every block type, every text style, every button type — one flat, documented
+function per thing, plus a safe `send()` / `edit()` / `reply()` call surface
+that handles two real Telegram/kurigram footguns automatically so you never
+have to think about them.
+
+```bash
+pip install richpyro
+```
+
+## Why
+
+Rich Messages are powerful but the raw API is deep (~50 constructor types)
+and has two sharp edges that fail silently in production:
+
+1. **Rich Messages only render for bot accounts.** Send `rich_message=...`
+   from a real user/userbot client (a logged-in session, not a bot token)
+   and Telegram silently drops or rejects it — no visible error, your
+   progress bar / status card just stops updating.
+2. **A numeric-string `chat_id` looks like a phone number to kurigram.**
+   `Client.resolve_peer()` strips `+()-` and whitespace from any string
+   `chat_id`; if what's left is all digits, it assumes it's a phone number
+   and calls `contacts.ResolvePhone` — a method **bot accounts cannot call
+   at all** (`[400 BOT_METHOD_INVALID]`), and which fails with
+   `PHONE_NOT_OCCUPIED` for user accounts too unless that string happens to
+   be someone's real registered phone number. This bites silently any time
+   a chat id is passed as `str(chat.id)` instead of `int` — an extremely
+   easy mistake, since chat ids get stringified for DB keys/dict lookups
+   all over a typical bot codebase and then get reused as-is for an API call.
+
+`richpyro.send()` / `.edit()` / `.reply()` check `client.me.is_bot` and
+auto-degrade to an equivalent plain-text message for user-account senders,
+and auto-int-ify any numeric-string `chat_id` before it reaches kurigram
+(`@usernames` pass through untouched). You get both fixes for free just by
+using this library's call surface instead of the raw kurigram methods.
+
+## Quick start
+
+```python
+import richpyro as rp
+
+# simplest possible call — one line, works from a bot OR a user client:
+await rp.quick(client, chat_id, "Processing your request...")
+
+# a structured card with formatting + buttons:
+card = rp.message(
+    rp.para("Hello ", rp.bold(name), "! Choose a plan:"),
+    rp.divider(),
+    rp.para("● ", rp.bold("Day Plan"), " — ₹20 (24 hours)"),
+    rp.buttons(
+        rp.btn("Day Plan ₹20", "pay_day"),
+        rp.url_btn("Learn more", "https://example.com"),
+    ),
+)
+sent = await rp.send(client, chat_id, card)
+...
+await rp.edit(client, chat_id, sent.id, rp.text("Payment confirmed."))
+
+# replying directly to an incoming message (uses its own client):
+await rp.reply(message, card)
+```
+
+Every builder returns a plain kurigram object — you can always drop down to
+raw `types.InputRichMessage(...)` etc. for anything this library doesn't
+wrap yet. richpyro objects and raw kurigram objects mix freely; nothing here
+subclasses kurigram, it only constructs.
+
+## What's covered
+
+**Text formatting** — `bold`, `italic`, `underline`, `strike`, `spoiler`,
+`code`, `link`, `user_mention`, `mention`, `custom_emoji`, `hashtag`,
+`bot_command`, `phone_number`, `email`, `cashtag`, `bank_card`, `date_time`,
+`subscript`, `superscript`, `anchor_target`, `anchor_link`, `footnote_ref`,
+`footnote_link`, `marked`, `math_inline`, `inline_button`.
+
+**Buttons** — `btn` (callback), `url_btn`, `webapp_btn`, `login_btn`,
+`switch_inline_btn`, `switch_inline_here_btn`, `switch_inline_chosen_btn`,
+`copy_btn`, `disabled_btn`, plus `buttons(...)` to lay out a row and
+`Style` (`DEFAULT` / `PRIMARY` / `DANGER` / `SUCCESS` / `LINK`).
+
+**Blocks** — `para`, `heading`, `divider`, `footer`, `anchor_block`,
+`photo_block`, `video_block`, `animation_block`, `audio_block`,
+`document_block`, `voice_block` (with matching `*_media` input helpers and
+`caption(...)`), `collage`, `slideshow`, `list_item` / `bullet_list`,
+`table_cell` / `table`, `details`, `blockquote`, `expandable_quote`,
+`pull_quote`, `preformatted`, `map_block`, `math_block`, `thinking`.
+
+**Message assembly** — `message(*blocks)` (the main entry point),
+`html_message`, `markdown_message`, `text(...)` (the single-line shortcut
+for the common case).
+
+**Safe send surface** — `send`, `edit`, `reply`, `quick`, `quick_edit`,
+`is_bot_client`, and `flatten_message` (the plain-text renderer used
+automatically for the bot → user-account fallback, also handy standalone
+for logs/previews).
+
+## Requirements
+
+- Python 3.9+
+- [Kurigram](https://pypi.org/project/Kurigram/) 2.2.26+ (the actively
+  maintained Pyrogram fork with Rich Messages support — still `import pyrogram`)
+
+## License
+
+MIT — see [LICENSE](LICENSE).
+
+## Author
+
+coded by **devgagan** — [github.com/devgaganin](https://github.com/devgaganin)

richpyro-1.0.0/pyproject.toml

@@ -0,0 +1,48 @@
+[build-system]
+requires = ["setuptools>=68", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "richpyro"
+version = "1.0.0"
+description = "A complete, easy-to-call wrapper for Pyrogram Rich Messages (Bot API 10.1+) — every block, every text style, every button type, with bot/user-account fallback and chat_id safety built in."
+readme = "README.md"
+requires-python = ">=3.9"
+license = "MIT"
+license-files = ["LICENSE"]
+authors = [
+    { name = "devgagan" },
+]
+keywords = [
+    "telegram", "pyrogram", "kurigram", "telegram-bot", "bot-api",
+    "rich-message", "rich-messages", "telegram-api",
+]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Developers",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.9",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Communications :: Chat",
+    "Topic :: Internet",
+    "Topic :: Software Development :: Libraries :: Python Modules",
+    "Typing :: Typed",
+]
+dependencies = [
+    "Kurigram>=2.2.26",
+]
+
+[project.urls]
+Homepage = "https://github.com/devgaganin/richpyro"
+Repository = "https://github.com/devgaganin/richpyro"
+Issues = "https://github.com/devgaganin/richpyro/issues"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+richpyro = ["py.typed"]

richpyro-1.0.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+