-
Notifications
You must be signed in to change notification settings - Fork 8
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
Determine Python version support #16
Comments
Also, if the answer is 2 but it would be trivial to support 3, I think we should consider it. It's a fairly simple module. |
The code was not compatible with Python 3 before because of a few minor issues, but I have just put up a pull request #18 to fix that. One thing that I do not know about is how to support testing of both languages in the same project (I don't expect that it is difficult, I just don't know how to do it). |
From what I've seen thus far, other Python modules I've had to dig into use Tox for testing against multiple versions. Others may have more experience here though. /cc @steventlamb |
My experience is limited, I attempted to support python3 with django-queryset-csv, but backed out due to some stickiness with how the two different languages handled unicode, IIRC. However, when I was doing it, my strategy for testing was to rely on a free-for-FOSS cloud CI service like travisCI. Then, it's as simple as updating your I have no experience with Tox. If you're not going to free this repo, then I don't have much to offer. However, why would you bother supporting two different versions of python if this isn't going to be a public repo? |
That's the plan here too once we settle on a license. The main driver for something like Tox is to support local testing across versions as well. For Travis, the build matrix would be driven by overrides to |
Is this done? |
This is primarily to advertise the correct package classifiers on PyPI:
The text was updated successfully, but these errors were encountered: