Hi Kwankyu,
On 27 Mai, 18:10, Kwankyu Lee wrote:
> How does Sage solve the following situation? A user stores objects pickled
> in Sage version X.1. Then a developer changes internal logic and data
> structure of the class of the objects for Sage version X.2. If we assume the
> developer's patch
On Friday, May 27, 2011 10:24:59 AM UTC-7, Nils Bruin wrote:
>
> I tried a "sage -upgrade" on a pristine 4.7.rc4 install to get to 4.7
> and I got hg "unresolved" and "uncommitted changes" problems left and
> right. Since "sage -upgrade" duly warns that it offers no guarantees,
> that's not re
On Fri, May 27, 2011 at 9:10 AM, Kwankyu Lee wrote:
> Hi,
>
> How does Sage solve the following situation? A user stores objects pickled
> in Sage version X.1. Then a developer changes internal logic and data
> structure of the class of the objects for Sage version X.2. If we assume the
> develope
I tried a "sage -upgrade" on a pristine 4.7.rc4 install to get to 4.7
and I got hg "unresolved" and "uncommitted changes" problems left and
right. Since "sage -upgrade" duly warns that it offers no guarantees,
that's not really a bug, but given that I didn't do anything with that
4.7.rc4 other than
Hi,
How does Sage solve the following situation? A user stores objects pickled
in Sage version X.1. Then a developer changes internal logic and data
structure of the class of the objects for Sage version X.2. If we assume the
developer's patch is merged to Sage X.2, then typically the user's ob
On 05/26/11 10:33 AM, Florent Hivert wrote:
Hi There,
One stupid question: currently in trac for the Report Upstream there are the
following choices:
- Fixed upstream, in a later stable release.
- Fixed upstream, but not in a stable release.
How do I write the following ?
- Fixed upst
