SABnzbd for Py3 stable yet?

[OneCD]

Hey guys, how's the code conversion to work with Python 3 going? Is the rewritten SABnzbd stable enough for everyday use?

I'm hoping to begin work on migration for QNAP users next month (July 2019), but can wait if it's not quite ready yet.

Thanks.

[sander]

IMHO stable enough for daily use by a developer. Not for every user. A traceback can still happen.

[OneCD]

Okiedoke, thanks @sander. I’ll wait a bit longer then.

[sander]

Okiedoke, thanks @sander. I’ll wait a bit longer then.

I was hoping you as a dev would start using it ...

[OneCD]

I'd hoped to start using it too... but I'm hardly a Python dev (haven't coded in Python for 2 to 3 years now), so I stick to 'stable' Python builds.

[safihre]

Maybe you could try to run it on your (QNAP) system and see what tracebacks you get? And then report those at Github?
That would be of great help!
Not yet as your daily-downloader, but just to see if you can get a few of your downloads to work as expected with your normal settings?

[OneCD]

Truth-be-told: I installed Debian on my production QNAP some time ago, so I don't actually use QNAP's OS myself on a daily basis.

I still maintain the sherpa script but have to develop and test it on my old backup NAS running QTS - which is only powered-up on the weekends for about an hour.

To test stability of the new SABnzbd properly on a QNAP, it needs to be installed on someone's production NAS running QTS.

[syth]

Where is the best place to check on progress on the py3 conversion? Is anyone working on updating the Synology package as well?

As for tracebacks, those happen in Sab current as well, so that is not a deal breaker, but now that py2.7 is EOLed, I don’t want to keep it installed on my NAS (it’s already been off my servers for awhile).

[OneCD]

Hey guys, just thinking out-loud here.

If I release a new and separate SABnzbd QPKG for QNAP NAS that runs on Python 3 (including notes that it's still in 'alpha' status), are you prepared for the increase in bug reports?

I'll always assist where I can, but Python stability testing is not something I'm in a position to carry-out.

So, this would give you a few more testers and might help get SABnzbd to 'stable' quicker.

Please advise.

[jcfp]

The py3 version works fine as a daily driver. Even the sabnzbdplus package in ubuntu 20.04 is based on a (pre alpha1) git snapshot, alpha2 is currently on the ppa (in turn used by 3rd party docker setups). None of that caused an avelanche of a bug reports either. Just go for it.

[safihre]

Yeah, go for it

[OneCD]

Okiedoke, I'll make a new package for this.

Thanks guys.

[OneCD]

Quick question: what will be the correct name and character-case for SAB running under Python 3?

Is it 'SABnzbd', 'SabNZBd', 'SABnzbd+', 'SABnzbdplus', 'SABnzbd3', 'SABnzbdplus3', etc...?

[safihre]

SABnzbd, like here on the website
Dunno where these other names came from long ago, I've also seen those in the wild

[OneCD]

Cool, then I’ll be able to name the new package correctly for the first time.