Build fails with python error in release v22 about heroku-buildpack-php HOT 9 CLOSED

This might be applicable to the issue...I'm using an empty composer.json file created using the instructions in the README:
echo '{}' > composer.json

The composer.lock file is therefore empty which may be why it's not getting handled properly

from heroku-buildpack-php.

Is your composer.lock completely empty, or does it contain any whitespace, or {} or similar? What operating system is this on?

Was the file generated by Composer, or through some other mechanism, or did you create it by hand?

from heroku-buildpack-php.

If you remove it and run composer update, does it get created again?

from heroku-buildpack-php.

Completely empty. It looks like composer doesn't generate a composer.lock file when the composer.json is empty.

It's been a while since I set up the project but I probably just did a touch composer.lock so it was there and would be detected as a php app.

from heroku-buildpack-php.

OSX 10.9.3

Composer version e77435cd0c984e2031d915a6b42648e7b284dd5c 2014-07-02 15:44:54

from heroku-buildpack-php.

FWIW, if I do:
echo '{}' > composer.lock
...then it will deploy properly.

So, not sure if this is necessarily a bug after all, but v21 didn't complain about an empty composer.lock

from heroku-buildpack-php.

You don't need a composer.lock at all. If you run composer update, Composer will remove it, as your composer.json specifies no package dependencies and thus needs no lock file.

from heroku-buildpack-php.

Ah, well that's even better 👍

I've been so used to using another buildpack before you added official support I assumed the composer.lock was required. My apologies for all the back and forth.

from heroku-buildpack-php.

Alright, should be all fixed now (5bfe3a5, already released), just in case you ever run into it again. Thanks for the heads-up!

P.S. you can do heroku config:unset BUILDPACK_URL as it'll auto-detect PHP projects and use the official buildpack.

from heroku-buildpack-php.