> On Dec 9, 2024, at 11:15 PM, Jacob Kruger <ja...@blindza.co.za> wrote:
>
> Might not be relevant, if am misunderstanding something, but I generally just
> use pip freeze > requirements.txt, shift that text file over to new
> location/machine, create new virtual environment, and run pip install -r
> requirements.txt from there to recreate environment, and, I do this across
> different operating systems as well?
If that works for you, then yeah, that's a good way to go. The usual reason
that this would not work would be if you have some native dependency with a
build requirement and no binary build for your target platform, and some
machines without C (or Rust, or FORTRAN, or whatever) compilers, which is
particularly common on Windows. But the right way to deal with that would be
`pip wheel` and copying over the wheels directory with the requirements.txt,
then pip install --no-index -f wheels/ --Ur requirements.txt, not copying the
virtualenv.
_______________________________________________
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32
