On Monday, August 12, 2019 at 5:42:30 AM UTC-7, E. Madison Bray wrote:
Although it was designed primarily with astronomy applications in
> mind, the core format is domain-agnostic. It would be really neat to
> see some ASDF "schemas" (descriptions of how specific types of data
> are serialized
Not to be confused with Another System Definition Facility, the de facto
standard build facility for Common Lisp
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
On Fri, Aug 2, 2019 at 5:45 PM Nils Bruin wrote:
>
> On Friday, August 2, 2019 at 2:47:04 AM UTC-7, E. Madison Bray wrote:
>>
>> As I have written before, pickle is not an appropriate format for
>> long-term stable serialization, and never has been, as it is
>> inherently tied to the code which pr
On Friday, August 2, 2019 at 2:47:04 AM UTC-7, E. Madison Bray wrote:
>
> As I have written before, pickle is not an appropriate format for
> long-term stable serialization, and never has been, as it is
> inherently tied to the code which produced it (and is highly
> Python-specific, at that).
On Wed, Jul 31, 2019 at 7:32 PM Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
>
> Dear developers,
>
> It appears that a sage object saved with the "save" command can
> sometimes be not loaded again with "load". It is the second time
> in a month that people complains that it is not working
Dear developers,
It appears that a sage object saved with the "save" command can
sometimes be not loaded again with "load". It is the second time
in a month that people complains that it is not working (because
of Sage version mismatch).
situation number 1: Attached to https://arxiv.org/abs/180