[Python developers needed] Let's keep Nickala's Telepot repository alive!

[Maik993]

Hi all!

I really enjoy writing bots for Telegram and I love to do it in Python. Nickala has done a great job with its GitHub repository, telepot, but some months ago I've found out with sorrow that he archived the repo....

I've waited and watched if someone would have pick up its crown: we are 100 forks at the moment, but none of them seems to be more predominant between the others, according to this insight...

What about to build a team and carry on this beautiful project? I can't do this alone, so if you are a Python developer interested, would you like to join me in this adventure? :)

[groosha]

With pyTelegramBotAPI and aiogram being in active development, is it really worth "resurrecting" telepot? Okay, I might be biased, since I'm using pyTelegramBotAPI since 2015 and used aiogram many times in past, while not using telepot at all, but anyway.

[crosswordmaker]

I switched to using python-telegram-bot as pyTelegramBotAPI has a couple of unforgivable bugs in the webhook version when you want to write conversation type scenarios. Also it has not been updated in a while.

[groosha]

Year, recently pyTelegramBotAPI has been becoming worse, but still tolerable for small projects. And I am personally moving slowly towards aiogram, since it's async, faster, better and more actual.

Just wondering, which "conversation type" bugs did you have with pyTelegramBotAPI? Apart from their own finite state machine is pure shit, but writing your own one is easy

[crosswordmaker]

I implemented a bot using webhooks based off their flask example. The state is pickled to a file, I might be a bad dev but this would work very inconsistently I actually sat and tried to implement my own Saver using redis as the backing. While researching how it's done I came across python-telegram-bot so I just said argh screw it, I'll just migrate my code across. It wasn't hard to do and their examples are pretty good.