-
Notifications
You must be signed in to change notification settings - Fork 590
Update package metadata #817
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
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,61 @@ | ||
| [build-system] | ||
| requires = ["setuptools", "wheel"] | ||
| build-backend = "setuptools.build_meta" | ||
| requires = ["hatchling>=0.14.0"] | ||
| build-backend = "hatchling.build" | ||
|
|
||
| [project] | ||
| name = "pipx" | ||
| description = "Install and Run Python Applications in Isolated Environments" | ||
| readme = "README.md" | ||
| license = "MIT" | ||
| requires-python = ">=3.7" | ||
| keywords = [ | ||
| "pip", | ||
| "install", | ||
| "cli", | ||
| "workflow", | ||
| "Virtual Environment", | ||
| ] | ||
| authors = [ | ||
| { name = "Chad Smith", email = "chadsmith.software@gmail.com" }, | ||
| ] | ||
| classifiers = [ | ||
| "License :: OSI Approved :: MIT License", | ||
| "Operating System :: OS Independent", | ||
| "Programming Language :: Python", | ||
| "Programming Language :: Python :: 3 :: Only", | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. One feature gap compared to setuptools and
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I suppose I could add a command for that but:
Are you saying that until there is a
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Indeed 😊 I am loosing some functionality otherwise that I do have with the current framework, and the benefits of switching to PEP-621 in the short term are not that much compared to
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Setup-cfg-fmt does a lot more than just formatting, it also keeps up the classifiers for new Python versions and cleans them up, sorts dependencies, etc. It also runs in pre-commit, can taplo? It also strips comments, valid empty (sub) sections, and can’t be disabled for part of a file AFAIK…
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
👍 An eventual tool should not be tied to a build backend, but be a generic tool; probably a pair of tools like taplo & (imaginary atm) pep621-fmt or something. Fmt is a little off since it would be more of a validator. Happy to have it live alongside hatch though. ;)
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There are some very good reasons to put comments in sometimes, like https://github.com/scikit-hep/awkward-1.0/blob/6d3c1d23d7ab492d0178b1798e179088a066e00a/pyproject.toml#L90-L157 - probably rare for the project metadata itself, but the other tool fields might need comments (flake8/pylint config being big ones for needed comments). Comments can be overdone, sure, but sometimes they are needed. setup-cfg-fmt doesn't support them for technical reasons, not primarily because they are a bad idea. I usually have managed without comments in setup.cfg, though, sometimes painfully with flake8, but really hope not to leak that issue over into pyproject.toml. :) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
As an example of its potential, I can safely use it in ini2toml for translating the "AST" of So if its being a while that you last checked
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. For what's worth I've been using There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Run into this due to the ping, and I found @gaborbernat already made a pyproject.toml formatter, powered by
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I tried to use toolkit in cibuildwheel (at least 6 months ago, probably more), and found it too buggy to use; it was a rather weird format, but it was important to keep it, which it failed to do. I ended up just writing a manual writer, since it was a very well structured limited file. Great to hear it is seeing improvements! I know it was not 1.0.0 compliant either last I checked, but is now. :) And @gaborbernat, @abravalheri, and @ofek have all made TOML formatter/validators. :) |
||
| "Programming Language :: Python :: 3.7", | ||
| "Programming Language :: Python :: 3.8", | ||
| "Programming Language :: Python :: 3.9", | ||
| "Programming Language :: Python :: 3.10", | ||
| ] | ||
| dependencies = [ | ||
| "argcomplete>=1.9.4", | ||
| "colorama>=0.4.4; sys_platform == 'win32'", | ||
| "importlib-metadata>=3.3.0; python_version < '3.8'", | ||
| "packaging>=20.0", | ||
| "userpath>=1.6.0", | ||
| ] | ||
| dynamic = ["version"] | ||
|
|
||
| [project.urls] | ||
| Documentation = "https://pypa.github.io/pipx/" | ||
| "Source Code" = "https://github.com/pypa/pipx" | ||
| "Bug Tracker" = "https://github.com/pypa/pipx/issues" | ||
|
|
||
| [project.scripts] | ||
| pipx = "pipx.main:cli" | ||
|
|
||
| [tool.hatch.version] | ||
| source = "code" | ||
| path = "src/pipx/version.py" | ||
|
|
||
| [tool.hatch.build.targets.sdist] | ||
| include = [ | ||
| "/src", | ||
| "/logo.png", | ||
| "/pipx_demo.gif", | ||
| "/*.md", | ||
| ] | ||
|
|
||
| [tool.isort] | ||
| profile = "black" | ||
|
|
||
This file was deleted.
This file was deleted.
Uh oh!
There was an error while loading. Please reload this page.