On Tuesday, May 27, 2014 8:29:13 AM UTC+5:30, Steven D'Aprano wrote:
> On Mon, 26 May 2014 08:44:51 -0400, Roy Smith wrote:
>
>
>
> >> That makes even less sense. The build system runs under whatever
>
> >> version of Python it needs, and your code runs under whatever version
>
> >> of Python
Oh, I was a bit trigger-happy with my earlier post.
On Mon, 26 May 2014 08:44:51 -0400, Roy Smith wrote about his build
system and production code:
> The are tightly integrated, and share code.
[...]
> When you start working with large systems, reducing complexity becomes
> important. Every t
On Mon, 26 May 2014 08:44:51 -0400, Roy Smith wrote:
>> That makes even less sense. The build system runs under whatever
>> version of Python it needs, and your code runs under whatever version
>> of Python you like. The two don't affect each other at run time, and
>> don't affect each other's tes
In article ,
Ben Finney wrote:
> Roy Smith writes:
>
> > Stefan Behnel wrote:
> >
> > > And I don't really see why you would consider fabric a dependency
> > > that keeps you from switching to Py3. In many cases, you can just
> > > keep running it in Py2 as you did before.
> >
> > In theory,
Roy Smith writes:
> Stefan Behnel wrote:
>
> > And I don't really see why you would consider fabric a dependency
> > that keeps you from switching to Py3. In many cases, you can just
> > keep running it in Py2 as you did before.
>
> In theory, that's possible. In practice, it would mean having t
