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

supports custom distribution files path for pdm publish #2723

Closed
zhan3680 opened this issue Mar 26, 2024 · 0 comments · Fixed by #2724
Closed

supports custom distribution files path for pdm publish #2723

zhan3680 opened this issue Mar 26, 2024 · 0 comments · Fixed by #2724
Assignees
Labels
⭐ enhancement Improvements for existing features

Comments

@zhan3680
Copy link

Is your feature/enhancement proposal related to a problem? Please describe.

Currently when running pdm publish to upload python distributions to a remote repository, it is not possible to specify a custom path of the distribution files, even when using --no-build:
pdm publish [-h] [-v | -q] [-p PROJECT_PATH] [-k SKIP] [-r REPOSITORY] [-u USERNAME] [-P PASSWORD] [-S] [-i IDENTITY] [-c COMMENT] [--no-build] [--skip-existing] [--no-very-ssl | --ca-certs CA_CERTS]

Describe the solution you'd like

Previously I was using twine, which allows specifying custom location of distribution files: twine upload [options] custom_dist_path; I also noticed that pdm build has -d DEST, --dest DEST Target directory to put artifacts option, can we have something similar for pdm publish as well? Any feedback would be appreciated.

@zhan3680 zhan3680 added the ⭐ enhancement Improvements for existing features label Mar 26, 2024
@frostming frostming self-assigned this Mar 27, 2024
frostming added a commit that referenced this issue Mar 27, 2024
Fixes #2723

Signed-off-by: Frost Ming <me@frostming.com>
frostming added a commit that referenced this issue Mar 27, 2024
Fixes #2723

Signed-off-by: Frost Ming <me@frostming.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⭐ enhancement Improvements for existing features
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants