Only works with Python 2.7? #6

tiagofassoni · 2016-02-10T17:03:43Z

First of all, awesome work, folks! Really liked it and intend to use.

This is more of a reminder for the README, because, when reading the code, I saw "python2.7" hardcoded and I figured it would be best to write that in the README

Miserlou · 2016-02-10T17:08:59Z

The problem is that Lambda itself only supports Python 2.7 for now.

I don't think there's any reason why it wouldn't work on P3, but the
target is what AWS supports.

On Wed, Feb 10, 2016 at 6:03 PM, Tiago Fassoni notifications@github.com
wrote:

First of all, awesome work, folks! Really liked it and intend to use.

This is more of a reminder for the README, because, when reading the code,
I saw "python2.7" hardcoded and I figured it would be best to write that in
the README

—
Reply to this email directly or view it on GitHub
#6.

tiagofassoni · 2016-02-10T19:12:31Z

Oops. Totally forgot about that. Mind if I update the README to write about that “limitation"?

On Feb 10, 2016, at 3:09 PM, Rich Jones notifications@github.com wrote:

The problem is that Lambda itself only supports Python 2.7 for now.

I don't think there's any reason why it wouldn't work on P3, but the
target is what AWS supports.

On Wed, Feb 10, 2016 at 6:03 PM, Tiago Fassoni notifications@github.com
wrote:

First of all, awesome work, folks! Really liked it and intend to use.

This is more of a reminder for the README, because, when reading the code,
I saw "python2.7" hardcoded and I figured it would be best to write that in
the README

—
Reply to this email directly or view it on GitHub
#6.

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

Miserlou · 2016-02-11T11:19:25Z

So, I was thinking more about this, and only the stuff that actually runs AWS side needs to be Py2.7.

All the rest can be Python3. However, this means that the tests need to be aware that some functions should only be tested on the target platform. Do you know how to do that with Travis?

tiagofassoni · 2016-02-17T22:05:52Z

Well, I have absolutely no idea, sorry.

mathom · 2016-02-20T21:53:50Z

I believe you could run Python 3 on lambda if you really wanted but you would have to ship a statically compiled version of the python binary along with your code. Sounds pretty gross, though.

Miserlou · 2016-02-21T14:50:42Z

That's a nightmarish idea.. not supporting that! :-P

Honestly I expect that Lambda will support multiple Python versions in the next 12 months. Screenshot this and we'll come back to it in a year to see if I was right..

Miserlou · 2016-02-21T14:51:33Z

