Visual studio: Python virtual environments in version control

I managed to successfully create a Visual Studio Python project. Now I want to share this project with other developers through source control (the company I work with uses SVN ).

How I want each of my colleagues not to manually configure the same Python environment, I studied the use of a virtual environment . In my head, this seems very similar to how NPMs are stored locally.

Without any hassle, I managed to set up a virtual environment that works brilliantly.

However, I was ready to exclude my Virtual Environment folder from SVN when I noticed that the “pyproj” file contains a link to my local virtual environment:

<ItemGroup>
  <Interpreter Include="VirtualEnvironment\">
  <Id>VirtualEnvironment</Id>
  <Version>3.6</Version>
  <Description>VirtualEnvironment (Python 3.6 (64-bit))</Description>
  <InterpreterPath>Scripts\python.exe</InterpreterPath>
  <WindowsInterpreterPath>Scripts\pythonw.exe</WindowsInterpreterPath>
  <PathEnvironmentVariable>PYTHONPATH</PathEnvironmentVariable>
  <Architecture>X64</Architecture>
</Interpreter>

" " Visual Studio, "requirements.txt" ( ). " " .

, - .

  • ?
  • , , ?

:

+4
2

MicrosoftDocs GitHub, zooba:

, , . VS VS Code.

Visual Studio: Python , . requirements.txt , , ( , , , , ).

, :

  • "" (env )
  • requirements.txt
  • " " ( ), "" , )

, , . (, , python -m venv path\to\env), , .

, "-" , , .

+3

IMHO: - .txt , python env. readme.txt.

- request.txt readme.

+1

Source: https://habr.com/ru/post/1694269/


All Articles