-
Notifications
You must be signed in to change notification settings - Fork 0
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
Cleanup and 3.x compatibility #5
Merged
Merged
Changes from 6 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
b8a2d6d
make lispify py3-compatible
chsamlee beba015
Merge branch 'master' into py3-compat
chsamlee e4cd22a
Fix style issue
chsamlee 03581a1
Fix import problem in 2.x
chsamlee 18d2d65
Use future for compatibility
chsamlee caca086
Fix 2.6 test problem by using unittest2
chsamlee 982513e
Fix docs, remove unneeded code, add tests and 2.6 support
chsamlee ef31709
F**k 2.6, better not run into more errors
chsamlee f468423
I want to drop 2.6 support...
chsamlee d71114a
Merge branch 'master' into py3-compat
chsamlee b7b3b85
Update README.md
chsamlee File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
# Lispify [![Build Status](https://travis-ci.org/infolab-csail/lispify.svg?branch=master)](https://travis-ci.org/infolab-csail/lispify) [![codecov](https://codecov.io/gh/infolab-csail/lispify/branch/master/graph/badge.svg)](https://codecov.io/gh/infolab-csail/lispify) | ||
Lispify converts Python objects into Lisp-like encoded strings that are interpretable in Common Lisp. | ||
Lispify converts Python objects into Lisp-like encoded strings that are interpretable in Common Lisp. This library requires Python 2.6, 2.7, or 3.3+. | ||
|
||
## Releases | ||
|
||
|
@@ -12,3 +12,4 @@ Version numbers `MAJOR.MINOR.PATCH` should follow a system inspired by [semantic | |
1. PATCH version when you make backwards-compatible bug fixes. | ||
|
||
Create a [release](https://help.github.com/articles/creating-releases/) on Github for each new version. | ||
>>>>>>> master | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. delete |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
future==0.15.2 | ||
unittest2==1.1.0 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd be nice to have travis build across all versions of python:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we should support 3.2 because very few people use it and 3.2 compatibility is more complicated: the
u'unicode string'
was removed in 3.0 and only readded in 3.3.Given that travis relies on volunteers for computing resources, I don't think we should have a build for every version. I think 2.7, 3.3, and nightly should be enough, and maybe 2.6 if that is necessary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, that sounds reasonable. Why don't you update the README with a list of supported Python versions so that it's clear.
I wouldn't worry about that too much. Millions of projects use Travis, and us using a few more builds is not going to make a difference.
Given my above reasoning, how about
2.6
,3.3
,3.4
,3.5
,3.5-dev
, andnightly
? I think2.6
might not havecodecov
. If that's the case, omit thecodecov
step. I'm not too keen on2.6
, so if it's causing lots of problems, don't worry about it. But the other versions I listed I think we should try to support if possible.