That being said, I think we should target 3.5 for all of the local Zappa tools (although I don't know what that will do to the venv packaging stuff. Could relate to our idea to pass custom venvs through the ZAPPA_SETTINGS.)

maljac · 2016-04-09T21:00:54Z

Sidenote: I was not able to use zappa with Python 2.7.6 (SSL / Insecure.. warnings from urllib3). With 2.7.11 I had no problems. Maybe you should put this in the Readme as requirement.

Miserlou · 2016-04-09T21:03:53Z

That's interesting. I think that comes because you need to install requests[security] on pythons.

hayd · 2016-05-09T08:14:45Z

FWIW Here's some work towards py3 https://github.com/hayd/Zappa/tree/py3. IIUC it's all for nought while lambda in python 2.7 only, but may be worth testing out early anyway.

Note: Some unicode handling became a little messier in a few places, but a lot of this could be cleaned up (for one thing by defining b64encode on str).

xuru · 2016-08-10T21:49:07Z

Hey guys... we can always add a compat.py file to allow python2.7/python3.5 compatibility functions. That way we'll be ready when it happens.

Miserlou · 2016-08-10T22:17:47Z

Can you elaborate more on that, @xuru ? I'm not familiar with that pattern.

xuru · 2016-08-11T18:08:39Z

I was thinking of the Flask cookiecutter repo https://github.com/sloria/cookiecutter-flask/blob/master/%7B%7Bcookiecutter.app_name%7D%7D/%7B%7Bcookiecutter.app_name%7D%7D/compat.py

Miserlou · 2016-08-11T18:38:51Z

That looks like voodoo to me..

hayd · 2016-08-11T22:41:48Z

I think the only thing that might want to go into a compat module is the b64encode/b64decode (to ensure this handles bytes/unicode consistently and correctly in py2 and py3). As you can see in the second commit above that's the majority of fiddly code repetition. I don't recall if that branch was passing py3 tests yet.

iJebus · 2016-08-24T16:06:00Z

Note that just actual 2.7 apparently won't do. I wasn't careful in using something recent (e.g. 2.7.12) and when I tried zappa deploy dev_api on the example project, I got the below. I didn't see this on 2.7.12 so, yup.

Packaging project as zip...
Uploading zip (4.4MiB)...
'ascii' codec can't encode character u'\u258e' in position 6: ordinal not in range(128)
Unable to upload to S3. Quitting.

Miserlou · 2016-08-24T16:23:27Z

Hmm. Interesting.

hayd · 2016-08-24T17:01:54Z

@iJebus Which version of python are you using? (The unicode handing should not be different between minor 2.7 versions...!!) Could that be dependent on the file (rather than the python version)? Or does precisely this same package work with 2.7.12?

xuru · 2016-11-23T19:12:02Z

I know this is a bit late in coming but there is a way to run python3 on lambda (it's a bit hackish, but it works): http://www.cloudtrek.com.au/blog/running-python-3-on-aws-lambda/

In my case, I have an API that I'm running in elastic beanstalk (so I get my python 3), but now I need to run some background processes on events from a 3rd party API. So in order to process those events, I need to modify the user object in dynamodb, and set a temporary password (long story). So right there, I have a problem, as now I have to have two copies of the user model, and also two spots that holds the password salt.

So I thought, I could have a paired down flask app.py with only the dynamodb stuff and the same settings file etc, as my main API, except I went the python 3 route...

Miserlou · 2016-11-23T20:16:49Z

Soooooo.. that's a really interesting idea. I'm into it.

However - is it worth building and maintaining that if official Python 3 support is right around the corner? Maybe we should talk more after reinvent..

nueverest · 2017-02-08T21:32:59Z

Could you provide an update on the status of Python 3 support? I would prefer it over 2.7.13

You can go to this AWS forum post to voice your support for python3.

c22 · 2017-02-13T00:27:16Z

@nueverest you should ask AWS when they're going to support Python3 on Lambda

mikespoff · 2017-02-23T23:43:05Z

I was really excited to use Zappa, but I've spent the past two days banging my head against an endless stream of problems. Now I realise that it was because Zappa only works on Python 2, and I'm using 3.

It would be very helpful to have a prominent warning up at the top of the readme saying something like, "Note: Because AWS Lambda currently only supports Python 2.7, Zappa also only runs on 2.7"

1oglop1 · 2017-03-07T19:33:30Z

I just hope that Djago will drop support for legacy python(2) soon enough.
This seems to be super interesting project and should not use legacy stuff :/

mathom · 2017-03-07T19:51:11Z

@1oglop1 Unfortunately there are a lot of projects out there that don't have python 3 support for various reasons. In this case, we're waiting on AWS to implement support.

As a brand new Zappa user, I wasted ~2 hours migrating from a local docker based environment to Virtual Env only to find out Zappa doesn't support 3.5 :-(. It looks like others have experienced the same thing too[0], so this PR is meant to the be a bare minimum notice that Python 3x is not supported. Down the road, it would be helpful to have a `zappa doctor` type command to validate/troubleshoot this stuff early on. Nonetheless, I'm still excited about this project so keep up the good work! [0] Miserlou#6

c22 · 2017-04-19T00:03:34Z

See #793

Miserlou · 2017-04-21T19:50:21Z

Python3 support has arrived! Try it out in 0.41.0! Please report any bugs you find! Nothing is guaranteed but it Works For Me™!

Miserlou added the enhancement label Feb 15, 2016

Miserlou mentioned this issue Nov 23, 2016

ImportError - unable to import Zappa #489

Closed

SBillion mentioned this issue Nov 30, 2016

Feature/support python35 #499

Closed

Miserlou mentioned this issue Dec 8, 2016

Allow Supplying Custom Python (including Python3) Runtimes #528

Closed

tsarpaul mentioned this issue Jan 1, 2017

Removed imp #577

Merged

iMerica mentioned this issue Mar 15, 2017

Adds Python version warning to README #719

Merged

nealmcb mentioned this issue Mar 22, 2017

Any chance of supporting Google App Engine or other serverless deployment environments? #733

Open

Miserlou closed this as completed Apr 21, 2017

Miserlou mentioned this issue May 19, 2017

Pull zappa's version into its own python module. #871

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Only works with Python 2.7? #6

Only works with Python 2.7? #6

tiagofassoni commented Feb 10, 2016

Miserlou commented Feb 10, 2016

tiagofassoni commented Feb 10, 2016

Miserlou commented Feb 11, 2016

tiagofassoni commented Feb 17, 2016

mathom commented Feb 20, 2016

Miserlou commented Feb 21, 2016

Miserlou commented Feb 21, 2016

maljac commented Apr 9, 2016

Miserlou commented Apr 9, 2016

hayd commented May 9, 2016

xuru commented Aug 10, 2016

Miserlou commented Aug 10, 2016

xuru commented Aug 11, 2016

Miserlou commented Aug 11, 2016

hayd commented Aug 11, 2016

iJebus commented Aug 24, 2016

Miserlou commented Aug 24, 2016

hayd commented Aug 24, 2016

xuru commented Nov 23, 2016

Miserlou commented Nov 23, 2016

nueverest commented Feb 8, 2017 •

edited

Loading

c22 commented Feb 13, 2017

mikespoff commented Feb 23, 2017

1oglop1 commented Mar 7, 2017

mathom commented Mar 7, 2017

c22 commented Apr 19, 2017

Miserlou commented Apr 21, 2017

Only works with Python 2.7? #6

Only works with Python 2.7? #6

Comments

tiagofassoni commented Feb 10, 2016

Miserlou commented Feb 10, 2016

tiagofassoni commented Feb 10, 2016

Miserlou commented Feb 11, 2016

tiagofassoni commented Feb 17, 2016

mathom commented Feb 20, 2016

Miserlou commented Feb 21, 2016

Miserlou commented Feb 21, 2016

maljac commented Apr 9, 2016

Miserlou commented Apr 9, 2016

hayd commented May 9, 2016

xuru commented Aug 10, 2016

Miserlou commented Aug 10, 2016

xuru commented Aug 11, 2016

Miserlou commented Aug 11, 2016

hayd commented Aug 11, 2016

iJebus commented Aug 24, 2016

Miserlou commented Aug 24, 2016

hayd commented Aug 24, 2016

xuru commented Nov 23, 2016

Miserlou commented Nov 23, 2016

nueverest commented Feb 8, 2017 • edited Loading

c22 commented Feb 13, 2017

mikespoff commented Feb 23, 2017

1oglop1 commented Mar 7, 2017

mathom commented Mar 7, 2017

c22 commented Apr 19, 2017

Miserlou commented Apr 21, 2017

nueverest commented Feb 8, 2017 •

edited

Loading