Missing sys.path entries when setup.py uses setup_requires

Bug #325658 reported by Marius Gedminas on 2009-02-05
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

When buildout develops an egg that both setup_requires and install_requires some package, scripts for that package don't work due to missing sys.path entries.

This is hard to describe in words, so I've attached a test case. Untar the archive and run ./reproduce.sh. It'll set up a virtualbox sandbox (to prevent your system Python from influencing the behaviour), bootstrap and run buildout, and will try to run the generated bin/testcase script, failing with an ImportError.

If you untar the archive in a fresh directory and remove the setup_requires line from setup.py before running ./reproduce.sh, bin/testcase will work fine.

Marius Gedminas (mgedmin) wrote :
Marius Gedminas (mgedmin) wrote :

This bug is probably a duplicate of #257555.

Marius Gedminas (mgedmin) wrote :

(I just spent 30 minutes debugging and then trying to reproduce this bug again.)

Interesting detail: if you use package_dir={'': 'src'} in your setup.py, this bug doesn't occur. Here's essentially the same test case with minimal modifications that made it work.

(However that's not suitable as a workaround for me, as it breaks paster shell...)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers