[SciPy-User] SciPy ecosystem and Python 3
Charles R Harris
Tue Jul 2 10:54:19 CDT 2013
On Tue, Jul 2, 2013 at 9:10 AM, Matthew Brett <firstname.lastname@example.org>wrote:
> On Tue, Jul 2, 2013 at 4:00 PM, Thomas Kluyver <email@example.com> wrote:
> > On 2 July 2013 07:47, Ralf Gommers <firstname.lastname@example.org> wrote:
> >> Please keep in mind that it's much more important to you, as an active
> >> who cares about 3.x adoption, then to them. All newcomers are getting
> >> now is some compatibility issues and strings they don't understand. On
> >> upside they don't have to move a few years later, but the business case
> >> thin.
> > I'm not just doing this to cheerlead Python 3 adoption. Many of us have
> > newcomers being confused by the split. I don't have references handy, but
> > I've heard about courses that have asked people to preinstall Python, and
> > despite careful instructions, people have turned up with a mixture of
> > 2 and Python 3, which then wastes valuable time while everyone gets to
> > same starting point. Discussion sites see regular 'should I use 2 or 3'
> > threads. And it's easy to imagine potential users who're evaluating
> > against alternative solutions, and get put off by the 2/3 split, though
> > probably don't hear from them.
> Agreeing with Thomas:
> Most of us when starting with a new software stack, look for the
> latest version. I guess this is because it's fun to use the latest
> stuff, and because it's annoying learning habits for stuff that will
> soon be deprecated or raise an error.
Good point. I always used to download the latest and greatest version of
everything in the expectation that it would be better ;)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SciPy-User