Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #72060

Re: Build tools, and Python 3 dependencies (was: How keep Python 3 moving forward)

From Roy Smith <roy@panix.com>
Newsgroups comp.lang.python
Subject Re: Build tools, and Python 3 dependencies (was: How keep Python 3 moving forward)
Date 2014-05-26 08:44 -0400
Organization PANIX Public Access Internet and UNIX, NYC
Message-ID <roy-0F23A3.08445126052014@news.panix.com> (permalink)
References <mailman.10254.1400876180.18130.python-list@python.org> <roy-F214F1.19572423052014@news.panix.com> <mailman.10285.1401009964.18130.python-list@python.org> <roy-34168F.14034325052014@news.panix.com> <mailman.10329.1401074189.18130.python-list@python.org>

Show all headers | View raw


In article <mailman.10329.1401074189.18130.python-list@python.org>,
 Ben Finney <ben@benfinney.id.au> wrote:

> Roy Smith <roy@panix.com> writes:
> 
> > Stefan Behnel <stefan_ml@behnel.de> 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 to
> > maintain two different versions of Python
> 
> Why would using Fabric – a build tool – require you to “maintain two
> different versions of Python”? You only need to maintain the build
> scripts, not Python itself.

Because to run these tools, we need have both versions installed on 
every machine.  So, we don't need to maintain Python in the sense of 
building it from source, but we do need to have our deployment scripts 
install it everyplace it's needed (or, at least, make sure it's 
installed as part of some base deployment package)

> > and test everything against both.
> 
> 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 testing dependencies.

The are tightly integrated, and share code.

> At least one of us seems to be misunderstanding what is required.

Yes :-)

When you start working with large systems, reducing complexity becomes 
important.  Every time you add a component, it comes with its own set of 
dependencies and constraints.  Those things come back to bite you when 
you least expect it.

Back to comp.lang.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

How keep Python 3 moving forward Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-05-23 21:16 +0100
  Re: How keep Python 3 moving forward Roy Smith <roy@panix.com> - 2014-05-23 19:57 -0400
    Re: How keep Python 3 moving forward Ethan Furman <ethan@stoneleaf.us> - 2014-05-23 17:27 -0700
      Re: How keep Python 3 moving forward Roy Smith <roy@panix.com> - 2014-05-23 21:12 -0400
    Python 3 support for Fabric (was: How keep Python 3 moving forward) Ben Finney <ben@benfinney.id.au> - 2014-05-24 14:29 +1000
    Re: How keep Python 3 moving forward - suds & Python 3 Jurko Gospodnetić <jurko.gospodnetic@pke.hr> - 2014-05-25 10:54 +0200
    Re: How keep Python 3 moving forward Stefan Behnel <stefan_ml@behnel.de> - 2014-05-25 11:25 +0200
      Re: How keep Python 3 moving forward Roy Smith <roy@panix.com> - 2014-05-25 14:03 -0400
        Build tools, and Python 3 dependencies (was: How keep Python 3 moving forward) Ben Finney <ben@benfinney.id.au> - 2014-05-26 13:16 +1000
          Re: Build tools, and Python 3 dependencies (was: How keep Python 3 moving forward) Roy Smith <roy@panix.com> - 2014-05-26 08:44 -0400
            Re: Build tools, and Python 3 dependencies (was: How keep Python 3 moving forward) Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-05-27 02:59 +0000
              Re: Build tools, and Python 3 dependencies (was: How keep Python 3 moving forward) Rustom Mody <rustompmody@gmail.com> - 2014-05-26 20:54 -0700
            Re: Build tools, and Python 3 dependencies (was: How keep Python 3 moving forward) Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-05-27 03:06 +0000
  Re: How keep Python 3 moving forward wxjmfauth@gmail.com - 2014-05-24 00:13 -0700
    Re: How keep Python 3 moving forward blindanagram <noone@nowhere.net> - 2014-05-24 15:35 +0100
      Re: How keep Python 3 moving forward Marko Rauhamaa <marko@pacujo.net> - 2014-05-24 12:59 +0300
        Re: How keep Python 3 moving forward Rustom Mody <rustompmody@gmail.com> - 2014-05-24 03:40 -0700
        Re: How keep Python 3 moving forward Devin Jeanpierre <jeanpierreda@gmail.com> - 2014-05-24 09:03 -0700
          Re: How keep Python 3 moving forward Marko Rauhamaa <marko@pacujo.net> - 2014-05-24 22:49 +0300
            Re: How keep Python 3 moving forward Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-05-24 21:11 +0100
            Re: How keep Python 3 moving forward Terry Reedy <tjreedy@udel.edu> - 2014-05-24 20:27 -0400
              Re: How keep Python 3 moving forward wxjmfauth@gmail.com - 2014-05-24 23:43 -0700
                Re: How keep Python 3 moving forward Ethan Furman <ethan@stoneleaf.us> - 2014-05-25 08:21 -0700
                Re: How keep Python 3 moving forward Rustom Mody <rustompmody@gmail.com> - 2014-05-25 10:38 -0700
                Re: How keep Python 3 moving forward Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-05-25 18:17 +0000
                Re: How keep Python 3 moving forward Tim Chase <python.list@tim.thechases.com> - 2014-05-25 13:56 -0500
                Re: How keep Python 3 moving forward Ethan Furman <ethan@stoneleaf.us> - 2014-05-25 13:18 -0700
                Re: How keep Python 3 moving forward Ethan Furman <ethan@stoneleaf.us> - 2014-05-25 11:34 -0700
                Re: How keep Python 3 moving forward Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-05-25 21:24 +0100
                Re: How keep Python 3 moving forward Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-05-25 18:22 -0400
                Re: How keep Python 3 moving forward Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-05-26 00:09 +0100
                Re: How keep Python 3 moving forward wxjmfauth@gmail.com - 2014-05-26 07:03 -0700
                Re: How keep Python 3 moving forward Chris Angelico <rosuav@gmail.com> - 2014-05-26 10:24 +1000
                Re: How keep Python 3 moving forward Ethan Furman <ethan@stoneleaf.us> - 2014-05-25 17:32 -0700
                Re: How keep Python 3 moving forward Chris Angelico <rosuav@gmail.com> - 2014-05-26 01:52 +1000
                Re: How keep Python 3 moving forward Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-05-25 17:32 +0100
                Re: How keep Python 3 moving forward Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2014-05-25 18:20 -0400
                Re: How keep Python 3 moving forward Terry Reedy <tjreedy@udel.edu> - 2014-05-25 21:32 -0400
        Re: How keep Python 3 moving forward Ethan Furman <ethan@stoneleaf.us> - 2014-05-24 12:08 -0700
        Re: How keep Python 3 moving forward Stefan Behnel <stefan_ml@behnel.de> - 2014-05-24 21:44 +0200
      Re: How keep Python 3 moving forward Travis Griggs <travisgriggs@gmail.com> - 2014-05-24 11:02 -0700
      Re: How keep Python 3 moving forward Gene Heskett <gheskett@wdtv.com> - 2014-05-25 20:45 -0400
    Re: How keep Python 3 moving forward Grant Edwards <invalid@invalid.invalid> - 2014-05-24 14:06 +0000

csiph-web