Skip to content

Update support for Python 2.6+ #178

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

Closed
wants to merge 4 commits into from

Conversation

rickhanlonii
Copy link
Collaborator

As discussed here, there's a discussion to drop support for Python 2.4.

This pull takes the first step by updating the README, removing pre-2.6 library imports, and 2.6+ style exception syntax.

Moved #177 to develop branch here.

@jaitaiwan
Copy link
Contributor

LGTM @joestump

@hayd
Copy link

hayd commented Jul 30, 2015

Is 2.5 even supportable? Travis doesn't run it so it'll never be ci tested.

I thought the new exception as syntax was backported to 2.6+ only...

@joestump
Copy link
Owner

I agree with @hayd. Honestly we should probably discuss a 2.6 EOL at some point in the next 12-18 months. I say we go 2.6+

@jaitaiwan
Copy link
Contributor

I hadn't realised that. I agree also...

@rickhanlonii
Copy link
Collaborator Author

I confirmed that tests currently pass under 2.5, but you have to install an old version of mock to run them.

I'm not particularly persuaded to drop a version because of the CI used, but the exception syntax makes it really difficult to move forward.

So altogether, I support dropping 2.5 as well.

I'll update this PR.

@rickhanlonii rickhanlonii changed the title Update README to only support python 2.5+ Update support for Python 2.6+ Jul 31, 2015
@rickhanlonii
Copy link
Collaborator Author

This PR now updates README to 2.6+, removes pre-2.6 library imports, and uses 2.6+ style exception syntax.

@jaitaiwan @joestump this can go. I'm going to work on getting the 3.3 and 3.4 tests to pass.

@hayd
Copy link

hayd commented Jul 31, 2015

There's going to be many merge conflicts in resolving these (e.g. the exception as syntax). We should fix up/merge #142 first.

@joestump
Copy link
Owner

joestump commented Aug 2, 2015

I concur with @hayd. We should get PT3K merged in first. Also @jaitaiwan you should release what we have in master if you're comfortable as 1.9-RC1 IMO.

@jaitaiwan
Copy link
Contributor

Ok, @rickhanlonii are you happy for current master to be 1.9-RC1?

@rickhanlonii
Copy link
Collaborator Author

Yeah I'm good with that.

@jaitaiwan jaitaiwan force-pushed the develop branch 2 times, most recently from a660e24 to ea42271 Compare September 12, 2015 12:05
@jaitaiwan
Copy link
Contributor

@rickhanlonii probably need this updated since we've released 1.9

@rickhanlonii
Copy link
Collaborator Author

This is no longer relevant. README.md was already updated with the correct versions and syntax has been updated.

@rickhanlonii rickhanlonii deleted the rh-readme-update branch March 3, 2016 02:02
@@ -460,7 +449,7 @@ def get_normalized_parameters(self):
else:
try:
value = list(value)
except TypeError, e:
except TypeError as e:
assert 'is not iterable' in str(e)
items.append((to_utf8_if_string(key), to_utf8_if_string(value)))

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • E501 line too long (114 > 79 characters)

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

Successfully merging this pull request may close these issues.

5 participants