[SciPy-User] SciPy ecosystem and Python 3
Sun Jun 30 09:11:41 CDT 2013
The main road block holding me back, just as a user in the environmental
consulting world, is the shapely/decartes combo. I believe that I only have
two project relying on them, and I could probably work around that in some
way, but I have a notebook in "production" for one project and no budget to
make that switch.
Luckily though, that's on a separate machine from my main working
environment, so I actually plan on making the switch soon (I've installed
everything so far).
On Thu, Jun 27, 2013 at 5:22 PM, Thomas Kluyver <firstname.lastname@example.org> wrote:
> At a conversation over lunch here at the SciPy conference, a few of us
> mentioned that we're starting to use Python 3 in earnest for our work.
> For new users, the choice of two major Python versions is confusing and
> offputting, and we're not going to completely get rid of that confusion
> until we can simply point new users to Python 3. Most of our introductions,
> like the SciPy stack install page, point to Python 2 because of the
> ecosystem, but more and more packages now support Python 3, and we're
> reaching the point where we could reasonably recommend Python 3 for new
> The aim of this post is to get an overview of where the ecosystem is with:
> - What packages don't yet support Python 3, or are still too unstable?
> - How important are each of those: how widely relevant are they, and are
> substitutes available?
> - What other conditions need to be met to recommend Python 3? E.g.
> Scientific Python distros, Linux distro packaging, documentation, etc.
> SciPy-User mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SciPy-User