El 03/12/2013 10:22, Paul Moore escribió:
On 3 December 2013 08:48, Nick Coghlan <ncogh...@gmail.com> wrote:
This means that one key reason I want to recommend it for the cases where it
is a good fit (i.e. the scientific Python stack) is so we can explicitly
advise *against* using it in other cases where it will just add complexity
without adding value.
Saying nothing is not an option, since people are already confused. Saying
to never use it isn't an option either, since bootstrapping conda first *is*
a substantially simpler cross-platform way to get up to date scientific
Python software on to your system. The alternatives are platform specific
and (at least in the Linux distro case) slower to get updates.
But you're not saying "use conda for the scientific Python stack".
You're saying to use it "when you have binary external dependencies"
which is a phrase that I (and I suspect many Windows users) don't
really understand and will take to mean "C extensions, or at least
ones that interface to another library, sich as pyyaml, lxml, ...)
Also, this presumes an either/or situation. What about someone who
just wants to use matplotlib to display a graph of some business data?
Is matplotlib part of "the scientific stack"? Should I use conda
*just* to get matplotlib in an otherwise wheel-based application? Or
how about a scientist that wants wxPython (to use Chris' example)?
Apparently the conda repo doesn't include wxPython, so do they need to
learn how to install pip into a conda environment? (Note that there's
no wxPython wheel, so this isn't a good example yet, but I'd hope it
will be in due course...)
Reducing confusion is good, I'm all for that. But we need to have a
clear picture of what we're saying before we can state it clearly...
Paul
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
A first and non-native try to get a clearer wording for this:
"Some collections of python packages may have further compatibility
needs than those expressed by the current set of platform tags used in
wheels.
That is the case of the Python scientific stack, where interoperability
depends on the choice of a shared binary data format that is decided at
build time.
This problem can be solved by packagers' consensus on a common choice of
compatibility options or by using curated indices. Also, package
managers like conda do additional checks to ensure a coherent set of
Python and non-Python packages and may offer at this time a better user
experience for package collections with such complex dependencies."
Regards,
--
Pachi
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
