Python3

[GoogleCodeExporter]

please support python3.2

thank you,
-david

Original issue reported on code.google.com by firefigh...@gmail.com on 17 Sep 2011 at 6:42

[GoogleCodeExporter]

Original comment by jcgregorio@google.com on 30 Oct 2011 at 3:34

• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

One reason to consider Python3 is SNI support, which will be come more relevant 
with SNI-requiring proxy servers.

Original comment by nherr...@google.com on 5 Mar 2013 at 11:28

[GoogleCodeExporter]

And Python2 will never get SNI support: http://bugs.python.org/issue5639

Original comment by nherr...@google.com on 5 Mar 2013 at 11:38

[GoogleCodeExporter]

I too would like to see Python3 Support.

Original comment by AcidTo...@gmail.com on 25 Jul 2013 at 3:18

[GoogleCodeExporter]

would also be useful for integration in sublime text 3 plugins (eg: 
sublimetext-google-apps-scripts)

Original comment by jul...@revolunet.com on 9 Nov 2013 at 1:03

[GoogleCodeExporter]

Please add Python 3 support as soon as possible.

Original comment by nkchhantyal on 24 Jun 2014 at 11:30

[GoogleCodeExporter]

Can someone suggest a Python-3-supporting alternative for this package? I can't 
use it because my project is on Python 3.4.

Original comment by ram.rac...@gmail.com on 10 Jul 2014 at 1:53

[GoogleCodeExporter]

https://github.com/enorvelle/GoogleApiPython3x

Original comment by songofacandy on 10 Jul 2014 at 2:03

[GoogleCodeExporter]

Is there any official word from Google on when there will be official support 
for Python 3.x?

It seems a bit strange that they haven't said much, and the priority for this 
ticket is marked as "Low".

For our particular use case, Python3 support is fairly pertinent, since we need 
to interface with JIRA via SSL, and this setup requires SNI support, which 
Python 2.x doesn't have - i.e.:

http://docs.python-requests.org/en/latest/community/faq/#what-are-hostname-doesn
-t-match-errors

Original comment by victorh...@gmail.com on 8 Dec 2014 at 3:37

[GoogleCodeExporter]

Hello,

This repository is no longer in use, we now host the project here:
https://github.com/googleads/googleads-python-legacy-lib/

Another thing to note is that this client library (adspygoogle) is deprecated; 
we announced this a while back on the Google Ads Developers Blog. It will be 
sunset on January 5th, 2015. Although it won't immediately cease working, this 
just means that we'll stop updating it as of that date.

Finally, we have a new client library called googleads that we released a while 
ago that is replacing this one. Most importantly for your use case, it does 
support Python 3. I'd suggest you check out the migration guide:
https://github.com/googleads/googleads-python-lib/wiki/Migrating-from-adspygoogl
e-to-googleads

Original comment by msanisca...@google.com on 8 Dec 2014 at 12:59

[GoogleCodeExporter]

As far as I know, this is not just the adspygoogle project. This is the Google 
APIs client for all of the discovery-based APIs, and as such, this bug is still 
relevant.

Original comment by nherr...@google.com on 8 Dec 2014 at 3:59

[GoogleCodeExporter]

Whoops, looks like I got ahead of myself there. Yes, you're right, this looked 
similar to an issue we had for our old client libs and I mistook it for that.

That said, the issue should be brought up on the github repo if it is still 
applicable:
https://github.com/google/google-api-python-client

Original comment by msanisca...@google.com on 8 Dec 2014 at 4:08