114 | | {{{ |
115 | | #!comment |
116 | | ==== Integrate with Python's PIP ==== #pip |
117 | | |
118 | | MacPorts should be able to search and install python packages using pip. MacPorts should continue to track what is installed and lock as it interacts with pip. |
119 | | |
120 | | Pip generates dependency files which should be made readable by MacPorts, perhaps as automatically generated Portfiles if one does not already exist. |
121 | | |
122 | | Classification: medium to challenging task[[BR]] |
| 114 | ==== Read Packages from Python's PIP (pip2port) ==== #pip2port |
| 115 | |
| 116 | MacPorts should be able to more readily install python packages from pip. We don't want to integrate the build/installation process of PIP, simply parse information or eggs it provides for various packages. This information will then be used to generate a Portfile, akin to [browser:contrib/cpan2port/cpan2port cpan2port]. |
| 117 | |
| 118 | There may be instances where MacPorts package names don't match up with pip's. In this case, pip should be the authority and all improperly named MacPorts packages should be replaced by a renamed copy. Verbose automation of this step, akin to the portcheckup script, is ideal. |
| 119 | |
| 120 | The [browser:contrib/portfile-gen/portfile-gen portfile generator] may or be helpful. |
| 121 | |
| 122 | Classification: medium task[[BR]] |