IDG SERPRO

We can't have contributor's agreement signed yet so we can't try to add a PR. :( But thanks for answering.

This is indeed nice but I don't think it addresses the main point of this issue. In pip freeze's documentation, we have: > Output installed packages in requirements format. And...

Related: https://github.com/buildout/buildout/issues/287

@enkidulan I've come to a similar conclusion in https://github.com/buildout/buildout/issues/479#issuecomment-494812645, but since we have https://github.com/buildout/buildout/issues/287 still opened, I think this issue is still relevant. Thanks for the suggestion though, people searching...

@janwijbrand this is the same as #238? It would be great! We had trouble with this: https://github.com/Julian/jsonschema/issues/453#issuecomment-413936081 @jonathanultis FYI

Indeed, I just came by this situation. I was using buildout annotate for some pinned versions like it's said in a related issue https://github.com/buildout/buildout/issues/320. But I realized that in a...

If you're planning to have both `requirements.txt` and `constraints.txt` and the motivation is to override the `[versions]` section, wouldn't a name like `buildout.versions` or even `buildout.versionpins` be more appropriate? >...

>See also my comment #244 (comment) @reinout as stated in the [setuptools documentation](https://setuptools.readthedocs.io/en/latest/setuptools.html#new-and-changed-setup-keywords), ```setup_requires``` isn't the dependency on the package that declares it but rather the dependency on the installation...

@jimfulton @leorochael @reinout

We have a small addition we think could be useful in https://github.com/buildout/buildout/blob/master/bootstrap/bootstrap.py. We work with Plone, but for legal reasons we can't sign the contributor's agreement. That's why we're asking...