New release to pypi server

[slitayem]

Can you please release a new version from master branch. The last release 5.0.6 is from 2014.

Thanks.

[slitayem]

@jhermann @robdennis @EliAndrewC Can anyone of you please do that ?
The last release was done on 2014
https://configobj.readthedocs.io/en/latest/configobj.html#version-5-0-6
Is the project still maintained ?

[kiddten]

bump

[bsipocz]

Hi,
Is there a ETA for the next release please?

[brainwane]

Hi! I'm a Twine maintainer; thanks for using Twine in your packaging and release process. I noticed you've pinned an old version of Twine in your requirements file. Twine has changes in 1.11.0 that you might find useful, and I hope that, when you start making your next release, you'll upgrade Twine. If you have any trouble upgrading, please do let us know.

[fmaussion]

I came into this issue today: for some inexplicable reason, the configobj package on pypi is named 5.0.6 but is dated from Aug 26, 2014. The file shipped with pypi contains this error: you can check it by yourself by downloading the package on pypi (https://pypi.org/project/configobj/#files) and open configobj.py

The header reads:

...
from _version import __version__

Where it should import from ._version instead. No idea how this old file made it to pypi but this should be corrected. Is anybody on this thread now using an alternative lib, or do you install from github instead?

[hoechenberger]

or do you install from github instead?

This. Unfortunately.

[fmaussion]

@jhermann any news on a PyPi release?

[vazhnov]

Last commit to master branch = 3 month ago.
Last release = 5 years ago.
Is this right time to release new version?

P.S.:
Sorry, I see:

• https://github.com/DiffSK/configobj/milestone/5
• 5.1.0 Release #105

[Sinan81]

wasted several hours on this. The version on PyPi even doesn't compile. Waiting for the above mentioned milestones to be completed, which seems to be overdue.

[hoechenberger]

I've created a "packaging fork" of configobj, meaning I simply copied configobj:master and released it to PyPI and conda-forge as configobj-dev. As the name of the installed package remains unchanged, it can be used as a drop-in replacement for configobj.

# install via pip:
pip install configobj-dev

# install via conda:
conda install -c conda-forge configobj-dev

See https://github.com/hoechenberger/configobj-dev/#configobj-dev

Hope this makes life for some of you a little easier!

[ericfrederich]

Someone should make a new release of this. I cannot use click-config-file in conjunction with versioneer because of #91.

[robdennis]

I think this is related to #213 / #204 so I'm going to track it there