Randy Döring

To summarize: * #142 made `sdist` builds repoducible in the sense of "building twice in a row on the same machine". It did not make `sdist` builds reproducible if you...

> Is there an update with this issue? Nothing except for comments in this issue afaik. > If someone makes a PR, would this get merged in? It depends on...

OK, the reason is simple: https://github.com/CATIA-Systems/FMPy/blob/1d74126039d6ae861df86110b423c068d5085b7d/azure-pipelines.yml#L220-L226 It's just the `RECORD` file from a Windows wheel. Instead of zipping the merged directory, running `wheel pack` should do.

Are you looking for something like [this](https://python-poetry.org/docs/contributing#local-development)?

@KotlinIsland Are you still interested in this PR? If so, please rebase it on the current main branch. Then, I'll take a closer look. Otherwise, there's now a (partial) duplicate...

Superseded by #241 and #294

> So the export fails when there's 2 different versions of `urllib3`, but both versions are placed into the lockfile by Poetry's dependency resolution. Is that valid/intended? Is that a...

> I'm curious to hear how poetry-plugin-export's output would differ from this (if it were working). Your approach creates a `requirements.txt` that's suitable for your current environment (Python version, platform,...

> How would you recommend we solve this within the export plugin? Create a test case (probably in `test_exporter.py`), try to debug and fix it. (As far as I know,...

> Having said all that... why can poetry export not write out [environment markers](https://stackoverflow.com/a/33451105/453851)? Would that not allow exporting all permutations in one requirements.txt? That's exactly what poetry-plugin-export is doing....