You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 thatpdm build
has-d DEST, --dest DEST Target directory to put artifacts
option, can we have something similar forpdm publish
as well? Any feedback would be appreciated.The text was updated successfully, but these errors were encountered: