Skip to content

Conversation

sbyrnes321
Copy link

All files now use from __future__ import absolute_import, and the Python 3 absolute vs relative import syntax.

After this change, colorpy.test.test() shows all tests passing in both Python 2.7 and Python 3.5 on my computer.

[Copied out of https://github.com/fish2000/ColorPy/pull/2 where I got colorpy running in Python 3 back in Feb 2014, not realizing it was a third-party repository!]

All files now use "from __future__ import absolute_import"
@sbyrnes321
Copy link
Author

Any comment? Colorpy is a really nice package, and so close to being usable in Python 3. it would be great if you could just make this small change and then re-upload to pypi.

@markkness
Copy link
Owner

markkness commented Apr 27, 2017 via email

@sbyrnes321
Copy link
Author

Oh, I didn't realize that you weren't the PyPI owner. It looks like the PyPI owner is @fish2000. His repository is already python-3-compatible (thanks to my pull request!) so I just asked him to re-upload to PyPI. ( fish2000/ColorPy#5 )

Well, if you want, you can ask @fish2000 for ownership of the PyPI entry, I think you're kinda entitled to it. Or upload it under a different name. Or just forget about it: I don't think there are any substantive differences between his version and yours. (Unless I'm missing something.)

@daviddoji
Copy link

Is it then your master branch compatible with Python 3.6? Or should I use the one from @sbyrnes321??

Thanks in advance for this great package!

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.

3 participants