Drop pyproject.toml

[lovelydinosaur]

Personally I'm not keen on us having a pyproject.toml exclusively for some bits of black configuration. We don't have this on our other projects, and I don't particularly appreciate IDE design choices forcing us into particular tooling conventions.

I'm okay with us having a conversation around this, but also am very strongly in favour of us being able to stick with similar conventions on our projects across encode, and striving towards low-config, low-tooling approaches wherever possible. To me this also include narrowing down the number of magical configuration files we have at the top-level.

Also, I needed a PR excuse to have a look at the latest build failure nonsense.

[lovelydinosaur]

I don't understand black's behaviour here.

Eg...

+ venv/bin/black --force-exclude 'httpcore/_sync/.*' --force-exclude 'tests/sync_tests/.*' --check --diff --target-version=py36 httpcore tests
would reformat httpcore/_sync/http11.py

But, I just asked you not to include that file?

[lovelydinosaur]

Okay got it, --exclude (and --force-exclude) only accept a single argument, so the flag is being silently overwritten.

[lovelydinosaur]

Okay, so presumably the SSL errors are something to do with the very latest python releases having some newer SSL config.

[florimondmanca]

Okay, so presumably the SSL errors are something to do with the very latest python releases having some newer SSL config.

Yup, tracked this under #276 — we've got a test that needs updating to unblock CI.

[florimondmanca]

Referencing #156 and #156 which is where we moved to this pyproject.toml file. We used to not have it before, right. :-)