Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Python #82

Open
3 of 18 tasks
codyopel opened this issue Nov 19, 2017 · 0 comments
Open
3 of 18 tasks

Python #82

codyopel opened this issue Nov 19, 2017 · 0 comments

Comments

@codyopel
Copy link
Member

codyopel commented Nov 19, 2017

Meta issue for tracking, planning, and breakage.

Priority 1

  • Rewrite wrapPython

Priority 2

  • Document bootstrapping buildPythonPackage
  • Fix stage 1 prefixName
  • Fix hardcoded PYTHONPATH definitions, always assume path is empty (e.g. ${PYTHONPATH:+:}$PYTHONPATH)
  • Symlink setuptools' dependencies into the vendor directory to reuse the vendor import paths and prevent propagating setuptools' dependencies
  • Stage 2 setuptools breaks namespaced imports on Python 2 (possibly other issues as well, also possibly applicable to Python 3). Currently we reuse the Stage 1 derivation.
    Update: This is an upstream setuptools bug when installing setuptools from a wheel to a wheel.
  • Don't overwrite pre/post phases in buildPythonPackage, append the pre/post phases defined in buildPythonPackage.
  • Possibly rewrite fetchPyPi to use python instead of jq
  • Remove with pkgs.lib from python-packages.nix, inherit lib normally
  • Check for orphaned packages
  • Finish moving packages out of python-packages.nix
  • Come up with a solution for removing propagation
  • Work on an alternative for PYTHONPATH that isn't susceptible to Python 2 & 3 collisions. In conjunction with wrapPython. rewrite build-python-package to not use PYTHONPATH #64
  • Install wheel files to a unique output
  • review and port deterministic build patches
  • Clean up check phases and functionality
  • rename configureFlags in buildPythonPackage
  • If possible, only propagate setuptools where necessary (e.g. namespaced packages require setuptools at runtime)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant