python 2 compatibility

[csplib]

python 2 compatibility

[ChrisJefferson]

We should decide on a set of platforms we want to function, and then do automated testing.

I suggest we move to supporting only python 3 (.2? .3?), on windows, linux and mac os x (which will I imagine mean we support python 3 everywhere).

[ozgurakgun]

One could use travis to do the automated testing on multiple platforms and python versions. It can be configured to run after every commit and for every pull request.

[Bilalh]

@ozgurakgun I was actually planing to use travis at some point

[turingfan]

I think Chris’s point is that there’s basically no benefit to supporting Python 2.

From: ozgurakgun <[email protected]mailto:[email protected]>
Reply-To: csplib/csplib <[email protected]mailto:[email protected]>
Date: Tuesday, 20 May 2014 11:46
To: csplib/csplib <[email protected]mailto:[email protected]>
Subject: {Disarmed} Re: [csplib] python 2 compatibility (#7)

One could use travishttps://travis-ci.org to do the automated testing on multiple platforms and python versions. It can be configured to run after every commit and for every pull request.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-43610672.

[ozgurakgun]

@turingfan That's probably true, I wouldn't know. Still, (a system like) travis can be used to test with various 3.x versions without too much hassle.

[ChrisJefferson]

The main problem with csplib is deciding what 'built correctly' means. Obviously we can check if there are no errors, but it's probably better to choose some version which is "canonical", and see if everything else can build an identical website. I don't know how easy that is to do in travis, although I'm sure it's possible.

[ChrisJefferson]

We decided to officially do away with support for python 2, to keep ourselves sane.