blocks|key|184401|text|您可以级联您的需求文件，并使用"-r“标志告诉pip将一个文件的内容包含在另一个文件中。您可以将需求分解为模块化的文件夹层次结构，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|184402|`--+django_project_root
%7C--+requirements
%7C+++%7C--+common.txt
%7C+++%7C--+dev.txt
%7C+++`--+prod.txt
`--+requirements.txt|code-block|syntax|javascript|184403|文件的内容将如下所示：|184404|common.txt：|184405|#+Contains+requirements+common+to+all+environments
req1==1.0
req2==1.0
req3==1.0
...|184406|dev.txt：|184407|#+Specifies+only+dev-specific+requirements
#+But+imports+the+common+ones+too
-r+common.txt
dev_req==1.0
...|184408|prod.txt：|184409|#+Same+for+prod...
-r+common.txt
prod_req==1.0
...|184410|在Heroku之外，您现在可以像这样设置环境：|184411|pip+install+-r+requirements/dev.txt|184412|或|184413|pip+install+-r+requirements/prod.txt|184414|由于Heroku专门在项目根中查找"requirements.txt“，它应该只镜像prod，如下所示：|184415|requirements.txt：|184416|#+Mirrors+prod
-r+requirements/prod.txt|184417|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1B|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1C|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1D|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|1E|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|1F|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|1G|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|1H|8|@]|9|@]|A|$]]|$1|S|3|T|5|D|7|1I|8|@]|9|@]|A|$E|F]]|$1|U|3|V|5|6|7|1J|8|@]|9|@]|A|$]]|$1|W|3|X|5|D|7|1K|8|@]|9|@]|A|$E|F]]|$1|Y|3|Z|5|6|7|1L|8|@]|9|@]|A|$]]|$1|10|3|11|5|D|7|1M|8|@]|9|@]|A|$E|F]]|$1|12|3|13|5|6|7|1N|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|1O|8|@]|9|@]|A|$]]|$1|16|3|17|5|D|7|1P|8|@]|9|@]|A|$E|F]]|$1|18|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|19|$]]

You can cascade your requirements files and use the "-r" flag to tell pip to include the contents of one file inside another. You can break out your requirements into a modular folder hierarchy like this:

