Micha Reiser

The main issue here is that `uv` assumes that Python is located at `$VIRTUAL_ENV/Scripts/python.exe` which isn't the case when pointing to a global python installation. see https://github.com/astral-sh/uv/pull/1803 for some details....

We're planning to solve this as part of https://github.com/astral-sh/uv/issues/1526 The recommended local workflow is to use a venv instead of installing dependencies globally.

> However in our setup, python is v2.7.14, while python3 is v3.10.5, so maybe python2 is actually called by uv? uv calls python 2 to get its version information. But...

I would expect that a server only sends an HTTP Timeout response if the connection is idle for too long, which makes me wonder if increasing the timeout solves the...

It's a difficult one. Making it visible to users could motivate artifactory to add support for it but showing it on every invocation sounds annoying. I wonder if there are...

I haven't used rye myself but I wonder if this is the suggested workflow. I think the proposed way of using `uv` with `rye` is to use `uv` through `rye`....

Possibly related to https://github.com/astral-sh/uv/issues/1795

Would you mind sharing the `C:\Users\username\Desktop\uvtest\uvenv\Scripts\pyinstaller.exe` file? I would like to look at open it in a HEX editor to inspect its content (we generate the exe dynamically and I...

Thanks. I'm not sure what's going wrong here. Running the above commands works successfully on my windows machine. I can even use your `pyinstaller.exe` and run it after patching the...

Okay that's interesting. I can reproduce with Python 3.7.9. Python 3.8.10 works fine. I quickly glanced over the Python 3.8 changelog to see if I can spot any changes to...