Closed theskumar closed 9 years ago
Interesting. Keep using .bumpversion.cfg as a workaround, I'll look into it.
On 03 Feb 2015, at 06:33, Saurabh Kumar notifications@github.com wrote:
setup.cfg (Before)
[bumpversion] current_version = 0.1.0
[other] DJANGO_SETTINGS = Value setup.cfg running bumpversion patch
[bumpversion] current_version = 0.1.1
[other] django_settings = Value We moved the .bumpversion.cfg to setup.cfg which already had other sections. bumping up a new version makes all the keys in setup.cfg lowercase making them unusable. @peritus thoughts?
\ Reply to this email directly or view it on GitHub.
Sure and thanks!
That should be fixed now, thanks again for the report.
I'll come say hello, next time I'm in New Delhi and you show me the Python community in India ?
Hey @peritus, sure any time, would love to do that. We also have Pycon India 2015 coming up. http://in.pycon.org/2015/. You might wanna plan something around that timeline.
Just drop me an email or i'm available at @_theskumar
Thanks! Will be in India probably around this time next year, backpacking with my girlfriend. We're currently learning some hindi and need to finish a university graduation, but after that India is our first stop!
I'll reach out to you, even if only for a coffee in New Delhi.
sure thing :)
@peritus since this was a patch/fix wondering if we can have a new release 0.5.2, so we are able to install it via pypi.
Thanks,
setup.cfg
(Before)setup.cfg
runningbumpversion patch
We moved the
.bumpversion.cfg
tosetup.cfg
which already had other sections. bumping up a new version makes all the keys insetup.cfg
lowercase making them unusable. @peritus thoughts?