Hi, we have some news for you!

We just moved the project from Leandros GitHub account to a GitHub-Organization called python-telegram-bot at https://github.com/orgs/python-telegram-bot/

We changed all URLs to point to the new project location, but old URLs should be redirected automatically.

For you, nothing should change. This is part of our plan to give the whole project more seriousness, and also to seperate the project from Leandro a bit, since he doesn't find the time to care for the project as much as he wants.

Eventually, Jannes (@jh0ker) will take the lead of the project. Leandro will keep being a part of it, though.

Thanks everyone for your help and support! It has been a pleasure being part of this. Keep up the good work - reporting bugs, requesting features, helping new users...

Y'all are rock stars! Have a great week!

Hey, we just released v3.1, which contains the following changes:

- The chat-field in Message is now of the new type Chat. (API update Oct 8 2015)
- Message now contains the optional fields supergroup_chat_created, migrate_to_chat_id, migrate_from_chat_id and channel_chat_created. (API update Nov 2015)

This might break backwards compability to v3.0, if you used the GroupChat class, which has been removed in favour of Chat. Please check before updating.

Released v3.1.1

- Fix a bug where handlers that use the @run_async-decorator could not have additional arguments
- Add groups and groupdict as additional optional arguments for regex-based handlers

Note: Handlers that use the @run_async-decorator are now required to have **kwargs at the end of their argument list. This enables them to receive optional arguments, as well. Please keep that in mind before updating.

Released v3.1.2

- Fix custom path for file downloads
- Don't stop the dispatcher thread on uncaught errors in handlers
- Change default poll interval in Updater from 1 to 0

Released v3.2

- Introducing JobQueue (original author: @franciscod)
- Streamlining all exceptions to TelegramError (Special thanks to @tsnoam)
- Proper locking of Updater and Dispatcher start and stop methods
- Small bugfixes

For more info on the JobQueue, check the README or take a look this example: https://github.com/python-telegram-bot/python-telegram-bot/blob/master/examples/timerbot.py

Also, since we changed all exceptions to TelegramError, you might want to check you exception handling code before updating in production.

We just published v3.3b1, which is a beta version for the inline bot API. Please check the attached example, and the Telegram Bot API resources.
Example: https://github.com/python-telegram-bot/python-telegram-bot/blob/inlinebots/examples/inlinebot.py

New stable release v3.3! It features

- Inline bots
- Send any file by URL
- Specialized exceptions: Unauthorized, InvalidToken, NetworkError and TimedOut
- Integration for botan.io (thanks to @ollmer)
- HTML Parsemode (thanks to @jlmadurga)
- Bugfixes and under-the-hood improvements

**Very special thanks to Noam Meltzer (@tsnoam) for all of his work!**

New stable release v3.4! It features

- Move Updater, Dispatcher and JobQueue to new telegram.ext submodule (thanks to @rahiel)
- Add disable_notification parameter (thanks to @aidarbiktimirov)
- Fix bug where commands sent by Telegram Web client would not be recognized (thanks to @shelomentsevd)
- Add option to skip old updates on bot startup
- Send files from BufferedReader

Released 4.0rc1

- Implement Bot API 2.0
- Almost complete recode of Dispatcher
- Please read the Transition Guide to 4.0: https://github.com/python-telegram-bot/python-telegram-bot/wiki/Transistion-guide-to-Version-4.0

To install, use pip install python-telegram-bot==4.0rc1
Please note: This release is not backwards compatible to 3.4

We also have a small website now: https://python-telegram-bot.org/

Released v4.0.1

- Implement Bot API 2.0
- Almost complete recode of Dispatcher
- Please read the Transition Guide to 4.0
- Changes from 4.0rc1
- The syntax of filters for MessageHandler (upper/lower cases)
- Handler groups are now identified by int only, and ordered
- Note: v4.0 has been skipped due to a PyPi accident

Transition guide: https://github.com/python-telegram-bot/python-telegram-bot/wiki/Transition-guide-to-Version-4.0

Update to latest version:
pip install -U python-telegram-bot

Released 4.0.2

- Bugfixes
- KeyboardReplyMarkup now accepts str again

Update with pip install -U python-telegram-bot

Released 4.0.3

- Add missing attribute location to InlineQuery

We couldn't find 4.0.4 to release this time, releasing 4.1 instead. 😉

Released 4.1

- Implement API changes from May 6, 2016
- Fix bug when start_polling with clean=True
- Methods now have snake_case equivalent, for example telegram.Bot.send_message is the same as telegram.Bot.sendMessage

Released v4.1.1
This release fixes the Deprecation warning caused by Dispatcher using two newly deprecated (mostly internally used) methods 😁

We are currently considering dropping Python 2.6 support. Would you mind answering this quick poll? https://www.strawpoll.me/10227996

Released v4.1.2

This is a fix release for a critical bug due to Bot API 2.1 changes, where getUpdates would fail.
Please update immediately:
pip install -U python-telegram-bot

Released v4.2

- Implement Bot API 2.1
- Move botan module to telegram.contrib
- New exception type: BadRequest

Also, we have a small tutorial now: https://github.com/python-telegram-bot/python-telegram-bot/wiki/Extensions-%E2%80%93-Your-first-Bot

Update to latest version with pip install -U python-telegram-bot

PS: We're already working on v5.0, featuring an improved JobQueue and better Emoji support.

Released v4.2.1

Minor bug fixes:

- Fix CallbackQuery.to_dict() bug (thanks to jlmadurga)
- Fix editMessageText exception when receiving a CallbackQuery

Update to latest version:
$ pip install -U python-telegram-bot

Released v4.3

- Use urllib3.PoolManager for connection re-use
- Rewrite run_async decorator to re-use threads
- New requirements: urllib3 and certifi

This release significantly improves performance, so we decided to release it separetely from v5.0, which is coming during the next weeks.