cloudfoundry/bosh-package-python-release

Python release for use with `bosh vendor-package`

python

To vendor python package into your release, run:

$ bosh vendor-package python-2.7 ~/workspace/bosh-packages/python-release

Included packages:

• python-2.7

To use python-* package for compilation in your packaging script:

#!/bin/bash -eu
source /var/vcap/packages/python-2.7/bosh/compile.env
pip install ...

bosh-package-python-release's Issues

upgrade pip 1.5.2 -> pip 10

https://pypi.org/simple/pip/

Keep versions up to date

• This release appears to be using python 2.7.6. The current release in the 2.x series is 2.1.14. We should upgrade.
• It would be great to package python 3.x as well.
• It would be ideal to keep versions current using CI, as suggested in cloudfoundry/bosh-package-golang-release#4.

python 3.6 package

Is this effectively deprecated?

(EDIT going to close this, it sounded ruder than I intended && I'm just going to package python myself 👍 )

Open question: is this vendored python-release effectively not maintained anymore?

Not trying to be whiny or sound ungrateful or anything like that; just trying to gauge my options as I'm slapping together a bosh release which requires Python, but I'm thinking that for now I should package it myself?

No worries either way, and if no one responds no worries I'll take it as "yes, it's no longer maintained", just figured I'd ask 😉 Thanks!

upgrade setuptools 2.2 to 39.1.0

https://pypi.org/simple/setuptools/

Also switches from tar.gz to zip