<pre><code>`-- django_project_root
|-- requirements
| |-- common.txt
| |-- dev.txt
| `-- prod.txt
`-- requirements.txt
</code></pre>

The files' contents would look like this:

common.txt:

<pre><code># Contains requirements common to all environments
req1==1.0
req2==1.0
req3==1.0
...
</code></pre>

dev.txt:

<pre><code># Specifies only dev-specific requirements
# But imports the common ones too
-r common.txt
dev_req==1.0
...
</code></pre>

prod.txt:

<pre><code># Same for prod...
-r common.txt
prod_req==1.0
...
</code></pre>

Outside of Heroku, you can now setup environments like this:

<pre><code>pip install -r requirements/dev.txt
</code></pre>

or

<pre><code>pip install -r requirements/prod.txt
</code></pre>

Since Heroku looks specifically for "requirements.txt" at the project root, it should just mirror prod, like this:

requirements.txt:

<pre><code># Mirrors prod
-r requirements/prod.txt
</code></pre>

blocks|key|2795023|text|现在一个可行的选择是使用pipenv而不是pip来管理依赖关系，这在最初的问题和答案发布时还不存在。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2795024|使用pipenv，不再需要像pip那样手动管理两个独立的需求文件，而是通过命令行上的交互来管理开发和生产包本身。|2795025|要安装在生产和开发中使用的软件包，请执行以下操作：|2795026|pipenv+install+<package>|code-block|syntax|javascript|2795027|要仅为开发环境安装软件包，请执行以下操作：|2795028|pipenv+install+<package>+--dev|2795029|通过这些命令，pipenv在两个文件(Pipfile和Pipfile.lock)中存储和管理环境配置。Heroku当前的Python+buildpack本机支持pipenv，并且如果Pipfile.lock而不是requirements.txt存在的话，它将从Python进行自我配置。|2795030|有关该工具的完整文档，请参阅pipenv链接。|2795031|entityMap|0|LINK|mutability|MUTABLE|url|https://pipenv.readthedocs.io/en/latest/^0|C|6|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@$A|13|B|14|1|15]]|C|$]]|$1|D|3|E|5|6|7|16|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|17|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|18|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|19|8|@]|9|@]|C|$]]|$1|O|3|P|5|J|7|1A|8|@]|9|@]|C|$K|L]]|$1|Q|3|R|5|6|7|1B|8|@]|9|@]|C|$]]|$1|S|3|T|5|6|7|1C|8|@]|9|@]|C|$]]|$1|U|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]]|V|$W|$5|X|Y|Z|C|$10|11]]]]

A viable option today which didn't exist when the original question and answer was posted is to use <a href="https://pipenv.readthedocs.io/en/latest/" rel="noreferrer">pipenv</a> instead of pip to manage dependencies.

With pipenv, manually managing two separate requirement files like with pip is no longer necessary, and instead pipenv manages the development and production packages itself via interactions on the command line.

To install a package for use in both production and development:

<pre><code>pipenv install &lt;package&gt;
</code></pre>

To install a package for the development environment only:

<pre><code>pipenv install &lt;package&gt; --dev
</code></pre>

Via those commands, pipenv stores and manages the environment configuration in two files (Pipfile and Pipfile.lock). Heroku's current Python buildpack natively supports pipenv and will configure itself from Pipfile.lock if it exists instead of requirements.txt.

See the pipenv link for full documentation of the tool.

blocks|key|3007625|text|如果您的需求是能够在同一台计算机上的环境之间进行切换，则可能需要为您需要切换到的每个环境创建不同的virtualenv文件夹。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3007626|python3+-m+venv+venv_dev
source+venv_dev/bin/activate
pip+install+-r+pip/common.txt
pip+install+-r+pip/dev.txt
exit
python3+-m+venv+venv_prod
source+venv_prod/bin/activate
pip+install+-r+pip/common.txt
exit
source+venv_dev/bin/activate
#+now+we+are+in+dev+environment+so+your+code+editor+and+build+systems+will+work.

#+let's+install+a+new+dev+package:
#+pip+install+awesome
#+pip+freeze+-r+pip/temp.txt
#+find+that+package,+put+it+into+pip/dev.txt
#+rm+pip/temp.txt

#+pretty+cumbersome,+but+it+works.+|code-block|syntax|javascript|3007627|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

If your requirement is to be able to switch between environments on the same machine, it may be necessary to create different virtualenv folders for each environment you need to switch to. 

<pre><code>python3 -m venv venv_dev
source venv_dev/bin/activate
pip install -r pip/common.txt
pip install -r pip/dev.txt
exit
python3 -m venv venv_prod
source venv_prod/bin/activate
pip install -r pip/common.txt
exit
source venv_dev/bin/activate
# now we are in dev environment so your code editor and build systems will work.

# let's install a new dev package:
# pip install awesome
# pip freeze -r pip/temp.txt
# find that package, put it into pip/dev.txt
# rm pip/temp.txt

# pretty cumbersome, but it works. 
</code></pre>

I have two branches, Development and Production. Each has dependencies, some of which are different. Development points to dependencies that are themselves in development. Likewise for Production. I need to deploy to Heroku which expects each branch's dependencies in a single file called 'requirements.txt'.

What is the best way to organize?

What I've thought of:

<ul>
<li>Maintain separate requirements files, one in each branch (must survive frequent merges!)</li>
<li>Tell Heroku which requirements file I want to use (environment variable?)</li>
<li>Write deploy scripts (create temp branch, modify requirements file, commit, deploy, delete temp branch)</li>
</ul>

How to customize a requirements.txt for multiple environments?

Python

我有两个分支，开发和生产。每一个都有依赖关系，其中一些是不同的。开发指向自身处于开发中的依赖项。生产也是如此。我需要部署到Heroku，它希望每个分支的依赖项都放在一个名为‘quirements.txt’的文件中。最好的组织方式是什么？我想到的是：维护单独的需求文件，每个分支中都有一个(必须经受住频繁的合并！)告诉He...

问如何为多个环境自定义一个requirements.txt？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何为多个环境自定义一个requirements.txt？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何为多个环境自定义一个requirements.txt？
EN