Python 3

[rozling]

Request for Python 3 support (continuing on from https://code.google.com/p/google-api-python-client/issues/detail?id=57). My use case is for using the popular editor Sublime Text 3 to interact with the Google API.

[craigcitro]

This is on our radar, but we don't have any concrete plans right now. I'm going to tag this "enhancement" for now, so people don't keep reopening.

[ianjosephwilson]

I also need python3 support since I started a project with python3 and now I want google+ sigin and access to google contacts. Here is the google document which lists the google api python client as needed for the g+ signin implementation, see step 8: https://developers.google.com/+/web/signin/server-side-flow

It seems that there are two strategies:

1. separate code bases for python2 and python3
   • here is a good implementation of that in one of this library's dependencies:
     • https://github.com/jcgregorio/httplib2
   • this is probably the safest approach if backwards compatibility is the number 1 concern
2. combined code base that supports both python2 and python3
   • here is a good implementation and the framework I am using in Python3
     • https://github.com/Pylons/pyramid

It seems that no actual python dependency is listed for either google-api-python-client or oauth2client. The python documentation states that limiting support to Python 2.6+ will make strategy 2, a combined code base, easier:
https://docs.python.org/3/howto/pyporting.html#try-to-support-python-2-6-and-newer-only

Seeing python3 support as inevitable if a high level path is chosen now then others can start contributing.

[craigcitro]

@ianjosephwilson i'm with you that we ultimately want a plan for moving to python 3 -- it also has to include oauth2client, and any other moving parts underneath. i'm happy to kick around ideas, but we don't have any sort of timeframe in mind just yet.

[ianjosephwilson]

@craigcitro I think same trick used in httplib2 could be used to choose the correct oauth2client lib if oauth2client used separate folders for python2 and python3. For example:

src_dir = 'python%s' % sys.version_info[0]
package_dir={
    'oauth2client':'oauth2client/' + src_dir + '/oauth2client',
    'uritemplate':'oauth2client/' + src_dir + /uritemplate',
}

So I don't think the embedding requirement will be limiting in choosing between strategies 1 and 2 I mentioned earlier.

What is the minimum python version that must be supported?

[craigcitro]

2.6 is fine for a minimum version.

[ianjosephwilson]

Maybe updating each repo in place to work with both python 2.6+ and python 3.2+ would be the best option then, strategy 2.

Can a depedency on six be added? It is discussed in the python docs here: https://docs.python.org/3/howto/pyporting.html#projects-to-consider

[JelteF]

There seems to be a python3 compatible unofficial clone: https://github.com/enorvelle/GoogleApiPython3x

[esistgut]

+1

[dustinfarris]

wait.. google doesn't support python3?

[JelteF]

Yeah, it's ridiculous
On Aug 14, 2014 11:10 PM, "Dustin Farris" notifications@github.com wrote:

wait.. google doesn't support python3?

—
Reply to this email directly or view it on GitHub
#3 (comment)
.

[slessans]

its unbelievable. and theres not even concrete plans it seems like...

[dustinfarris]

dammit, google 👎