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


Groups > comp.lang.python > #36753

Re: pylint or similar to test version-specific language constructs?

References <1454e34f-5ca0-4f49-ad29-c99df4fdd322@gu9g2000vbb.googlegroups.com> <mailman.349.1357776502.2939.python-list@python.org> <QeednQoFKKHXUHLNnZ2dnUVZ8gadnZ2d@brightview.co.uk> <mailman.401.1357916818.2939.python-list@python.org> <fc8295cd-e226-42e5-ad1e-ddc81a5303a3@c14g2000vbd.googlegroups.com>
Date 2013-01-14 07:59 +1100
Subject Re: pylint or similar to test version-specific language constructs?
From Chris Angelico <rosuav@gmail.com>
Newsgroups comp.lang.python
Message-ID <mailman.479.1358110759.2939.python-list@python.org> (permalink)

Show all headers | View raw


On Mon, Jan 14, 2013 at 4:56 AM, jkn <jkn_gg@nicorp.f9.co.uk> wrote:
> Hi Dave
>
> On 11 Jan, 15:06, Dave Angel <d...@davea.name> wrote:
>>
>> Not sure what you mean by beforehand.  Don't you run all your unit tests
>> before putting each revision of your code into production?  So run those
>> tests twice, once on 2.7, and once on 2.4.  A unit test that's testing
>> code with a ternary operator will fail, without any need for a separate
>> test.
>>
>> if it doesn't, then you've got some coverage gaps in your unit tests.
>
> By 'beforehand' I meant 'before testing on my target 2.4 system;
> perhaps I should have been clearer in that I am running 2.7 on my
> 'development' platform, and 2.4 on my target. It would be painful to
> put 2.4 on my target system (although I continue to wonder about
> that...). So I was looking to catch such errors before migrating to
> the target.

Painful to put 2.4 on your dev, you mean? I've never done it, but I
would expect that the old sources will compile against newer libraries
with no problems.

That's likely to be the easiest option. It's the language-level
equivalent of watching for a thrown exception rather than asking
forgiveness beforehand :)

ChrisA

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


Thread

pylint or similar to test version-specific language constructs? jkn <jkn_gg@nicorp.f9.co.uk> - 2013-01-09 15:45 -0800
  Re: pylint or similar to test version-specific language constructs? Gisle Vanem <gvanem@broadpark.no> - 2013-01-10 01:07 +0100
    Re: pylint or similar to test version-specific language constructs? The Night Tripper <jkn+gg@nicorp.co.uk> - 2013-01-11 08:29 +0000
      Re: pylint or similar to test version-specific language constructs? Terry Reedy <tjreedy@udel.edu> - 2013-01-11 08:38 -0500
      Re: pylint or similar to test version-specific language constructs? Dave Angel <d@davea.name> - 2013-01-11 10:06 -0500
        Re: pylint or similar to test version-specific language constructs? Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-01-11 15:37 +0000
          Re: pylint or similar to test version-specific language constructs? Dave Angel <d@davea.name> - 2013-01-11 11:09 -0500
        Re: pylint or similar to test version-specific language constructs? jkn <jkn_gg@nicorp.f9.co.uk> - 2013-01-13 09:56 -0800
          Re: pylint or similar to test version-specific language constructs? Chris Angelico <rosuav@gmail.com> - 2013-01-14 07:59 +1100
  Re: pylint or similar to test version-specific language constructs? thenault@gmail.com - 2013-01-11 00:35 -0800

csiph-web