Ed Morley

Hi! This doesn't seem like an issue with the buildpack, rather an issue with jupyter hub - and so not a Heroku issue? The NLTK feature of this buildpack is...

Closing since this appears to be an upstream issue.

I'd love to be able to add support for this in a vendor-independent manner. Perhaps we can use `requires-python` and either: (a) insist it specifies a single version (or at...

I've written up my latest thoughts on ways to specify Python version for Heroku apps, here: https://github.com/heroku/heroku-buildpack-python/issues/913#issuecomment-1031468659

See also recent discussion on: https://github.com/heroku/heroku-buildpack-python/pull/982#issuecomment-815645795

Closing this out for the reasons in https://github.com/heroku/heroku-buildpack-python/pull/982#issuecomment-815645795 - we can always revisit in the future if needed.

@zyv Hi! There is not a public API - the files are just uploaded to S3. I think the best way to solve this is to fix #913, that way...

One advantage of the #913 approach would be that the resultant Python version would be deterministic for the buildpack release. That is, pinning to an older buildpack would give a...

Closing in favour of #913. In the meantime you can pull/parse this file: https://raw.githubusercontent.com/heroku/heroku-buildpack-python/main/bin/default_pythons

Reading through #656 and #654 it appears the issue is more to to with editable dependencies rather than git. I'm pretty sure this is due to the path rewriting hacks...