submit to PyPi

[mvexel]

Never done before, what more would be required to do this?

This seems relevant: https://packaging.python.org/en/latest/distributing.html

[mharnold]

I recently did this for the first time for spiderosm: % python setup.py register % python setup.py sdist % python setup.py sdist upload

I found the following extremely helpful: http://www.scotttorborg.com/python-packaging/minimal.html

[mharnold]

I suggest that the first step (registration) be done ASAP - might as well reserve the name.

Before uploading I suggest we clean up to PEP-8. Will be more awkward to change names, once there are users!

I also have some suggestions for the args to API.Get() that are probably best discussed before a real release.

[mvexel]

Created a release 0.1.0 for this purpose.

[mvexel]

Committed to pypi-test: https://testpypi.python.org/pypi/overpass/0.1.0

[mharnold]

Cool I didn't know about pypi-test!

[willemarcel]

I published it to pypi: https://pypi.python.org/pypi/overpass

I put my github repository, because it's the most updated.

[mvexel]

We should decide which repo is the master, and thad repo should be in sync with PyPi. I prefer this to be that repository, because yours is a fork. We should merge any upstream changes into this master first, so we can all keep track of what is going on. Sound good?

Martijn van Exel skype: mvexel

On Sun, Apr 5, 2015 at 8:03 PM, Wille Marcel notifications@github.com wrote:

I published it to pypi: https://pypi.python.org/pypi/overpass

I put my github repository, because it's the most updated.

— Reply to this email directly or view it on GitHub https://github.com/mvexel/overpass-api-python-wrapper/issues/16#issuecomment-89888982 .

[willemarcel]

Of course, It's good for me! I've updated the package in Pypi with reference to your repository and gave you owner rights.

[mvexel]

Best to send a pull request with changes from your fork to this repo so we can all review and then submit from here, does that sound good? Thanks @willemarcel

[willemarcel]

There is already a pull request: https://github.com/mvexel/overpass-api-python-wrapper/pull/27

[mvexel]

That's right, sorry for the confusion...

Martijn van Exel skype: mvexel

On Tue, Apr 7, 2015 at 6:05 AM, Wille Marcel notifications@github.com wrote:

There is already a pull request: #27 https://github.com/mvexel/overpass-api-python-wrapper/pull/27

— Reply to this email directly or view it on GitHub https://github.com/mvexel/overpass-api-python-wrapper/issues/16#issuecomment-90528500 .

[gEndelf]

@mvexel Plz

• update README
• and this issue can be closed

[willemarcel]

Hi, @gEndelf and @mvexel

I updated the README on my fork and I made a pull request some months ago (#27)

[mvexel]

Hi, just checking in here I see that there is version 0.3.1 on PyPi, however the master repo only has a 0.1.0. We should try and merge that code back in, I think this is confusing. @willemarcel is that your fork?

[mvexel]

New PR at #36 - please review!

[mvexel]

Let's prepare a new release now that @willemarcel 's code is merged in, and I made some changes that affect end users (to the CLI interface and to the responseformat parameter)

[sandrotosi]

@mvexel could you cut a new release and upload it to pypi? there has been quite a few improvements since 0.3.1 - thanks!

[mvexel]

Done. 0.4.0 now on PyPi