Office365-rest-python-client: Release version 2.1.1, to PyPI?

Created on 4 Jun 2018  ·  13Comments  ·  Source: vgrem/Office365-REST-Python-Client

Today I tried this library. I could get the v2.0.0 to work with Microsofts current Office365. I also tried checking out the GitHub version and installed it manually, this worked. Is it possible to release v2.1.1 to PyPI too so it can be installed with PIP?

enhancement

Most helpful comment

100% kudos for great library goes to @vgrem. Me, I just needed PyPI package some time ago. Anyway: I'll update on the progress. This doesn't seem to be difficult at all, but some steps are required.

The plan proposal. Overall:

  • use TravisCI for all release tasks,
  • trigger TravisCI based on git-tags
  • release will require a) bumping version in setup.py, b) creating git-tag (possibly with some naming convention).

Steps:

  1. get POC of that scheme working
  2. enable this ability on a fork of this repo, to double check (and currently I have creds for PyPI package)
  3. when all works fine, I'll transfer PyPI package ownership to @vgrem and make a PR to this repo.

All 13 comments

Eh. This is probably on me. Thanks for bringing this up.

Full disclosure: I mentioned that I'll prepare proper pipeline to automatically release to PyPI from Travis. I said that few months ago… I hope that this ticket will motivate me to find time to finally do that 😞

Hey @kgadek it's not a problem, I know how it works haha. Just thought I should bring it to you attention :-) Thanks for the nice library!

100% kudos for great library goes to @vgrem. Me, I just needed PyPI package some time ago. Anyway: I'll update on the progress. This doesn't seem to be difficult at all, but some steps are required.

The plan proposal. Overall:

  • use TravisCI for all release tasks,
  • trigger TravisCI based on git-tags
  • release will require a) bumping version in setup.py, b) creating git-tag (possibly with some naming convention).

Steps:

  1. get POC of that scheme working
  2. enable this ability on a fork of this repo, to double check (and currently I have creds for PyPI package)
  3. when all works fine, I'll transfer PyPI package ownership to @vgrem and make a PR to this repo.

I've manually released version 2.1.1 to PyPI — please check if that works: https://pypi.org/project/Office365-REST-Python-Client/2.1.1/

New issue #92 and associated PR #93 are essentially a step 1 & 2 described above.

Sorry it took this much time.

@kgadek I think the maintainer of the repo should be able to manually upload a package
Very often between the release on github and the pypi upload we have some time waiting the pypi owner to do a manual upload (travis upload is not working at the moment) and people have to go and check pypi hoping to find the package there...
(https://github.com/vgrem/Office365-REST-Python-Client/pull/184)

Do you think we can try to find a solution?

Hey guys!

Meanwhile 2.1.9 version has been released.

Hopefully we'll get it published to PyPI soon
with fellow contributors @kgadek and @domdinicola

Great!
pypi package version 2.1.9 is available here https://pypi.org/project/office365-rest-client/
@kgadek would be appreciated if you can grant myself and @vgrem access to the official pypi package.

Hey guys,

2.1.10 version has been released

pypi version is available here https://pypi.org/project/office365-rest-client/
@kgadek pls give us access to the official pypi version

Hi all, Sorry for a [very] long hiatus. Trying to quickly catch up.

I've added dom.dinicola & vgrem as co-owners on PyPI. I believe one of next steps would be to complete a transfer of the repo to one of you guys. Not sure if your permissions allow this, I'll be happy to help with this.

I've pushed tags to my fork, my-travis happily built and released 2.1.8, but failed at 2.2.0 and master. I believe this is caused by config made to @vgrem's-travis account and missing in mine-travis.

Thus, I think it'd be best to first configure @vgrem's-travis to do releases (and deprecate my fork), then it should all be good.

Greetings @kgadek and good to hear from you! :)
I confirm PyPI access, thank you!

Token password has been generated per instruction () but not sure yet how to trigger PyPI update.
Vadim

pypi packages have been uploaded! Let's wait next release to check if automatic upload works!

Was this page helpful?
0 / 5 - 0 ratings