New release to PyPI?

[Florent]

There's many improvements in the jcrocholl repository, compared with
4.2.

Additionnally I pushed some changes to my branch:
- fix issue #1 and #4
- add --version switch
- improved --count switch

Maybe it's time to push a release to PyPI. The last one is 4 months
old.

--
Florent

[Chris Beaven]

Good idea. Everyone likes frequent releases (well, I do at least :))

[Reinout van Rees]

Last few times I did the release. Be happy to do it again. Will be Friday as I'm at a conference now. Oh, and what's the current branch that's got to be released, I mean are all changes already merged into the "trunk"?

Reinout

-- 

Reinout van Rees  rei...@vanrees.org

http://reinout.vanrees.org

http://www.thehealthagency.com

[Johann C. Rocholl]

Thank you for the updates. I have merged Florent's changes and
released a new version:
http://pypi.python.org/pypi/pep8/0.5.0

As a note to self, or in case somebody else wants to upload a new
release in the future, here are the steps to publish a new release:

1. Update version numbers in setup.py, pep8.py and CHANGES.txt:
http://github.com/jcrocholl/pep8/commit/57704caa4ec9e4b500a16427b73230e4945d0cfe

2. Log in with PyPI account:
$ python setup.py register

3. Upload source distribution tarball:
$ python setup.py sdist upload

4. Test to make sure that the new version works:
$ sudo easy_install --upgrade pep8
$ pep8 --version
$ pep8 --doctest --verbose

--
Johann

[Reinout van Rees]

Tip: use zest.releaser. That cuts the list down to just a
"fullrelease" call. Version number increase, release to pypi, new
heading in the changelog, all the paperwork.

I added git support as I used it for pep8 :-)

Reinout

--
Reinout van Rees rei...@vanrees.org
http://reinout.vanrees.org
http://www.thehealthagency.com

On 18 feb 2010, at 04:29, "Johann C. Rocholl" <joh...@rocholl.net>
wrote:

[Florent]

Good news,
I like to pep8ify my code :)

--
Florent