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

py3: bug in pynac when evaluating functions #24751

Closed
embray opened this issue Feb 16, 2018 · 6 comments
Closed

py3: bug in pynac when evaluating functions #24751

embray opened this issue Feb 16, 2018 · 6 comments

Comments

@embray
Copy link
Contributor

embray commented Feb 16, 2018

There are several cases like:

sage: arcsinh(z)
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-2-fbfc0c968329> in <module>()
----> 1 arcsinh(z)

/home/embray/src/sagemath/sage-python3/local/lib/python3.6/site-packages/sage/symbolic/function.pyx in sage.symbolic.function.BuiltinFunction.__call__ (build/cythonized/sage/symbolic/function.cpp:11719)()
    988
    989             if callable(method):
--> 990                 res = method()
    991
    992         if res is None:

/home/embray/src/sagemath/sage-python3/local/lib/python3.6/site-packages/sage/symbolic/expression.pyx in sage.symbolic.expression.Expression.arcsinh (build/cythonized/sage/symbolic/expression.cpp:49022)()
   8588         """
   8589         return new_Expression_from_GEx(self._parent,
-> 8590                 g_hold_wrapper(g_asinh, self._gobj, hold))
   8591
   8592     def arccosh(self, hold=False):

TypeError: attribute name must be string, not 'bytes'

Upstream PRs: pynac/pynac#306 pynac/pynac#308

Upstream: Fixed upstream, but not in a stable release.

Component: python3

Keywords: pynac

Issue created by migration from https://trac.sagemath.org/ticket/24751

@embray embray added this to the sage-8.2 milestone Feb 16, 2018
@embray
Copy link
Contributor Author

embray commented Feb 16, 2018

Changed upstream from Reported upstream. No feedback yet. to Fixed upstream, but not in a stable release.

@embray

This comment has been minimized.

@fchapoton
Copy link
Contributor

comment:3

This seems to be no longer an issue..

@fchapoton fchapoton removed this from the sage-8.2 milestone Mar 14, 2018
@embray
Copy link
Contributor Author

embray commented Mar 14, 2018

comment:4

I wouldn't say it's no longer an issue, but it should be fixed by #24838.

@fchapoton
Copy link
Contributor

comment:5

It seems to be fixed now, that's what I mean.. I am using a python3 branch + only a few more tickets on top of it.

@fchapoton
Copy link
Contributor

comment:6

this should be closed now, please

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants