>> Will your update include our stance on including all python packages >> versus only c-modules (or otherwise needing MacPorts' involvement)? > > I'm not sure what you mean.
Joshua pointed it out in a previous thread: we don't make use of other package managers (Pip in this instance), so we shouldn't have their packages in MacPorts unless they have requisites in MacPorts. If you don't see this as an issue, that's perfectly fine too (unless Joshua wants to chime in again ;-) ). _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
