Skip to main content

Python inline calendar for telegram bots with persian jalali date support

Project description

persian-telegram-bot-calendar

CodeFactor cock

This is fork of artembakhanov/python-telegram-bot-calendar which support jalali calendar. Very simple inline calendar for your bot.

Getting Started

This library is tested on Python 3.6 - 3.12.

Installation

pip install persian-telegram-bot-calendar

Usage

There is one main class - DetailedTelegramCalendar that can be used as follows. This is the example for pyTelegramBotAPI library. Other libraries are also supported.

from telegram_bot_calendar import DetailedTelegramCalendar, LSTEP

...
@bot.message_handler(commands=['start'])
def start(m):
    calendar, step = DetailedTelegramCalendar(locale='fa').build()
    bot.send_message(m.chat.id,
                     f"Select {LSTEP[step]}",
                     reply_markup=calendar)


@bot.callback_query_handler(func=DetailedTelegramCalendar.func())
def cal(c):
    result, key, step = DetailedTelegramCalendar(locale='fa').process(c.data)
    if not result and key:
        bot.edit_message_text(f"Select {LSTEP[step]}",
                              c.message.chat.id,
                              c.message.message_id,
                              reply_markup=key)
    elif result:
        bot.edit_message_text(f"You selected {result}",
                              c.message.chat.id,
                              c.message.message_id)

In start handler the calendar is created. Several arguments can be passed:

  • calendar_id - small integer or string, used for calendar identification. It used when you need several different calendars (default - 0)
  • current_date - datetime.date object, initial date value (default - today date)
  • additional_buttons - 1D list of buttons that will be added to the bottom of the calendar
  • locale - either en, ru, eo or fa can be added more. fa is required to work in persian
  • min_date and max_date - both are used as min and max values for the calendar

As you can see, special function that is provided should be passed to callback query handler. It will automatically work. The function takes only one argument - calendar_id that is 0 by default.

In the body of the handler function you need to call process function on callback data. WARNING! You need to create the calendar object again if it was not saved before.

The function process return tuple of size 3 - result, keyboard, step.

  • result - datetime.date object if user finished selecting. Otherwise None
  • keyboard - inline keyboard markup if the result is not ready. Otherwise None
  • step - YEAR, MONTH, or DAY if not ready. None is also possible if there is no change in keyboard.

Advanced use

Several calendars

You can create as many calendars as you want. However, in order to handle them properly set different calendar_id's when you want to distinguish them. Take a look at examples.

Date ranges

In the class constructor min_date and max_date - both are used as min and max values for the calendar. If you add them, the calendar will not show undesired dates. Example: 3

Custom style

You can also write your own code. One of the examples is redefining the steps order.

In the package you can find WMonthTelegramCalendar and WYearTelegramCalendar that start from day and month selecting, not from year.

You can also redefine style parameters. Example:

class MyStyleCalendar(DetailedTelegramCalendar):
    # previous and next buttons style. they are emoji now!
    prev_button = "⬅️"
    next_button = "➡️"
    # you do not want empty cells when month and year are being selected
    empty_month_button = ""
    empty_year_button = ""

You will get:

4

Custom Translation

your_translation_months = list('abcdefghijkl')
your_translation_days_of_week = list('yourtra')

class MyTranslationCalendar(DetailedTelegramCalendar):
    def __init__(self, **kwargs):
        super().__init__(**kwargs)
        self.days_of_week['yourtransl'] = your_translation_days_of_week
        self.months['yourtransl'] = your_translation_months

5

Examples

Contributing

Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/yourFeature)
  3. Commit your Changes (git commit -m 'Add some yourFeature')
  4. Push to the Branch (git push origin feature/yourFeature)
  5. Open a Pull Request

Authors

License

This project is licensed under the MIT License - see the LICENSE file for details

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

persian_telegram_bot_calendar-1.1.1.tar.gz (11.0 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

persian_telegram_bot_calendar-1.1.1-py3-none-any.whl (10.8 kB view details)

Uploaded Python 3

File details

Details for the file persian_telegram_bot_calendar-1.1.1.tar.gz.

File metadata

File hashes

Hashes for persian_telegram_bot_calendar-1.1.1.tar.gz
Algorithm Hash digest
SHA256 549e21941b20b3a8da9723240a1aaa74292a5fe47b20655436981bc7719610c5
MD5 4a992120a36a5114dbecaf1d6f52ebb5
BLAKE2b-256 1214954a850be36b8deb0f3bd64cf770d2840d57a5fa5b9d54db1b56969b49c5

See more details on using hashes here.

File details

Details for the file persian_telegram_bot_calendar-1.1.1-py3-none-any.whl.

File metadata

File hashes

Hashes for persian_telegram_bot_calendar-1.1.1-py3-none-any.whl
Algorithm Hash digest
SHA256 95b297f81277bd5a0632e1eab41d14656af524d4bee948094630825e819574ad
MD5 7417db1256913e16ace32c6342177161
BLAKE2b-256 2927739a35a09887e7a26b55efe851ace6915be831f23fa65415db44144e137d

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page