Add scripts for building conda package and deployingn to anaconda.org

[joshbtn]

trafficstars

Great project thanks for sharing!

This pull request contains scripts I used to package your project with conda and deploy it to anaconda.org (https://anaconda.org/joshbtn/neo4j-driver). The upload location is driven by the anaconda token.

I leveraged TravisCI to deploy based on a new tag being created. The only thing that needs to be set in travis to make this work is an ANACONDA_TOKEN.

Regards, Josh Bennett

[technige]

Thanks. We'll look into this.

[technige]

Hi @joshbtn

I've just started looking at this but I'm unfamiliar with Anaconda in general. Could you help me understand how this benefits users above and beyond the PyPI distribution, and how this might be achieved through our own internal build infrastructure, rather than Travis CI.

Thanks Nigel

[jberends]

Hi @joshbtn

I've just started looking at this but I'm unfamiliar with Anaconda in general. Could you help me understand how this benefits users above and beyond the PyPI distribution, and how this might be achieved through our own internal build infrastructure, rather than Travis CI.

Thanks Nigel

Anaconda is similar to PyPI in the way you distribute, however a lot of (my) corporate clients may only use anaconda repositories for download of packages and not from PyPI due to their internal IT regulations which are overly concerned with security. Therefore it would be beneficial to have all neo4j packages distributed both in PyPI and in Anaconda. This contributes to the bottomline of adoption of neo4j in python (which is the de-facto (and discussable) standard for datascience and AI projects)

[martin-neotech]

I will have a look into this for the 4.0 release of the driver.

[robsdedude]

I don't think this is needed any longer as conda forge picked up the slack :raised_hands: :bow:

https://github.com/conda-forge/neo4j-python-driver-feedstock