Wim Jeantine-Glenn

Yeah, this is out of scope. `parse` currently is totally agnostic about any filesystem, it just works with strings. For a glob replacement which uses parse instead of wildmatch, recommend...

Not reproducible.

The "fixed" results are already iterable as a side-effect of `parse.Result` being indexable (i.e. implementing `__getitem__`). I don't think any Pythonic API is possible to combine the tuple of `result.fixed`...

More sensible default behavior would be desirable here. This bit me too, I don't keep a .gitignore in the sourcetree unless it's excluding stuff generated specifically by that project. Excludes...

@hynek Thank you for that, really nice. Just tried it out and found a couple of interesting things: it [didn't work on a windows runner](https://github.com/pytest-dev/pytest-freezer/actions/runs/5330395183/jobs/9657030876) (meh?), and the PKG-INFO inside...

@ofek There is nothing wrong with that explicit configuration: when using `[tool.hatch.build.targets.sdist]` it does the correct thing. My complaint was that the default configuration is not clever enough to know...

> If one of you does fork it please let me know, we would definitely consider switching to an import sorter that had the same sort of considered opination that...

You are right. I get: Error: Command '['/path/to/testenv/bin/python3', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 127.

Thanks for the info. For what it's worth, I would totally expect having to reinstall poetry if upgrading system interpreter.

This also tripped me up - providing headers in a request blew away the User-Agent which was setup globally on the pool manager. A possible proposal is: pm.request('POST', 'https://foo.bar', headers=pm.headers...