<div dir="ltr"><div>I have not seen the benefit of using (or being forced to use) setup.py for this or many projects: as you said, requirements.txt contains the freeze of the deployment configuration, which as a deployed application not a library is all that is needed?<br></div><div><br>If tox supports "merging" dependencies from setup.py & depends, and tox has added support for requirements.txt, then it would make sense for them to be some way to use both ways?<br><br></div><div>I simply want to use tox to be able to easily test the project against multiple versions of dependencies, and avoid having to keep multiple places up to date, or having to create n number of files where n is the number of dependencies that can change :)<br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><br>Best regards,<br>Antony</div></div>
<br><div class="gmail_quote">On 16 June 2015 at 14:04, Robert Collins <span dir="ltr"><<a href="mailto:robertc@robertcollins.net" target="_blank">robertc@robertcollins.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 16 June 2015 at 23:19, Antony Seedhouse <<a href="mailto:antony.seedhouse@gmail.com">antony.seedhouse@gmail.com</a>> wrote:<br>
> Is there a way to "merge" tox deps with requirements.txt, without having to<br>
> split requirements.txt into multiple files (one per dep specified in<br>
> tox.ini) or other more complicated methods?<br>
><br>
> For example, I have a project with all current dependencies in<br>
> requirements.txt, and would like to test it with multiple versions of django<br>
<br>
</span>Why do you have your dependencies in requirements.txt?<br>
requirements.txt should be a freeze of the exact deployment<br>
configuration....<br>
<span class=""><br>
> I would like my deps = to look like:<br>
><br>
> deps =<br>
> -r../requirements.txt<br>
> django17: Django>=1.7,<1.8<br>
> django18: Django>=1.8,<1.9<br>
><br>
> This would tell tox to overwrite the Django version in requirements.txt with<br>
> the environment specified version<br>
><br>
> Currently this errors: Double requirement given: Django==1.7.7 (from -r<br>
> ../requirements.txt (line 3)) (already in Django<1.8,>=1.7, name='Django')<br>
<br>
</span>Yes, this is expected. I would have your dependencies be in your<br>
setup.py, and use the tox syntax to select specific versions for<br>
testing as you are trying to here.<br>
<br>
-Rob<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
--<br>
Robert Collins <<a href="mailto:rbtcollins@hp.com">rbtcollins@hp.com</a>><br>
Distinguished Technologist<br>
HP Converged Cloud<br>
</font></span></blockquote></div><br></div>