Hm, ok. I went ahead and just used mkDerivation directly "setup.py install" instead of going the buildPythonPackage route. This yields directories instead of eggs. I then made wrappers with appropriate PYTHONPATH around the binaries, similar to what some other packages did.
Python eggs (with their site.py and setuptools.pth merging) always seem ironically more complicated that standard module loading, anyway, and fitting them into a modular user environment seems to be more trouble than it's worth. -nate On Fri, Jun 11, 2010 at 4:15 AM, Ludovic Courtès <[email protected]> wrote: > Hi, > > Peter Simons <[email protected]> writes: > >> Generally speaking, the state of Python in Nix is poor. We need a way to >> compute PYTHONPATH properly, like ghc-wrapper does for GHC, but so far no-one >> has volunteered to do it. > > More precisely, the state of Python libraries in user environments is > poor. > > Python applications in user environments (e.g., Tahoe-LAFS, BuildBot) > work well. > > Within Nix builds Python’s setup hook along with ‘buildPythonPackage’ do > the right thing, too. > > Thanks, > Ludo’. > _______________________________________________ nix-dev mailing list [email protected] https://mail.cs.uu.nl/mailman/listinfo/nix-dev
