title: Maintain one requirements.txt for a semi-private Python project with editable dependencies
body: <p>I have a Python package (A) that depends on another package (B). I am developing them locally at the same time. My <code>requirements.txt</code> for A looks like:</p>
  
  <pre><code>--editable /path/to/B
  --editable .
  </code></pre>
  
  <p>I will be sharing both packages with others, but not listing them on PyPI. When I distribute A, users will need to obtain the dependency B. I can specify where to get B in a <code>requirements.txt</code>:</p>
  
  <pre><code>git+https://github.com/smackesey/B#egg=B
  .
  </code></pre>
  
  <p>But this <code>requirements.txt</code> is different than the one I use locally. Is it possible to maintain one requirements.txt that satisfies both needs?</p>