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

Updated elisaviihde.py to be python3 compatible #16

Merged
merged 1 commit into from Dec 13, 2015

Conversation

Tomin1
Copy link

@Tomin1 Tomin1 commented Dec 12, 2015

Updated elisaviihde.py to be python3 compatible. The code is still compatible
with python2.

Replaces #15.

Updated elisaviihde.py python3 compatible. The code is still compatible
with python2.
enyone added a commit that referenced this pull request Dec 13, 2015
Updated elisaviihde.py to be python3 compatible
@enyone enyone merged commit 5725c3d into enyone:pre-1.5 Dec 13, 2015
@enyone
Copy link
Owner

enyone commented Dec 13, 2015

With what version of python3 was this tested? (just to add it to TravisCI and README.md)

@Tomin1
Copy link
Author

Tomin1 commented Dec 13, 2015

I used 3.5.1 on my laptop, but I think it should work with any 3.x version.

@enyone
Copy link
Owner

enyone commented Dec 13, 2015

Nose tests didn't like 3.5 :( Seems to be a problem in requests module. Any ideas?
https://travis-ci.org/enyone/elisaviihde/jobs/96555689

@Tomin1
Copy link
Author

Tomin1 commented Dec 13, 2015

Well, it's obvious I didn't do any unit tests, just some smoke testing with my own scripts and there it seemed to work. Anyway it seems that testing code (httmock) does something differently than the real api. I'm not very familiar with httmock. It looks like there is (or was) some code on httmock to prevent this but there might be some bugs left.
httmock unit test: https://github.com/patrys/httmock/blob/master/tests.py#L222

You might want to use 3.4 as that is the latest requests and httmock really support. I used that version of oython (3.4.3) on my server probably did equal amount of testing elisaviihde.py on it (compared to testing done with 3.5.1 on my laptop). Anyway, the unit tests aren't going to work on 3.4 either.

@enyone
Copy link
Owner

enyone commented Dec 13, 2015

Python community has ruined itself making things not being backward compatible. I will mark Python3 support as experimental as long as unit tests are fixed.

@enyone
Copy link
Owner

enyone commented Dec 13, 2015

Opened bug #17

@Tomin1 Tomin1 deleted the python3 branch January 23, 2016 23:00
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.

None yet

2 participants