#83 Project rename: munepy -> flufl.enum


Please rename my project 'munepy' to 'flufl.enum'. Thank you.


  • Barry Warsaw

    Barry Warsaw - 2010-04-25
    • priority: 5 --> 7
    • summary: Project rename --> Project rename: munepy -> flufl.enum
  • Martin v. Löwis

    I have now renamed the project. There is one issue with renaming: the file names attached to a release stay the same.

    I could change the renaming implementation to perform a substring replacement on all file names. Do you think that is desirable?

  • Barry Warsaw

    Barry Warsaw - 2010-04-26

    Thanks for the rename Martin. It's not necessarily to rename the packages; I'll be uploading a new version soon with the right package names. Thanks!

  • Richard Jones

    Richard Jones - 2010-04-26

    I wouldn't bother.

  • Barry Warsaw

    Barry Warsaw - 2010-04-27

    Actually, I'm having a problem with this. The upload is failing, though the
    new version did get established.

    % python setup.py sdist upload -s -v
    running sdist
    running egg_info
    writing flufl.enum.egg-info/PKG-INFO
    writing namespace_packages to flufl.enum.egg-info/namespace_packages.txt
    writing top-level names to flufl.enum.egg-info/top_level.txt
    writing dependency_links to flufl.enum.egg-info/dependency_links.txt
    reading manifest file 'flufl.enum.egg-info/SOURCES.txt'
    reading manifest template 'MANIFEST.in'
    no previously-included directories found matching '_build'
    writing manifest file 'flufl.enum.egg-info/SOURCES.txt'
    creating flufl.enum-3.0
    creating flufl.enum-3.0/flufl
    creating flufl.enum-3.0/flufl.enum.egg-info
    creating flufl.enum-3.0/flufl/enum
    creating flufl.enum-3.0/flufl/enum/docs
    creating flufl.enum-3.0/flufl/enum/tests
    making hard links in flufl.enum-3.0...
    hard linking MANIFEST.in -> flufl.enum-3.0
    hard linking Makefile -> flufl.enum-3.0
    hard linking README.txt -> flufl.enum-3.0
    hard linking distribute_setup.py -> flufl.enum-3.0
    hard linking opens.txt -> flufl.enum-3.0
    hard linking setup.py -> flufl.enum-3.0
    hard linking setup_helpers.py -> flufl.enum-3.0
    hard linking template.py -> flufl.enum-3.0
    hard linking flufl/__init__.py -> flufl.enum-3.0/flufl
    hard linking flufl.enum.egg-info/PKG-INFO -> flufl.enum-3.0/flufl.enum.egg-info
    hard linking flufl.enum.egg-info/SOURCES.txt -> flufl.enum-3.0/flufl.enum.egg-info
    hard linking flufl.enum.egg-info/dependency_links.txt -> flufl.enum-3.0/flufl.enum.egg-info
    hard linking flufl.enum.egg-info/namespace_packages.txt -> flufl.enum-3.0/flufl.enum.egg-info
    hard linking flufl.enum.egg-info/top_level.txt -> flufl.enum-3.0/flufl.enum.egg-info
    hard linking flufl/enum/NEWS.txt -> flufl.enum-3.0/flufl/enum
    hard linking flufl/enum/README.txt -> flufl.enum-3.0/flufl/enum
    hard linking flufl/enum/__init__.py -> flufl.enum-3.0/flufl/enum
    hard linking flufl/enum/_enum.py -> flufl.enum-3.0/flufl/enum
    hard linking flufl/enum/conf.py -> flufl.enum-3.0/flufl/enum
    hard linking flufl/enum/docs/__init__.py -> flufl.enum-3.0/flufl/enum/docs
    hard linking flufl/enum/docs/using.txt -> flufl.enum-3.0/flufl/enum/docs
    hard linking flufl/enum/tests/__init__.py -> flufl.enum-3.0/flufl/enum/tests
    hard linking flufl/enum/tests/test_docs.py -> flufl.enum-3.0/flufl/enum/tests
    Writing flufl.enum-3.0/setup.cfg
    tar -cf dist/flufl.enum-3.0.tar flufl.enum-3.0
    gzip -f9 dist/flufl.enum-3.0.tar
    removing 'flufl.enum-3.0' (and everything under it)
    running upload
    gpg --detach-sign -a dist/flufl.enum-3.0.tar.gz

    You need a passphrase to unlock the secret key for
    user: "Barry Warsaw <barry@warsaw.us>"
    4096-bit RSA key, ID A74B06BF, created 2009-05-14

    File `dist/flufl.enum-3.0.tar.gz.asc' exists. Overwrite? (y/N) y
    Submitting dist/flufl.enum-3.0.tar.gz to http://pypi.python.org/pypi
    Upload failed (500): Internal Server Error

  • Martin v. Löwis

    • status: open --> closed
  • Martin v. Löwis

    Most likely, it was a permission problem, which is now fixed. If it isn't please report the full HTTP dialog (e.g. by turning on HTTP logging in the upload command).


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks