Medusa support to be continued!

[OneCDOnly]

Important

2025-10-21: The application developers have updated Medusa so it will now run on Python 3.12.
2025-10-23: But still incompatible with Python 3.13.
2025-11-08: Python 3.13 compatibility has been pushed into the develop branch only.
2025-11-13: Python 3.13 compatibility has been pushed into the master branch.

---

Medusa appears to be a dead project. It hasn't been maintained and is known to be incompatible with Python 3.12 and-later. This means its days are numbered.

Presently, we are able to run Medusa because Python 3.11.7 is available through Entware. When the Entware folks next upgrade the Python packages to 3.12 or-later, Medusa will no-longer run. I don't know when this will happen, but it's safe-to-say it will happen eventually.

I highly recommend all Medusa users $\color{Red}\textbf{immediately}$ begin transitioning to another TV show handler. Don't wait until your Medusa instance won't start, the interruption to your TV shows will be far-worse if you do.

If your NAS supports Docker containers, you can continue with the Medusa docker image available here: https://hub.docker.com/r/pymedusa/medusa/ which should work with your existing Medusa database. But, this will require you to manually transfer the database files.

If-not, there are only two remaining TV show handlers available through sherpa: SickGear and Sonarr (64b):

• SickGear is a very stable, but feature-light version compared to more advanced handlers like Medusa. It doesn't have many of the newer options Medusa has, but it IS still being developed and supported.

• Sonarr is also actively developed and supported, but is compatible with 64b CPUs only.

[Kvothe1970]

Aw man. I get it but this sucks. I‘ll have to look at getting docker containers to work but my TS-431+ is pretty underpowered for that and can’t really be upgraded https://www.qnap.com/en/product/ts-431+/specs/hardware

[Kvothe1970]

So, let‘s assume I’ll go ahead and will get a new one, and keep this one as a backup target which would be an option as it’s still working just fine otherwise.: https://www.qnap.com/en/product/ts-464/specs/hardware/TS-464-8G.pdf

What do you think about this one? @OneCDOnly

[OneCDOnly]

Yes, looks good. The TS-464 is an excellent unit. It should remain supported for many years to-come. 👍🏽

[Kvothe1970]

Thank you for the feedback I appreciate it 😊 now looking at prices!

[papampi]

Hi mate,
I just asked in pyMedusa discord and Dariox replied
https://discord.com/channels/565118008943575050/1019854379886583839/threads/1427616742460493946

What makes them think Medusa is not maintained?
Python 3.12 works perfectly fine
Don't know where he gets that info from
https://github.com/pymedusa/Medusa/tree/develop
last commit 4 days ago
should I push a PR every 2 days to make the project seem more active?
Everything works and there are no issues

[Kvothe1970]

I am pleasantly surprised! @OneCDOnly want to take another look at this`? Mind you, I just ordered the new NAS etc anyway because I bought the current one in 2016 and all the disks etc are that old.. this is just me futureproofing the whole thing. Thanks a bunch for asking @papampi !

[OneCDOnly]

Hi @papampi and cheers for finding that. 👍🏽

Unfortunately, the developers haven't pushed this later Python version compatibility into the master branch. And - as a package maintainer - offering a develop branch to folks for production use is risky. It's far-more prone to breakages.

It's been a while since master was updated. That and the increasing number of security-related PRs they haven't merged leads me to think they're not maintaining this project.

Perhaps they would be kind-enough to update the master branch so we can keep using Medusa? 😉

[OneCDOnly]

And a relevant (still open) PR: pymedusa/Medusa#11967

[papampi]

Hi @medariox
Please check ..

[papampi]

Hi @OneCDOnly
Latest sherpa still gives warning of Medusa getting discontinued, is it still getting discontinued although project is not dead?

[OneCDOnly]

Hi mate, yes the warning will remain unless the Medusa folks update their master branch. I have to leave the warning there in-case the new Python version comes along through Entware.

[papampi]

Fair enough

[OneCDOnly]

If the devs haven't updated master before Entware updates Python, Medusa support will be - let's say - suspended, instead of discontinued.

I'm happy to continue supporting Medusa if the Medusa devs do the same. 😉

[papampi]

If the devs haven't updated master before Entware updates Python, Medusa support will be - let's say - suspended, instead of discontinued.

I'm happy to continue supporting Medusa if the Medusa devs do the same. 😉

@medariox

[Kvothe1970]

let there be light!
Or and update 😁 this looks great!

Repository: https://github.com/[pymedusa/Medusa](https://github.com/pymedusa/Medusa) · Tag: https://github.com/pymedusa/Medusa/tree/[v1.0.23](https://github.com/pymedusa/Medusa/tree/v1.0.23) · Commit: pymedusa/Medusa@[9906ba9](https://github.com/pymedusa/Medusa/commit/9906ba9868b6f9e77421450a77104d81d9acd39b)868b6f9e77421450a77104d81d9acd39b · Released by: https://github.com/[medariox](https://github.com/medariox)

New Features

• Add support for Python 3.12 and remove support for Python 3.7 and 3.8
• Add invalid episode status

Improvements

• Update many Python libs
• Update thexem tld from .de to .info (Thanks to https://github.com/borntohonk)
• Improve colors for history table
• Removed dependency on unmaintained docker container (Thanks to https://github.com/bobpaul)
• Set the WEB_PORT by enviroment variable if enviroment variable is set (Thanks to https://github.com/borntohonk)

Fixes

• Fix rare mass download of unset episodes
• Fix Python 3.12 support on some systems (Thanks to https://github.com/borntohonk)
• Fix Forced Search typo (Thanks to https://github.com/cheese1)
• Fix trakt episodes sync

—

This release has 2 assets:

• Source code (zip)
• Source code (tar.gz)

Visit the https://github.com/pymedusa/Medusa/releases/tag/v1.0.23 to download them.

[papampi]

V1.0.23 released.

[OneCDOnly]

That's great! Good work. I'll remove the sherpa message linking to this discussion page shortly. 🤓

[OneCDOnly]

... and done.

There's a new Medusa QPKG version. I had to remove that warning message from the QPKG service-script as-well. 😉

[Kvothe1970]

Fantastic, thanks so much 😊 this will be grand for the upcoming migration.

[OneCDOnly]

Just tried Medusa in a Python 3.13 environment : still no-go. 😞

It seems the recent Medusa push into master only added compatibility with Python 3.12.

Let's hope the next Python version jump in Entware isn't a big one.

[Kvothe1970]

Oh no :/
Did you have time to raise an issue in their repo?

[OneCDOnly]

There's already a pull request open for this. It's the one I linked-to earlier: pymedusa/Medusa#11967

[Kvothe1970]

And the new one now pymedusa/Medusa#12067

let’s see

[Kvothe1970]

Just tried Medusa in a Python 3.13 environment : still no-go. 😞

It seems the recent Medusa push into master only added compatibility with Python 3.12.

Let's hope the next Python version jump in Entware isn't a big one.

Just saw this on their discord confirming your finding. Fingers crossed the PR will go through

[OneCDOnly]

Received some good news from @zyxmon regarding the next Entware Python version: it's presently at 3.11.13.

So, if Entware were-to release a new package set today, that's the Python version we'd be working-with. 👍🏽

But, the next Entware release date is unknown, so it could change before then.

[Kvothe1970]

Fingers crossed.
They just released this https://github.com/pymedusa/Medusa/releases/tag/v1.0.24 but the PR is still open.

[Kvothe1970]

and I just saw this PR pymedusa/Medusa#12073 so I reckon we might just get the compatibility with 3.13 with this or the other PR

[Kvothe1970]

I guess this will be released. It was merged into develop so should only be a question of time :)

[Kvothe1970]

And here we are:

https://github.com/pymedusa/Medusa/releases/tag/v1.0.25

„ Add support for Python 3.13“ 😊

[OneCDOnly]

Ah, excellent news! 👍🏽