Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backwards Compatibility #2

Closed
isislovecruft opened this issue Apr 16, 2012 · 2 comments
Closed

Backwards Compatibility #2

isislovecruft opened this issue Apr 16, 2012 · 2 comments
Labels
question for open questions

Comments

@isislovecruft
Copy link
Contributor

Are we writing for Python >= 2.6?

What if I want to use something that is new to 2.7, should I just take the code I need and put it into utils? I ask because I want the namedtuple, OrderedDict, and Counter classes from the collections module but the later two classes are new to 2.7.

@hellais
Copy link
Member

hellais commented Apr 16, 2012

I think that we should keep backward compatibility with 2.6 for at least the core of OONI.

If you want to use something for a test that is 2.7 and there is no other way to do it with >= 2.6 then go for it, but keep in mind that this will impact it's usability across platforms.

@isislovecruft
Copy link
Contributor Author

Ok, sounds reasonable. Where something new to 2.7 is small and modular, as in the case of namedtuple, I'll just add it to utils and import from there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question for open questions
Projects
None yet
Development

No branches or pull requests

2 participants