-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pull out high-level interfaces as an extended example #83
Conversation
Suggestion: move it into examples/*, to clearly denote that it's an example and make room for us to add additional things/examples/demos if we want to in the future. |
OK, I've moved it into an |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great to me! ^.^
Thanks @pradyunsg :-) |
How do we plan to manage the rollout of this change? There's probably a fair number of folks using this as a CLI tool. |
I'd probably wait until a new python-build release/python-build gets into PyPA, so that we can recommend that as an alternative. |
@FFY00 any ETA on that? anything to help with that? |
I need to fix some simple issues and probably improve the test suite a bit. I don't think it should take too long. |
Am I correct in understanding that this removes I guess I should have taken more seriously the warnings that it wasn't necessarily ready for production use, but given that this was the only PEP 517 build front-end for several years, I would kind of expect it to keep working at least for a while. I'll now have to run around and pin the versions on a bunch of my projects now. If the justification is "we'll get a release of |
The high level CLI will evidently be removed soon (and suddenly): pypa/pyproject-hooks#83
pep517 will apparently soon drop the pep517.build CLI, suddenly. No replacement is available, so we will pin to the latest version that supports it. pypa/pyproject-hooks#83
pep517.build is deprecated see: pypa/pyproject-hooks#83
This was intended as a proof of concept; build seems to be the correct replacement. See pypa/pyproject-hooks#83
This was intended as a proof of concept; build seems to be the correct replacement. See pypa/pyproject-hooks#83
* Migrate from the deprecated pep517.build to python-build CLI for builds for packaging - c.f. pypa/pyproject-hooks#83 * Remove check stage as done implicitly with python-build - c.f. https://github.com/FFY00/python-build/issues/105
* Migrate from the deprecated pep517.build to python-build CLI for builds for packaging - c.f. pypa/pyproject-hooks#83 * Remove check stage as done implicitly with python-build - c.f. https://github.com/FFY00/python-build/issues/105
This was intended as a proof of concept; build seems to be the correct replacement. See pypa/pyproject-hooks#83
This was intended as a proof of concept; build seems to be the correct replacement. See pypa/pyproject-hooks#83
* feat: setup.py redesign and helpers * refactor: simpler design with two outputs * refactor: helper file update and Windows support * fix: review points from @YannickJadoul * refactor: fixes to naming and more docs * feat: more customization points * feat: add entry point pybind11-config * refactor: Try Extension-focused method * refactor: rename alt/inplace to global * fix: allow usage with git modules, better docs * feat: global as an extra (@YannickJadoul's suggestion) * feat: single version location * fix: remove the requirement that setuptools must be imported first * fix: some review points from @wjacob * fix: use .in, add procedure to docs * refactor: avoid monkeypatch copy * docs: minor typos corrected * fix: minor points from @YannickJadoul * fix: typo on Windows C++ mode * fix: MSVC 15 update 3+ have c++14 flag See <https://docs.microsoft.com/en-us/cpp/build/reference/std-specify-language-standard-version?view=vs-2019> * docs: discuss making SDists by hand * ci: use pep517.build instead of manual setup.py * refactor: more comments from @YannickJadoul * docs: updates from @ktbarrett * fix: change to newly recommended tool instead of pep517.build This was intended as a proof of concept; build seems to be the correct replacement. See pypa/pyproject-hooks#83 * docs: updates from @wjakob * refactor: dual version locations * docs: typo spotted by @wjakob
* Migrate from the deprecated pep517.build to python-build CLI for builds for packaging - c.f. pypa/pyproject-hooks#83 * Remove check stage as done implicitly with python-build
* Migrate from the deprecated pep517.build to python-build CLI for builds for packaging - c.f. pypa/pyproject-hooks#83
pep517.build is going to be deprecated: pypa/pyproject-hooks#83 So let's use a tool that explicitly has an interface we can use to build.
This is necessary because `pep517` is going to drop its experimental CLIs eventually and the PyPA recomments using a new tool called `build` instead. `pypa/build` is a CLI built around the APIs provided by the `pep517` library. Refs: * pypa/pyproject-hooks#83 * pypa/pyproject-hooks#91
This is necessary because `pep517` is going to drop its experimental CLIs eventually and the PyPA recomments using a new tool called `build` instead. `pypa/build` is a CLI built around the APIs provided by the `pep517` library. Refs: * pypa/pyproject-hooks#83 * pypa/pyproject-hooks#91
This is necessary because `pep517` is going to drop its experimental CLIs eventually and the PyPA recomments using a new tool called `build` instead. `pypa/build` is a CLI built around the APIs provided by the `pep517` library. Refs: * pypa/pyproject-hooks#83 * pypa/pyproject-hooks#91
An attempt to tackle #82, by putting all the code that tries to manage environments & installation into a separate
buildtool_demo
package, which does not get installed.This will break things for anyone who was relying on the high-level functionality being in
pep517
, but I don't see any way to clean it up without doing that.The functions for loading & checking the build-system info are retained as part of the real package, in
pep517.pyproject
.