Do I have my environment correct?

[MrGibbage]

I use the uv package manager and virtual environment manager. I am new to it, so it wouldn't surprise me if I don't have it set up quite correctly. Today I looked at my uv.lock file, and I have a bunch of packages in there that I have no idea why they are there. It is my understanding that uv uses this file to make sure that if I create a virtual environment on a different computer, it will be set up exactly the same as this one. That is very important because I will use it for each of the team members' laptops, to make sure they are correctly set up. In my case though, I have all of the following packages. My assumption is that this is all a part of pybricks, in which case it is fine. But a lot of the pacakges are ones that I have used on other projects, so I wonder if I have somehow polluted this one with remnants from other projects?

Here's the package list from my uv.lock:

aioserial
appdirs
argcomplete
asyncssh
bleak
cffi
colorama
cryptography
dbus-fast
fll-fall-2025-unearthed # This is my current project
hidapi
mpy-cross-v5
mpy-cross-v6
packaging
prompt-toolkit
pybricks # This I recognize
pybricksdev # and this I recognize
pycparser
pyobjc-core
pyobjc-framework-cocoa
pyobjc-framework-corebluetooth
pyobjc-framework-libdispatch
pyserial
pyusb
reactivex
semver
setuptools
tqdm
typing-extensions
wcwidth
winrt-runtime
winrt-windows-devices-bluetooth
winrt-windows-devices-bluetooth-advertisement
winrt-windows-devices-bluetooth-genericattributeprofile
winrt-windows-devices-enumeration
winrt-windows-foundation
winrt-windows-foundation-collections
winrt-windows-storage-streams

By the way, the only packages I install in my current project are pybricks and pybricksdev. Should I be importing anything else?

[dlech]

These all look like depedencies of pybricksdev, so all looks OK.

There is a bug with the mpy-cross-v{5,6} v1.1.0 packages on Windows that I am currently working on. So if you have that version of those packages, you should downgrade them for now (i.e. put !=1.1.0 in your version spec for those 2 packages).

[MrGibbage]

Whew! Thanks :)