[HTTP server] Build failing due to removing Pipfile and Pipdfile.lock

Checklist:

  1. :white_check_mark: or :cross_mark:: I’ve uncommented the code.
  2. :white_check_mark: or :cross_mark:: I’ve saved the changes.
  3. :white_check_mark: or :cross_mark:: I’ve run the git commands:
git commit -am "[seeking help on forum]"
git push origin master

I’m working on the Python HTTP Server challenge and switched from pipenv to uv + pyproject.toml. I’ve deleted Pipfile and Pipfile.lock as they were causing issues in vscode due to pipenv not being installed and added a valid .codecrafters.yml with a custom build script using uv. However, the build still fails with:

failed to calculate checksum of ref … “/Pipfile”: not found.

It seems like the old pipenv cache is still being used. Could you please help clear/reset the cache on your end?

here’s the relevant build log:
remote: [build] Step 11 complete.
remote: [build] Error: failed to calculate checksum of ref v0oay9i9vljk0pfrxkj9avnts::y8i81r3u80n8vrgm6zra3n7cl: “/Pipfile”: not found.
remote: [build] Error: failed to calculate checksum of ref v0oay9i9vljk0pfrxkj9avnts::y8i81r3u80n8vrgm6zra3n7cl: “/Pipfile.lock”: not found.
remote: [build] Build failed. Check the logs above for the reason.

Hey @rowds, unfortunately our Python tester currently only supports pipenv, since it’s built into the Dockerfile.

We’re planning to introduce buildpack variants that can support different build tools like uv and/or poetry, but for now pipenv is required for the build to succeed.

Appreciate you highlighting the issue, and let us know if you run into anything else!

Hey @andy1li, thanks for the clarification. It’s a long shot, but by any chance is is possible to push our own docker file? Or it is maintained centrally only?

I can contribute in making the buildpack variants too if that is an option.

@rowds Really appreciate the offer to help! :folded_hands:

Buildpack variants are still in the planning stage, and the groundwork to support them hasn’t been laid out yet. For now, pipenv is the only supported option.

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.