Ed Morley

(Think of `--flatten` like controlling which git commits in a git log to squash together -- it doesn't change what is in the overall working directory on HEAD compared to...

Hi! Thank you for filing an issue :-) Could you add some more detail on why the production dependencies are kept in a separate group? In general, we would encourage...

Thank you for the extra context! For dependencies that are only used in production, I think there is still often value in having them as part of the main dependency...

I just came across another case which caused confusion when debugging, due to the subdir buildpack not being listed first (which caused the earlier buildpacks to be clobbered). @timanovsky Would...

We also need to filter out the env var `RANDOM`, since it's a special Bash env var too, otherwise `RANDOM=Foo` results in eg: ``` /tmp/codon/tmp/buildpacks/0f40890b54a617ec2334fac0439a123c6a0c1136/vendor/buildpack-stdlib_v8.sh: line 56: Foo: unbound variable...

Also non-ASCII env var names apparently (plus it seems API should prevent setting these in the first place?): ``` /tmp/codon/tmp/buildpacks/0f40890b54a617ec2334fac0439a123c6a0c1136/vendor/buildpack-stdlib_v8.sh: line 56: export: `': not a valid identifier ```

@guybowden Hi! I'd recommend writing the profile file directly - the buildpack's own scripts are considered an internal implementation detail and not part of the public API. Also, I would...

(The behaviour here changed as of #1595, which intentionally stopped some env vars leaking into subprocesses: https://github.com/heroku/heroku-buildpack-python/blob/main/CHANGELOG.md#v252---2024-06-17)

The docs for `.profile.d/` are here, in case it helps :-) https://devcenter.heroku.com/articles/buildpack-api#profile-d-scripts

Closing since this is answered, but feel free to comment if you have any more questions :-)