Skip to content

Split internal code for better maintainability #619

@jsmnbom

Description

@jsmnbom

Currently all our telegram.* classes are all jumbled up in a single folder, and it's starting to get a bit unwieldy. I propose we split it into a few folders - much like the telegram documentation also does (Inline, Games, Payments).
We can still have everything exported in the telegram module (and we really should), so it should be fully backwards compatible provided you've done something like from telegram import User or simply import telegram, - in fact the only time it wouldn't work is if they've hardcoded the module such as from telegram.user import User, but I've never actually seen anyone do that, so I think we're fine.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy