Skip to content

release procedure update / twine check / Project pre-registration is no longer required #173

Closed as not planned

Description

@s-celles
$ python setup.py register sdist bdist_wheel --universal
running register
running egg_info
creating semver.egg-info
writing semver.egg-info/PKG-INFO
writing dependency_links to semver.egg-info/dependency_links.txt
writing entry points to semver.egg-info/entry_points.txt
writing top-level names to semver.egg-info/top_level.txt
writing manifest file 'semver.egg-info/SOURCES.txt'
reading manifest file 'semver.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'semver.egg-info/SOURCES.txt'
running check
warning: Check: This command has been deprecated. Use `twine check` instead: https://packaging.python.org/guides/making-a-pypi-friendly-readme#validating-restructuredtext-markup

The project's long description is valid RST.
Registering semver to https://upload.pypi.org/legacy/
Server response (410): Project pre-registration is no longer required or supported, upload your files instead.
WARNING: Registering is deprecated, use twine to upload instead (https://pypi.org/p/twine/)
running sdist
creating semver-2.9.0
creating semver-2.9.0/semver.egg-info
copying files to semver-2.9.0...
copying LICENSE.txt -> semver-2.9.0
copying MANIFEST.in -> semver-2.9.0
copying README.rst -> semver-2.9.0
copying semver.py -> semver-2.9.0
copying setup.cfg -> semver-2.9.0
copying setup.py -> semver-2.9.0
copying test_semver.py -> semver-2.9.0
copying semver.egg-info/PKG-INFO -> semver-2.9.0/semver.egg-info
copying semver.egg-info/SOURCES.txt -> semver-2.9.0/semver.egg-info
copying semver.egg-info/dependency_links.txt -> semver-2.9.0/semver.egg-info
copying semver.egg-info/entry_points.txt -> semver-2.9.0/semver.egg-info
copying semver.egg-info/top_level.txt -> semver-2.9.0/semver.egg-info
Writing semver-2.9.0/setup.cfg
creating dist
Creating tar archive
removing 'semver-2.9.0' (and everything under it)
running bdist_wheel
running build
running build_py
creating build
creating build/lib
copying semver.py -> build/lib
installing to build/bdist.macosx-10.9-x86_64/wheel
running install
running install_lib
creating build/bdist.macosx-10.9-x86_64
creating build/bdist.macosx-10.9-x86_64/wheel
copying build/lib/semver.py -> build/bdist.macosx-10.9-x86_64/wheel
running install_egg_info
Copying semver.egg-info to build/bdist.macosx-10.9-x86_64/wheel/semver-2.9.0-py3.7.egg-info
running install_scripts
adding license file "LICENSE.txt" (matched pattern "LICEN[CS]E*")
creating build/bdist.macosx-10.9-x86_64/wheel/semver-2.9.0.dist-info/WHEEL
creating 'dist/semver-2.9.0-py2.py3-none-any.whl' and adding 'build/bdist.macosx-10.9-x86_64/wheel' to it
adding 'semver.py'
adding 'semver-2.9.0.dist-info/LICENSE.txt'
adding 'semver-2.9.0.dist-info/METADATA'
adding 'semver-2.9.0.dist-info/WHEEL'
adding 'semver-2.9.0.dist-info/entry_points.txt'
adding 'semver-2.9.0.dist-info/top_level.txt'
adding 'semver-2.9.0.dist-info/RECORD'
removing build/bdist.macosx-10.9-x86_64/wheel
(base) ✔ ~/github/scls19fr/python-semver [master|✔]
16:18 $ twine upload dist/*
Uploading distributions to https://upload.pypi.org/legacy/
Uploading semver-2.9.0-py2.py3-none-any.whl
100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 16.8k/16.8k [00:02<00:00, 7.29kB/s]
Uploading semver-2.9.0.tar.gz
100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 20.8k/20.8k [00:01<00:00, 12.7kB/s]

Activity

  1. changed the title [-]release procedure update / twine check[/-] [+]release procedure update / twine check / Project pre-registration is no longer required[/+] on Oct 30, 2019
  2. added
    InfraAll about infrastructure (GitHub Action, project build etc.)
    on Nov 5, 2019
  3. added
    WontfixInvalid, out-of-scope, or other inappropriate issues
    on Dec 23, 2022
  4. tomschr commented on Dec 23, 2022

    @tomschr
    Member

    I think, this is already solved with the new(?) setup.cfg/pyproject.toml that was introduced some ago (probably in commit cbd4335).

    I close this issue for the time being. If you have concerns or further ideas, just reopen it and we can discuss the details. 🙂

    Many thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    InfraAll about infrastructure (GitHub Action, project build etc.)WontfixInvalid, out-of-scope, or other inappropriate issues

    Type

    No type

    Fields

    SIze

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions