Changes between Version 1 and Version 2 of Ticket #27492, comment 4


Ignore:
Timestamp:
Oct 27, 2019, 7:28:10 PM (3 years ago)
Author:
nbruin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #27492, comment 4

    v1 v2  
    4242si
    4343}}}
    44 As you can see, there's a rather opague string involved. The `unpickle_build` is part of the getstate/setstate protocol, and reading `sage.symbolic.expression.Expression.__setstate__` and `sage.symbolic.expression.Expression.__getstate__` shows you that a Pynac archive is involved. It's not hard to imagine the coordination problems that can arise when using such low-level tools. This needs a pynac expert. I don't know if those still exist.
     44As you can see, there's a rather opague string involved. The `unpickle_build` is part of the getstate/setstate protocol, and reading `sage.symbolic.expression.Expression.__setstate__` and `sage.symbolic.expression.Expression.__getstate__` shows you that a Pynac archive is involved. It's not hard to imagine the coordination problems that can arise when using such low-level tools. This needs a pynac expert. See https://github.com/pynac/pynac/issues/349 (if github is preferred for tracking pynac)