I get the stacktrace below if I use any pip > 10

$ reqwire build -a
Traceback (most recent call last):
  File "/home/kevin/.local/bin/reqwire", line 7, in <module>
    from reqwire.cli import main
  File "/home/kevin/.local/lib/python3.7/site-packages/reqwire/cli.py", line 16, in <module>
    import reqwire.helpers.requirements
  File "/home/kevin/.local/lib/python3.7/site-packages/reqwire/helpers/requirements.py", line 15, in <module>
    import pip.basecommand
ModuleNotFoundError: No module named 'pip.basecommand'

Current workaround is to downgrade back to pip < 10, e.g.:

pip install -U "pip<10"

Reqwire version 0.2.1

Commit 0b86ba7 apparently introduced a bug with the add command, where if no other flags are provided, the provided specifier replaces all of the requirements in the targeted source file.

I have a very fuzzy recollection of why that configuration flag was introduced, and only exposed via the environment, and not documented. It certainly is not working as intended, so for now I'm just removing it altogether.

There is also a bug in requirements.resolve_specifier, in which it does not return a HashableInstallRequirement sometimes, resulting in the possibility of duplicate requirements being added.

I've stumbled upon an issue that causes reqwire to drop previously added dependencies to a requirement .in. Steps to reproduce:

bash-3.2$ mkdir test
bash-3.2$ cd test
bash-3.2$ reqwire init
created /Users/fmontag/test/requirements/src
created /Users/fmontag/test/requirements/lck
created /Users/fmontag/test/requirements/src/docs.in
created /Users/fmontag/test/requirements/src/main.in
created /Users/fmontag/test/requirements/src/qa.in
created /Users/fmontag/test/requirements/src/test.in
bash-3.2$ reqwire add sqlalchemy
Collecting sqlalchemy
Installing collected packages: sqlalchemy
Successfully installed sqlalchemy-1.1.5
saving requirement(s) to main
bash-3.2$ cat requirements/src/main.in
# -*- mode: requirementstxt -*-
# vim: set ft=requirements
# Generated by reqwire on Sun Feb 26 20:12:35 2017
--index-url https://pypi.python.org/simple
SQLAlchemy==1.1.5

Ok, at this point let's add another dependency to main.in:

bash-3.2$ reqwire add sqlalchemy-utils
Collecting sqlalchemy-utils
Requirement already satisfied: six in /Users/fmontag/venv/lib/python3.6/site-packages (from sqlalchemy-utils)
Requirement already satisfied: SQLAlchemy>=1.0 in /Users/fmontag/venv/lib/python3.6/site-packages (from sqlalchemy-utils)
Installing collected packages: sqlalchemy-utils
Successfully installed sqlalchemy-utils-0.32.12
saving requirement(s) to main
bash-3.2$ cat requirements/src/main.in
# -*- mode: requirementstxt -*-
# vim: set ft=requirements
# Generated by reqwire on Sun Feb 26 20:13:03 2017
--index-url https://pypi.python.org/simple
SQLAlchemy-Utils==0.32.12

The first one just vanishes, adding a second dependency drops the first. Maybe it is just because sqlalchemy-utils pulls in sqlalchemy as a dependency but both of them are top level dependencies for my project so I was expecting to have both of them pinned in main.in.

Hi,
I'm interested to add editable dependencies like this:

-e git+https://github.com/darvid/reqwire.git@5b455cdca4e919041dfdf448c329eb206329b5e3#egg=reqwire

Is there is a way to achieve this ?

knowing that --pin is not documented maybe this option is deprecated ?

Using build as the build directory name is less than ideal because most standard .gitignore files ignore it.

Open to suggestions. Some possibilities:

• built
• resolved
• full
• _build (and use _src for src?)
• all

Because reqwire uses pip.req.parse_requirements, requirements from nested requirement files are flattened out when source files get updated with reqwire add. These lines need to be preserved in source files, and the nested requirements need to be excluded from the resulting resolved requirements. Unsure what degree of validation should be done to avoid conflicts between added requirements (and their dependencies) and requirements from nested files.

If qa.in depends on main.in and you update or add a package in main.in, it would be handy to be prompted to also build any downstream tags that have main.in as nested includes. And an option to automatically do it, as well.