pyenv-win VS pytest

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

In this blog post I want to demonstrate how my lab equipment such as a lab power supply or a digital multimeter (DMM) have been integrated into some pytest-based tests. Would love to get your feedback and thoughts! 🚀

Pytest: is a third-party testing framework that supports fixtures, parameterized testing, and easy test discovery while having room to add plugins to extend its functionality.

Next, you need to install a testing framework that will be used for performing unit testing in your project. Several testing frameworks are available depending on the programming language used to create an application. For example, JUnit is commonly used for Java apps, pytest for Python apps, NUnit for .NET apps, Jest for JavaScript apps, and so on. We’ll use the Jest framework for this tutorial since we are using JavaScript.

Yea, read through the pytest docs.

I absolutely agree about fixtures-as-arguments thing. Ward does this a lot better, using default values for the fixture factory. There's a long issue on ideas to implement something like that as a pytest plugin (https://github.com/pytest-dev/pytest/issues/3834), but it seems the resulting plugin relies on something of a hack.

I recommend writing a few tests. py.test makes that quite simple:

Since ITK's inception in 1999, there has been a focus on engineering practices that result in high-quality software. High-quality scientific software is driven by regression testing. The ITK project supported the development of CTest and CDash unit testing and software quality dashboard tools for use with the CMake build system. In the Python programming language, the pytest test driver helps developers write small, readable scripts that ensure their software will continue to work as expected. However, pytest can only test Python scripts by default, and errors in untested computational notebooks are more common than well-tested Python code.