Is virtualenv actually using venv? When I create a new project it states in pyvenv.cfg command = /opt/homebrew/opt/python@3.13/bin/pytho… -m venv and I definitely don't have virtualenv installed on my system so whats actually going on here? Will it just then use venv by default unless I install virtualenv via pip globally on my system?
Yes, WIng is running Python with -m venv to set up a virtualenv. As far as I understand it 'virtualenv' was an older implementation that 'venv' replaces but people tend to still call them virtualenvs. It's confusing at best, and we should review the UI and docs to try to make this clearer, although I think most people don't think of the two as any different. The location where the venv is placed is specified on the second New Project dialog screen, and you should find it in there. By default if creating a new project directory the location is just in that directory.
All that said, I'd recommend using something like Poetry if you can. Actually even better 'uv' but support for that isn't in Wing 10 and will only be available when we get the first beta of Wing Pro 11 out, hopefully within a few weeks.
Does the annual license include upgrade from wing 10 pro to wing 11 pro?
Yeah uv is good, at the moment I just use venv for now as I learn python.
Yes, annual licenses work with all versions, including new ones once they are available.
Comments