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

python 3 support #53

Open
pkit opened this issue Jul 6, 2014 · 5 comments
Open

python 3 support #53

pkit opened this issue Jul 6, 2014 · 5 comments

Comments

@pkit
Copy link
Member

pkit commented Jul 6, 2014

According to this one https://wiki.ubuntu.com/Python/3 we don't really need to support python 3 anywhere in the future
Because python community has problems understanding what "backwards compatibility" means I'm not going to test my changes on any python3 stuff
Therefore if somebody wants to support it, I suggest creating zerovm-cli-python3 repo
Will drop py3 from tox.ini unless I get clear explanation why we need it.

@mgeisler
Copy link
Contributor

mgeisler commented Jul 7, 2014

Therefore if somebody wants to support it, I suggest creating zerovm-cli-python3 repo

Please don't create new repositories under the zerovm team — we should instead cleanup the existing ones.

Will drop py3 from tox.ini unless I get clear explanation why we need it.

We have Python 3 support because Python 3 is the future. If we don't support Python 3 now, we will see requests to begin supporting it later. I have seen this with Mercurial: it is Python 2.x only and we get complains on the mailinglist from people who run systems with Python 3 only.

Adding support for Python 3 is easy with new code like ours. If we wait a year or two, we will have to deal with all the compatibility problems at once — it is normally easier to deal with them one commit at a time.

@pkit
Copy link
Member Author

pkit commented Jul 7, 2014

We have Python 3 support because Python 3 is the future.

Very distant one at that.

we will see requests to begin supporting it later.

It's Open Source, fork it and support python 3 all the way around.

Adding support for Python 3 is easy with new code like ours.

I don't see anything "easy" in creating dependency on some strange compatibility module that does some even stranger things under the hood.
And the whole 3.2 incompatible with 3.3 incompatible with 3.4 circus is very entertaining only when you look at it with an entomological interest. Not when you have to support it first hand.

@mgeisler
Copy link
Contributor

mgeisler commented Jul 7, 2014

And the whole 3.2 incompatible with 3.3 incompatible with 3.4 circus is very entertaining only when you look at it with an entomological interest. Not when you have to support it first hand.

Heh, yeah :-) I'm happy not to support Python 3.2. As far as I can tell, it was never deployed very widely. Python 3.3 and 3.4 will see much wider use, so that's what we're targeting in zpm.

@pkit
Copy link
Member Author

pkit commented Jul 7, 2014

I think I will drop support for 3 in zvsh anyway. The "unified zerovm cli" can reinstate support for any type of python, but zvsh, as a tool for testing, will stay python 2 only. I don't see a problem here.

@mgeisler
Copy link
Contributor

mgeisler commented Jul 7, 2014

Hey, I tried discussing this on IRC :) We can drop support as we wish, but I prefer to keep compatibility if we can.

larsbutler pushed a commit to larsbutler/zerovm-cli that referenced this issue Jan 7, 2015
miniswift: add docs to SwiftClient/ZwiftClient
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

No branches or pull requests

2 participants