-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
mako 1.0.1 is incompatible with Python 3.5 #250
Comments
Michael Bayer (@zzzeek) wrote: hi Barry - are there any changes in Python 3.5 to the specification listed here: https://docs.python.org/3/library/ast.html#abstract-grammar ? call is listed like this:
that means may or may not have "starargs" or "kwargs", so we just need to check with hasattr(), is that correct? |
Michael Bayer (@zzzeek) wrote: don't have 3.5 built at the moment, if you want to try this patch:
|
Barry Warsaw (@warsaw) wrote: Hi Mike, Yes, that looks like it fixed the build failure. Thanks! I'll upload 1.0.1 with this patch to Debian and Ubuntu. One other thing to keep in mind for 3.5 is that inspect.getargspec() is deprecated. You get a DeprecationWarning when running the test suite under 3.5, but it doesn't break the build so I'm not going to worry about it. :) |
Michael Bayer (@zzzeek) wrote:
→ 4707bb0 |
Changes by Michael Bayer (@zzzeek):
|
Barry Warsaw (@warsaw) wrote: On Aug 26, 2015, at 05:58 PM, Mike Bayer wrote: One thing I still can't figure out. When I build the package, we run
|
Michael Bayer (@zzzeek) wrote: hmmm, well when i google python3-funcsigs most of the hits seem to be ubuntu-specific. It looks like this package provides the "signature" series of functions that Python 3.4 seems to say that "getfullargspec()" now builds on top of. So perhaps something in Ubuntu. Does a command like "pip freeze" illustrate this package as a dependency? |
Migrated issue, originally created by Barry Warsaw (@warsaw)
In Ubuntu we've enabled Python 3.5 as a supported version. mako 1.0.0 and 1.0.1 are incompatible with it and fail to build because of the use of a new API in the ast module. Here's a paste of the test failures.
The text was updated successfully, but these errors were encountered: