Skip to content
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

[Python APIView] Support for packages with only pyproject.toml #9617

Open
lmazuel opened this issue Jan 10, 2025 · 1 comment
Open

[Python APIView] Support for packages with only pyproject.toml #9617

lmazuel opened this issue Jan 10, 2025 · 1 comment
Assignees
Labels
APIView feature-request This issue requires a new behavior in the product in order be resolved. P1 Python

Comments

@lmazuel
Copy link
Member

lmazuel commented Jan 10, 2025

As we're planning to move away from setup.py and have only a pyproject.toml, APIView needs to be able to handle source code with no setup.py.

This PR can be used to look into what a pure pyproject.toml package looks like:
Azure/azure-sdk-for-python#39100

Note that the wheel will be exactly the same (since a wheel do not contain packaging information anymore), it's only the source (Github and sdist) that are different

@lmazuel lmazuel added APIView feature-request This issue requires a new behavior in the product in order be resolved. P1 Python labels Jan 10, 2025
@lmazuel lmazuel self-assigned this Jan 10, 2025
@github-project-automation github-project-automation bot moved this to 🆕 New in ApiView Jan 10, 2025
@lmazuel lmazuel assigned swathipil and unassigned lmazuel Jan 10, 2025
@swathipil
Copy link
Member

swathipil commented Jan 14, 2025

For reading pyproject.toml, try not to use if "pyproject.toml" vs. "setup.py", look into using these packages:

  • setuptools
  • build
  • pip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
APIView feature-request This issue requires a new behavior in the product in order be resolved. P1 Python
Projects
Status: 🆕 New
Development

Successfully merging a pull request may close this issue.

2 participants