beardypig/streamlink-portable

Latest Nightly build release failed...

Vangelis66 opened this issue · 10 comments

Vangelis66 commented

Happy New Year @beardypig 😄

I am watching the Nightly portable build releases since a while ago and
just became aware that the usual, daily, GitHub e-mail titled
[beardypig/streamlink-portable] Pre-release latest - Nightly Build
from github-actions[bot] is AWOL... 😞
That would've been announcing the availability of
streamlink-portable-2.0.0+16.g7b74974-py3.6.5-win32.zip

I browsed the Actions tab and regrettably saw that the build creation has failed:

SL-Nightly_fail

Perhaps recent repo activity has somehow broken things?
These portable builds of yours are highly appreciated 👍 , as the other portable streamlink package has been sadly abandoned 😭 ...

While I'm at it, would you mind if I asked some related questions?

  1. PSF has 3.6.8-win32 binaries available, can these be used instead of 3.6.5?
  2. Would it be hard to move to latest py3.7 (3.7.9 to be exact)?
  3. What is the underlying reason some modules are "frozen" at older versions (e.g. pycryptodome-3.4.3 used, latest being 3.9.9)?

Many thanks, my heartfelt wishes for 2021, stay healthy and safe wherever you happen to be...

beardypig commented

Yes, it broke. I noticed it broke and took a look, but I didn't see a way to fix it quickly. I planned to look at it tomorrow.

Updating to 3.7.9 is easy and I will do it.

The versions were frozen at the time when I made it to maintain compatibility pre-2.0.0, they could be updated now to match the current versions used by streamlink 2.0.0.

  • 👍1
beardypig commented

I have updated the Python version and the dependencies, I just need to fix that pesky nightly build issue.

  • 👍1
  • 😄1
beardypig commented

For some reason the merge commit was making the auto-release fail.

Vangelis66 commented

I'm sorry to spoil it again for you, ... but the archive's filename still mentions Python 3.6.5 :

NR

Vangelis66 commented

... And does still contain Python 3.6.5 in its guts:

py365

I think I have opened a can of worms... 😞

beardypig commented

Actually for real will be 3.7.9, forgot it set the Python version in the action workflow too...

Vangelis66 commented

Thanks... at long last! 🎉
Apologies I made you work overtime/overnight... 😃

One last thing:
__pycache__ folders inside the new py3.7.9 archive (./streamlink/packages/*) still contain compiled files (*.pyc) from py3.6.5, also some other remnant files reference py3.6, should these be removed or will cause no harm?

P1 P2

beardypig commented

That's weird, maybe from caching on github... they shouldn't do any harm though and will probably disappear in a couple of days worth of nightly builds anyway.

  • 😄1
Vangelis66 commented

__pycache__ folders inside the new py3.7.9 archive (./streamlink/packages/*) still contain compiled files (*.pyc) from py3.6.5, also some other remnant files reference py3.6,

I see now this was, most probably, addressed by 612b929 👍
Thanks for your perseverance! 😄

beardypig commented

yeah it probably was that :)

  • 😄1