Rongrong

Hi there, @inyutin. I consider you should at least bump the minor version (`a.B.c`) instead of the patch version (`a.b.C`) since it is a breaking API change for those users...

The new release is fine. Should v2.5.6 be yanked from PyPI? It may help prevent loose versions from selecting it.

Self-hosted or public demo?

I got more data in production. I have two instances of https://github.com/Rongronggg9/RSS-to-Telegram-Bot on the same VPS. One with ~4000 feeds, another one with ~3000 feeds. The bot will check the...

Hi, @lemon24. Thanks for your share. I can confirm that your statement "I am not convinced this is a memory leak in feedparser" is true. `BeautifulSoup(something, 'html.parser')` (`html.parser` is written...

A better workaround for multithread programs is to replace the `ptmalloc` from `glibc` with `jemalloc`. https://github.com/Rongronggg9/RSS-to-Telegram-Bot/commit/ae69f738cab53f21f4587272cfce5f22915182a6 https://github.com/Rongronggg9/RSS-to-Telegram-Bot/commit/eb07fa91f7ba9f49584f9effea1488bd0142d7b4 `jemalloc` shows impressive performance while maintaining a high memory recycling rate on multithread...

Try https://github.com/Rongronggg9/RSS-to-Telegram-Bot

> > Try [Rongronggg9/RSS-to-Telegram-Bot](https://github.com/Rongronggg9/RSS-to-Telegram-Bot) > > Wow, that's not even a fork? Thanks I'll check it out. https://github.com/Rongronggg9/RSS-to-Telegram-Bot#license > The repository is formerly a fork of [BoKKeR/RSS-to-Telegram-Bot](https://github.com/BoKKeR/RSS-to-Telegram-Bot). They have been...

> Afterwards I would like to remove this `fallback_import` behavior again, since it should be better for a user to specify `rapidfuzz[speedup]` as dependency instead of setting a random environment...

OK then. There is still something that can be improved. Practically speaking, `speedup` is not a good `extra_require` name since the only difference it makes is to throw an error...