Dear Nicolas,
thank you very much for that comprehensive and kind response -
unfortunately (witness today's sage-support) I am having an impossible time
linking the file you sent, to my virtual machine ...
In any event, I had in the past few days developed a workaround for the
problem because
Hello,
I want to install sage on a system that share the sage installation
directory and are all Debian6 machines, but they might have different
packages installed.
In particular, I ran into the problem (see below):
ERROR:root:code for hash md5 was not found.
Unfortunately, I haven't found a
Yay! with a little digging around I think I know what feature cython-
derived classes are missing that pure python classes do have: It's the
Py_TPFLAGS_VALID_VERSION_TAG feature, which gets used in the method
cache. in _PyType_Lookup (python source: typeobject.c)
Evidence obtained with the
On Sat, 06 Apr 2013 at 01:17PM +0200, Ralf Hemmecke wrote:
Hello,
I want to install sage on a system that share the sage installation
directory and are all Debian6 machines, but they might have different
packages installed.
In particular, I ran into the problem (see below):
In particular, I ran into the problem (see below):
ERROR:root:code for hash md5 was not found.
Well, I did sage -i openssl and then at least I could start sage.
But then, I ran into the thing below and gave up.
I used
Just to tell people that the first and second errors listed below no
longer occur with 5.9.beta3.
As for the third error, I have a trac ticket that fixes it:
http://trac.sagemath.org/sage_trac/ticket/14392
On 03/20/2013 10:09 PM, Stephen Montgomery-Smith wrote:
This is under FreeBSD. (There
Am Donnerstag, 4. April 2013 11:38:41 UTC+2 schrieb P Purkayastha:
I suggest that you introduce a function in sage/plot/misc.py, say,
def get_matplotlib_linestyle(linestyle, return_type):
if return_type == 'short':
# change linestyle from 'dotted', 'dashed', etc to ':',
Hi!
Suppose you write data to orig.sobj, and then you create a symbolic link
copy.sobj to orig.sobj. If you now save data under the name copy.sobj,
then the data in orig.sobj get overridden:
sage: d = tmp_dir()
sage: save(1, os.path.join(d, 'orig'))
sage:
Is this a bug?
$ mkdir a
$ ln -s a b
$ touch b/t
$ ls a
t
What touch b/t did was open b for writing to put a link to the freshly
allocated file underlying t. The fact that opening a symbolic link
means opening the thing to which the link is pointing is essential to
the nature of symbolic links.
Simon King wrote:
Hi!
Suppose you write data to orig.sobj, and then you create a symbolic link
copy.sobj to orig.sobj. If you now save data under the name copy.sobj,
then the data in orig.sobj get overridden:
sage: d = tmp_dir()
sage: save(1, os.path.join(d, 'orig'))
10 matches
Mail list logo
