xstream VS pyenv-win

I hope we don't end up with the same things as the java world. JDK9 removed and moved to a library a few things like JAXB. Since JDK11, every new version is harsher for programs that use reflection to mess with non-published internals. Both are good changes, BTW.

In theory, you add a few libs and you're ready to upgrade. In practice, adding libs at scale is hard, and quite a few dependencies of dependencies of ... are using reflection to mess with internals.

As a result, there are still a lot of enterprise applications on JDK8 and JDK11, even if the security impact of this is bad and the fix should be easy.

For a typical example: see https://github.com/x-stream/xstream/issues/101

Run the below command in the powershell, if you find this blog post to be too old, please follow the steps in the official repository of pyenv-win.

Looks like it’s an open issue with pyenv-win https://github.com/pyenv-win/pyenv-win/issues/469

What made this weird was the inconsistency between *NIX and Windows systems. On Windows the Python Launcher is used. This allows you to switch between different Python versions which are registered in the Windows Registry via PEP514 logic. Unfortunately, one of the popular implementations, PyPy, didn't have great support for it. On *NIX systems pyenv made this easy, while on Windows pyenv-win exists but it's currently not able to pull the PyPy mirrors. I wanted a more simplistic way to integrate PyPy into Windows for easy Python Launcher integration. So I started to do something really crazy: write Powershell.

We then use pyenv which is a command line tool used to manage multiple versions of Python. This is useful if you are working on multiple projects that use different versions of Python. Check out the GitHub readme of the 'pyenv' project for more information on how to install it on your operating system. For windows check out pyenv-win or you can use venv Python's Built-in Virtual Environment.

I have tried my best to research this issue and have not come up with much. It is obvious that its a backend issue right? The guides that I used https://github.com/bmaltais/kohya_ss and https://github.com/pyenv-win/pyenv-win/

IMO I prefer pyenv. There is a pywinenv https://github.com/pyenv-win/pyenv-win. Lets you set up multiple python installs with less probability of screwing then up

The problem seemed to be that powershell won't run scripts by default. https://github.com/pyenv-win/pyenv-win/issues/289 This person had the same issue as me when installing pyenv. After fixing the execution policy the windows installer ran fine. However when I run anki it crashes after a few seconds.

I've had success using pyenv on Mac and Linux. If I had to use Windows, I'd probably try pyenv-win [0].

I have run into issues trying to use packages that were available for one platform but not another, due to native code, etc. Most of the time I could find a pure Python alternative, but not always. This can lead to using containers, which adds complexity, which is a drawback because one of the advantages of Python to me is the simplicity (assuming you have something like pyenv).

I've used Poetry in the past, but it added enough complexity/overhead that I probably won't again.

I've had some success putting a line in a README for an internal tool that other devs can use to pip install from a Git repo. Again, assuming you have pyenv or the like, starting from a clean venv and pip install from Git seems to be pretty straightforward.

[0] - https://github.com/pyenv-win/pyenv-win

Or https://github.com/pyenv-win/pyenv-win