euler-py: vendor deps

[iMichka]

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

[timsutton]

Is setuptools still required as an explicit resource? Asking because my understanding is that pip will attempt to download it if it's unavailable.

Wondering if (in general) setuptools makes sense to be included as an explicit resource if it is for some reason a runtime dependency?

[cho-m]

Is setuptools still required as an explicit resource? Asking because my understanding is that pip will attempt to download it if it's unavailable.

euler-py is too old (2019-12-13) that it is still using deprecated setup.py which assumes that setuptools/distutils is bundled with Python (no longer the case with 3.12).

In order for build-time setuptools to be automatically installed, projects usually need to use pyproject.toml instead and have:

[build-system]
requires = ["setuptools"]

---

Wondering if (in general) setuptools makes sense to be included as an explicit resource if it is for some reason a runtime dependency?

Usually, we want to only have runtime dependencies in resource list (i.e. the packages that show up when running brew update-python-resources <formula>).

However, setuptools is a bit of an odd one given it used to be bundled in Python 3.11 and older. So, a lot of Python packages assume it exists.

[branchvincent]

I've been forcing pip to behave as if there was a pyproject.toml with --use-pep517 (which will eventually become the default), e.g.

ENV["PIP_USE_PEP517"] = "1"

[github-actions]

🤖 An automated task has requested bottles to be published to this PR.