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

[Pyrex] c-code mis-interpretation #187

Closed
sagetrac-joel mannequin opened this issue Dec 19, 2006 · 2 comments
Closed

[Pyrex] c-code mis-interpretation #187

sagetrac-joel mannequin opened this issue Dec 19, 2006 · 2 comments

Comments

@sagetrac-joel
Copy link
Mannequin

sagetrac-joel mannequin commented Dec 19, 2006

I found a small bit of code that gets compiled incorrectly to c. A sample is:

def unlist():
        lst = [1,2]
        lst,m = lst

The translated c-code from this will produce an Unindexable exception. This
results from the fact that the variable "lst" is bound to the first element
of the list (the integer 1) before the second element is extracted
from "lst". Hence it tries to unpack from the integer rather than the list.

Component: interfaces

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

@sagetrac-mabshoff
Copy link
Mannequin

sagetrac-mabshoff mannequin commented Aug 28, 2007

comment:1

This is a rather old bug. We should verify that the problem still exists.

tagged for 2.9, hopefully to be resolved during Sage Bug Day 2.

Cheers,

Michael

@sagetrac-mabshoff sagetrac-mabshoff mannequin added this to the sage-2.9 milestone Aug 28, 2007
@williamstein
Copy link
Contributor

comment:2

works for me now.

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

1 participant