Hi Dima,
On 2021-09-09, Dima Pasechnik wrote:
> I think that 'git trac' is mainly used by the release manager - I
> won't recommend it to newcomers.
No, I'm not a release manager, but I find it very practical to be able
to do "git trac pull 12345" instead of doing a series of commands that
I
Hi Thierry,
On 2021-02-08, Thierry wrote:
> We should notice that, contrary to other packages, those packages should
> be considered as downstream (not upstream), and this should be reflected
> in our release process.
>
> Indeed, their code get adapted after Sage changes, see e.g. (randomly
>
Hi Samuel,
thank you for the interesting sources!
Best regards,
Simon
On 2020-04-08, Samuel Lelievre wrote:
> About Sage and floating-point numbers, if I remember correctly,
>
> - IEEE 754 is not a complete specification, some details are left
> up to the implementation and therefore IEEE
Hi!
On 2020-04-07, Thierry wrote:
> By the way, an excellent ressource to teach those kind of things and
> check carefully what happens is the sign_mantissa_exponent method:
>
> sage: a = RR(1.1)
> sage: a
> 1.10
> sage: a.sign_mantissa_exponent()
> (1, 4953959590107546, -52)
Nice,
On 2020-04-07, Thierry wrote:
> An appropriate place seems to be : https://ask.sagemath.org/questions/
I will never prefer ask.sagemath over sage-support.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop
Hi!
A few days ago, I asked on sage-support about rounding in Sage. But
since there was no answer and since it is relevant to my teaching in the
upcoming semester, let me repost here (with modifications).
According to IEEE 754, the default rounding mode for floating-point
operations is "round
Hi Michael,
perhaps the code in src/sage/docs/instancedoc.pyx is helpful for you?
I see several problems:
1. It is possible to override the __doc__ of an anbound method, but this
would override the __doc__ also in the parent class:
sage: class A:
: def my_method(self):
:
Hi!
On 2020-03-19, John H Palmieri wrote:
> What about
>
> my_method = Mother.my_method
> my_method.__doc__ = "new docstring"
>
>
> Does that do what you want?
Probably not. Wouldn't that be the same as
Mother.my_method.__doc__ = "new docstring"
?
Best regards,
Simon
--
You received this
Hi Sébastien, hi Marc,
On 2020-03-12, Sébastien Labbé wrote:
> You may not be using the good register. You may see what is in the current
> registers by writing:
>
>:registers
>
> To yank in the register +, you do "+y or "+\Y to yank with Marc's code. The
> register + is the clipboard on my
Hi Marc,
On Wednesday, March 11, 2020 at 12:50:07 PM UTC+1, Marc Mezzarobba wrote:
>
> Sébastien Labbé wrote:
> > But I am not getting errors, maybe my vim is too old (7.4.1689). I
> > need to update my machine but I am always postponing this to tomorro
>
> Indeed, it looks like I'm using
Hi Marc,
sorry, I still don't get what *exactly* one needs to do in order to achieve
*what*.
In your original mail, you wrote that it is "for copy-pasting examples and
doctests to the sage repl".
If I understand correctly, repl is abbreviation for read-eval-print-loop. I
guess that' what I
On 2020-03-08, David Joyner wrote:
> On a tangential matter, I'd like to add that
> according to Dan Bump's notes "Group Representation
> Theory" (http://sporadic.stanford.edu/bump/group/gr1_4.html),
> this set of elements that the permutations does not
> fix is called the support.
Exactly.
>
On 2020-03-08, David Joyner wrote:
> I agree with Michael O, a permutation is a bijection,
> so the image is the domain is the codomain.
+1
> For a patch to "define the image of a permutation
> to be the set of elements that it does not fix" is a
> mistake, IMHO. Maybe the set computed could be
On 2020-02-22, Emmanuel Charpentier wrote:
> Le samedi 22 février 2020 14:35:49 UTC+1, Eric Gourgoulhon a écrit :
>> A solution here is to declare explicitly the LaTeX name of the symbolic
>> variable at creation, as we did when using only ASCII names:
>>
>
> Of course. but this somehow defeats
On 2020-02-21, Simon King wrote:
> Hi Emmanuel,
>
> On 2020-02-21, Emmanuel Charpentier wrote:
>> sage: latex(λ^2)
>> λ^{2}
>
> Couldn't we modify the latex() function, by exploiting
> IPython.core.completer.reverse_latex_symbol, to automatically translate
>
Hi Emmanuel,
On 2020-02-21, Emmanuel Charpentier wrote:
> sage: latex(λ^2)
> λ^{2}
Couldn't we modify the latex() function, by exploiting
IPython.core.completer.reverse_latex_symbol, to automatically translate
all unicode symbols that aren't understood by pdflatex?
Best regards,
Simon
--
You
,
Simon
On 2020-02-13, Simon King wrote:
> Hi Denis,
>
> in the past, sage-combinat-devel was a very active list and certainly
> the topic of your post fits well, but it seems to me that it would be a
> good idea to re-post on sage-devel.
>
> Did you read the developer's guide?
&
Hi Denis,
in the past, sage-combinat-devel was a very active list and certainly
the topic of your post fits well, but it seems to me that it would be a
good idea to re-post on sage-devel.
Did you read the developer's guide?
Certainly people could help you contributing the code. In particular
Hi Frederic,
On 2020-02-07, Han Frederic wrote:
> It is indeed rare for an spkg to be linked to the sage library...
... but it is not the only one. p_group_cohomology is similar in that
regard.
> We need one of the following
> (to not lose any features) either giacpy_sage is an external
On 2020-02-04, Markus Wageringel wrote:
> Giacpy_sage provides C-bindings for Giac which is already a standard
> package. So making Giacpy_sage a standard package as well would allow to
> replace pexpect calls to Giac by C-calls, which is the overarching goal of
> #16688. Giac is currently
Hi Samuel,
On 2020-02-03, Samuel Lelievre wrote:
> Please vote for making giacpy_sage a standard package.
Could you elaborate what giacpy is about, i.e., what functionality would
it add to SageMath resp. improve in SageMath? That question isn't
addressed on the ticket yet.
Best regards,
Simon
Hi Dima,
On 2020-01-30, Dima Pasechnik wrote:
> I think git-trac should not be mentioned in the manual as the preferred way
> to use git.
OK. Stating that "being able to use plain git is a useful skill" is
fine, and of course elaborating how to use plain git to work with trac
is fine, too. But
Hi Eric,
On 2020-01-30, Eric Gourgoulhon wrote:
> I would even vote for removing the git-trac section from the developer
> manual.
-1
I do use "git trac".
Best regards,
Simon
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe
Hi Nils,
yes, that's exactly the same problem! Thank you for reminding me. I've
totally forgotten how the "correct" encoding was called.
Best regards,
Simon
On 2020-01-22, Nils Bruin wrote:
> On Wednesday, January 22, 2020 at 1:35:16 PM UTC-8, Simon King wrote:
>>
&g
Hi!
I have (Sage-related) data pickled with Python-2. Part of the data is
binary data put into a Python-2 str.
Now, with Python-3, the binary data is put into bytes.
Consequently, when unpickling my old data with Python-3, I want the
Python-2 str to be interpreted as bytes. However, Python-3
Dear Dima,
Indeed it now works. I didn't change anything, just tried again.
So, problem solved...
Thank you!
Simon
--
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
Hi Dima,
On Thursday, January 16, 2020 at 9:08:54 PM UTC+1, Dima Pasechnik wrote:
>
> the story is here, in fact:
>
> https://lars.ingebrigtsen.no/2020/01/06/whatever-happened-to-news-gmane-org/
>
Thank you!
As it seems, the only mentioning of "news.gmane" in my home directory in a
file whose
Hi!
I prefer reading all SageMath-related groups with slrn, via news.gmane.org.
However, since a few days, I always get this:
king@klap:~$ slrn
slrn 1.0.2
Loading /usr/share/slrn/slang/slrn.sl
Reading startup file /etc/news/slrn.rc.
Reading startup file /home/king/.slrnrc.
Loading
Hi Nils,
On 2020-01-06, Nils Bruin wrote:
> In fact, I think it would make a lot of sense to make 9.1 the last release
> to support py2 and therefore make 9.1 more a bugfix release: concentrate on
> fixes of issues that arise as a result of 9.0 and fix them, so that there's
> a relatively
Hi Nils,
On 2019-12-02, Nils Bruin wrote:
> On Monday, December 2, 2019 at 3:18:20 PM UTC-8, Michael Orlitzky wrote:
>>
>> Who do I have to make a campaign donation to if I want this to be the
>> default?
>>
>
> The Society for the Prevention of Predictable Performance would be a good
> place
Dear Erik,
On 2019-11-12, E. Madison Bray wrote:
> On Fri, Nov 8, 2019 at 11:06 PM Simon King wrote:
>> While we are at it: Currently, for building the package's documentation,
>> I use "$MAKE html" followed by some "cp -r" to copy the resulti
Hi Erik,
On 2019-11-08, E. Madison Bray wrote:
> Just to clarify, once more (and please reread my earlier message in
> this thread regarding what a "DESTDIR install" is and why that is
> used),
This does not clarify it to me at all, I'm afraid. To start with,
in my very simple mind, I can not
Hi Dima,
On 2019-11-06, Dima Pasechnik wrote:
> sdh_install installs a json file into
> SAGE_LOCAL/var/lib/sage/installed/
> which are then used by unistallaller
> ...
> I guess sdh_pip_install does not do this, I don't know.
No, I just checked: Those files of p_group_cohomology that got
n/sage-dist-helpers. In my opinion they should also be
> documented in the developer's guide, but they don't seem to be.
>
>
> On Thursday, November 7, 2019 at 6:35:05 AM UTC-8, Simon King wrote:
>>
>> Hi Dima,
>>
>> On 2019-11-06, Dima Pasechnik > wrote:
&g
Hi Dima,
On 2019-11-06, Dima Pasechnik wrote:
> if you look at its spkg-install, you'd see that shd_install is not
> used at some place, instead
>
> make install
>
> is done, something that won't write any JSON files, IMHO...
Good that I leave comments in my code...
The comment says that I
Hi Eric,
On 2019-11-06, E. Madison Bray wrote:
>> However, I heard rumours that in order to make a Sage optional package
>> uninstallable, one needs some new script analogous to spkg-install.
>>
>> Can someone give me a pointer on what should be done in that script and
>> what tools (sdh_*) are
On 2019-11-05, E. Madison Bray wrote:
> The generated file `build/make/Makefile` is output by the
> `./configure` script. In fact, that's its main purpose. When
> switching branches in this case the best thing to do is to re-run
> `./configure`.
Concerning the original question how to
Hi Vincent,
On 2019-10-27, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
> This was an easy one. The following shows that SR is just
> broken pi is rational!
>
> sage: q = continued_fraction(pi).convergent(100)
> sage: q
>
Hi Emmanuel,
On 2019-10-24, Emmanuel Charpentier wrote:
> Writing *correctly* this decomposition is, IIRC, a numerical analysis
> bitch... You are, IIRC, led to compute differences of large products, where
> underflows can easily slip into... Definitely not an amateur's problem.
>
> While I
On 2019-10-24, Michael Jung wrote:
> Do you have an example where SR fails to be exact?
One can convert a float to SR. The result is in SR, but still behaves
like a float:
sage: a = SR(2.)^(1/500)
sage: a^500
2.05
sage: a.parent()
Symbolic Ring
Best regards,
Simon
--
You
Hi Michael,
On 2019-10-24, Michael Jung wrote:
> Maybe, I did get something wrong. But what's the problem about Gram-Schmidt
> on SR? There are just sums and divisions (and probably roots to normalize)
> in Gram-Schmidt which should not lead to problems in SR.
>
> By the way, what does "exact"
Hi David,
On 2019-10-19, David Roe wrote:
> I think the idea is that if a user's typing interactively then they don't
> need a deprecation warning (since the behavior currently works). It's more
> important to show a user a warning if they have the deprecated behavior in
> a function they've
On 2019-10-02, Kwankyu Lee wrote:
> Hera:sage-dev$ g version
> git version 2.23.0
$ git version
git version 2.7.4
May that be the problem, then?
In any case, git checkout -f did work, and apparently did
no harm. So, I'm back at work...
Best regards,
Simon
--
You received this message
On 2019-09-28, Simon King wrote:
> I wonder what's different. I am still reluctant to do "git checkout -f
>", but perhaps that would be my best bet.
I tried, and it seemed to work.
However, someone who knows about git (i.e., not I) should report the bug
that git allows dele
Here is how to reproduce the git problem at least to some extent:
king@klap:~$ mkdir gittest
king@klap:~$ cd gittest
king@klap:~/gittest$ mkdir A
king@klap:~/gittest$ cd A
king@klap:~/gittest/A$ git init
Initialized empty Git repository in /home/king/gittest/A/.git/
king@klap:~/gittest/A$ touch
Hi Kwankyu,
On 2019-09-27, Kwankyu Lee wrote:
>> I am not totally sure if that's what was happening. Would git really
>> allow the "git branch -d" operation when another worktree is on that
>> branch?
>>
>
> If you were at foobar in py3 worktree and at develop in py2 worktree, no.
Then what
On 2019-09-27, Simon King wrote:
> Indeed, all files in the Sage tree are untracked, in the py3 worktree.
> And that's why "git checkout develop" won't work (it tells me to commit
> are stash first).
>
> Can you please tell me how to recover from that mess?
Perhaps &quo
Hi!
At some point I was advised to use "git worktree" to have one py2 and
one py3 installation sharing the same git repository. Till one hour ago,
it worked fine.
Now, if I understand correctly, in my py2 worktree, I was on the develop
branch. There was one branch "foobar" (not its real name)
Hi!
Trying to make my group cohomology package work in both py2 and py3, I
already thought it was done, but I found that a pickle created with py3
cannot be read by py2. It would of course be possible to argue that people
are unlikely to unpickle a py3 pickle with py2, and since unpickling a
py2
Hi Dima,
On 2019-09-24, Dima Pasechnik wrote:
> I'm surprised that *.c files created by Cython for pyX may be used for
> py(5-X) without many problems.
> I'd expect this to break down totally...
Indeed. It is surprising that I only got two kinds of spurious errors:
In one place, a pickle of a
Hi Dima,
On 2019-09-24, Dima Pasechnik wrote:
> Shouldn't coexisting installations like this have different --prefix ?
Of course. But if I understand correctly, this only affects where stuff
is installed, not where it is built. The situation is as follows:
- the .c files are created in the
Hi Vincent,
On 2019-09-24, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
> Are you sure that the problem comes from the C files? If you erase
> them between the two installations what do you get?
That's what I'm testing now.
BTW, meanwhile I found that I can prescribe in my setup.py
Hi!
At #28414, I'm trying to upgrade my group cohomology package so that it
works both on sage-with-py2 and sage-with-py3.
On the laptop where I work on the new package version (I didn't publish
the code yet), I have a py2 and a py3 installation of Sage. To build the
package without the hassle
Hi!
Let R be a ring that is an F-vector space, for some field F.
Let x,y be elements of R and c be an element of F.
If I understand correctly, in order to implement x/y, one should provide
a single underscore method x._div_. But what should one provide for x/c?
It seems that the default
Hi!
Although late...
On 2019-09-01, mmarco wrote:
> ...
>
> Do you think it is reasonable to do these deep changes in this short time?
> If it is , then i definitely vote for it.
>
> If it is not, then I would propose to leave it as a longer term goal
> (hopefully not much longer), and once
Hi!
During recent the Sage workshop in Bonn, I started using travis-ci for
my optional Sage package on group cohomology. I am now basically done to
make the package work both in py2 and py3 --- on my laptop at least.
What is needed to do to let both language levels be considered in
travis-ci?
PS:
On 2019-09-03, Simon King wrote:
> - Without `encoding='bytes'`, Python-3 can in general not unpickle any
> pickle created with Python-2 that contains strings.
Stated differently:
Ostensibly, Python-2 str corresponds to Python-3 bytes, and Python-2
unicode corresponds to Python
Hi!
On 2019-09-02, Simon King wrote:
> The problem apparently boils down to the following:
> - Pickle the string '\x80\x1f' in Python-2
> - Try to load that pickle in Python-3 (it fails).
>
> Bummer!
Nils Bruin pointed me to
https://stackoverflow.com/questions/28218466/unpick
On Monday, September 2, 2019 at 6:22:24 PM UTC+2, Simon King wrote:
>
> Also, if I understand the error message "UnicodeDecodeError: 'ascii'
> codec can't decode byte 0x80 in position 0: ordinal not in range(128)"
> correctly, it is an error in unpickling a string. And t
On 2019-09-02, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
> As discussed in
>
> https://groups.google.com/forum/#!topic/sage-devel/JuKzzgxDlmA
>
> Pickling/unpickling is not supposed to work accross Sage versions
> (including the Python version you use).
>
> Is this what you are trying
On 2019-09-02, Simon King wrote:
> Strangely, when I read the pickle as a string
>open('path/to/file.sobj').read()
> then it fails with a (different?) UnicodeError in Python-3.
That's not the problem. However, I am not able to track down the problem
myself. So, I'd appreciate help.
Hi!
I have a pickle that I can unpickle in Sage-with-Python-2, but it fails
to unpickle in Sage-with-Python-3, because of some UnicodeError.
Strangely, when I read the pickle as a string
open('path/to/file.sobj').read()
then it fails with a (different?) UnicodeError in Python-3.
The details
Hi Dima,
On 2019-08-29, Dima Pasechnik wrote:
> is this python2 from your OS, or from Sage's installation?
>From Sage's installation (apparently Sage-with-py-3 also builds
python-2):
(sage-sh) king@klap:~$ which python
/home/king/Sage/git/py3/local/bin/python
(sage-sh) king@klap:~$
Hi!
The following happens with a Py-3 build of Sage: I open a sage-shell,
and then I get
(sage-sh) king@klap:src$ sage --python --version
Python 3.7.3
(sage-sh) king@klap:src$ python --version
Python 2.7.15
Is it expected that the default python version in a py-3 install is a
py-2?
Best
Hi Eric,
On 2019-08-27, Eric Gourgoulhon wrote:
> To avoid such mistake, you can run set_inverse() with the option
> verbose=True. Then the provided inverse transform is checked.
Is the option really called "verbose=True"? Not "check=True", like in
most other cases?
Best regards,
Simon
--
Hi all,
did someone open a ticket for that issue?
Best regards,
Simon
On 2019-08-24, Nils Bruin wrote:
> It seems to be spending a lot of time in cython code, so "%crun" might give
> the best idea. This is part of the profile obtained by running the "copy"
> command 20 times:
>
>0
Hi,
I am sorry for the late answer (and I am a bit surprised that nobody
else answered before).
I believe it is somehow useful to have such a feature when developing a
large piece of new code (so that one can do a relevant subset of tests
quickly). However, I am not so sure how that feature
Hi,
On 2019-08-02, E. Madison Bray wrote:
> Sage's use of pickle for save()/load() is a mis-feature IMO. One that
> made sense at a time, for lack of a better choice. And that's still
> useful as a means of saving/restoring some objects between sessions.
> But I don't think you can always
Hi Markus,
apparently our posts crossed.
On 2019-08-01, Markus Wageringel wrote:
> Usually, the latest beta should be available as sagemath/sagemath:develop
> at DockerHub. However, for some reason this tag has not been updated in a
> while, so it still points to 8.8.beta5. See also
>
Hi Nathan,
On 2019-08-01, Nathan Dunfield wrote:
> Docker images with beta versions of Sage are available:
>
> https://hub.docker.com/r/sagemath/sagemath/tags
Great, thank you! When applying a patch (from some closed-but-not-merged
ticket) to the latest beta tag then things work fine, which
Hi!
Last week at SageDays100, I got an introduction to travis-ci, and with
help from this list and a lot of duckduckgo-search I now have a version
of my group cohomology software that on github with travis-ci successfully
installs in a Sage docker image.
Problem: It does install, but it wouldn't
Hi Markus,
On 2019-07-31, Markus Wageringel wrote:
> I think it would be good to keep the install script for Travis-CI as close
> as possible to what you would normally do to install a package in Sage,
> that is, create an updated tarball of your repository and copy it to
> upstream/, update
Hi Markus,
On 2019-07-31, Markus Wageringel wrote:
> I think it would be good to keep the install script for Travis-CI as close
> as possible to what you would normally do to install a package in Sage,
> that is, create an updated tarball of your repository and copy it to
> upstream/, update
On 2019-07-30, Simon King wrote:
> Perhaps I found a solution.
Yes and no.
Yes, it does work with the sage version on my laptop
No, it does not work on travis-ci with a sage docker image.
Namely, sage-dist-helpers cannot be found in $SAGE_ROOT/build/bin in the
docker image:
ls $SAGE_R
Perhaps I found a solution.
Apparently the sdh_* shell functions are defined in
$SAGE_ROOT/build/bin/sage-dist-helpers. Sourcing, so it seems, makes the
spkg-install script work.
Best regards,
Simon
On 2019-07-30, Simon King wrote:
> Hi Dima,
>
> On 2019-07-30, Dima Pasechnik wrote
Hi Dima,
On 2019-07-30, Dima Pasechnik wrote:
> just fix the PATH, no?
>
> It should include SAGE_ROOT/src/bin, SAGE_ROOT/build/bin, etc
Apparently sage -sh is fixing the path:
$ ~/Sage/git/sage/sage -sh -c 'echo $PATH'
Hi!
I learned at Sage Days 100 how to post the code for my cohomology spkg
on github, and learned basics about travis-ci.
Meanwhile I found out how to start a docker container and install the
prerequisites of my spkg.
Current problem: How to launch the package's spkg-install?
Of course(?) the
Hi!
If we say that Sage Integers and Rationals should comply with Python's
requirements, then for consistency, the same should hold for elements of
integral domains respectively of their fraction fields.
In particular, the required element methods of QuotientFields() should
be removed and
On 2019-07-21, Travis Scrimshaw wrote:
> Maybe a difference between Python and Cython classes?
If I recall correctly, Cython can be made to embed information
into the docstring, because otherwise that information wouldn't be
accessible. And with Python classes that information is directly
Hi Michael,
On 2019-07-13, Michael Jung wrote:
> You could try something like
> try:
> is_field = R.is_field()
> except TypeError:
> is_field = (R in Rings())
> as a compromise? Would that make the code faster?
I think today the preferred way to test if something is a ring or
integral
Hi Dima,
On 2019-07-10, Dima Pasechnik wrote:
> IMHO "git trac" can create trac tickets for you, but if one created a
> ticket by hand then, unless there is a branch already, "git trac checkout"
> may get confused...
Normally, I create the ticket manually and then do "git trac checkout",
and
Hi Isuru,
On 2019-07-09, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
> The usual procedure is to set the milestone to "won't fix/duplicate" and
> then "needs review".
To elaborate a bit more (because in the past at some point I had the
same problem):
A ticket can only be *closed* by
Hi Grayson,
On 2019-07-03, Grayson Jorgenson wrote:
> Check that :trac:`27483` is fixed::
>
> sage: P. = PolynomialRing(QQ)
> sage: I = Ideal([x^3, x*y^2, y^4, x^2*y*z, y^3*z, x^2*z^2, x*y*z^2,
> x*z^3])
> sage: I.hilbert_polynomial(algorithm='singular')
> 3
>
> Was this meant
Hi Grayson,
On 2019-07-03, Grayson Jorgenson wrote:
> I found ticket 27483 which seems to be dealing with a similar bug, but I'm
> using Sage 8.9 beta1 and their changes seem to be present in my version so
> it seems the fixes there do not address this issue (I think this ticket was
> merged
Hi!
Is it a Python object?
A cached method (if that hasn't changed since I last looked at the code)
stores the cached values in some dict stored as an attribute, and when
you pickle the object (at least when no __reduce__ method interferes),
it should automatically store that attribute.
But you
Hi Dima,
On 2019-06-21, Dima Pasechnik wrote:
> Basically, this is a great illustration that pexpect interface (what's
> topcom using)
> is slow...
Question: Is that slowness OS dependent? I recall that when I was using
openSuse on my laptop, a couple of years ago, I needed to patch the OS
Hi!
On 2019-06-16, Dima Pasechnik wrote:
> libsingular interface is a mess, cf e.g.
> https://trac.sagemath.org/ticket/27508
Singular uses a peculiar memory manager that is optimized for Gröbner
basis computations. If that memory manager is replaced by ordinary
malloc (which makes sense for
Hi Daniel,
I'd be interested in that topic as well. I do not try to answer your
question myself, because I remember (hopefully correctly) that the
recommended way to do equality testing has changed because of the
switch to Python3.
So, hopefully someone else can chime in...
Best regards,
Simon
Hi Simon,
On 2019-05-27, Simon Brandhorst wrote:
> I would agree that I want unique representation with simple "ambient"
> objects (usually constructed from an integer and maybe a ring). Then with
> complicated objects I am not so sure anymore. Say subgroups of a group and
> submodules of a
Hi Simon,
On 2019-05-23, Simon Brandhorst wrote:
> I can live with (V, projections, coprojections)
> but I dislike hiding everything in lists (or lists of lists, or lists of
> lists of lists..).
> Being able to type VW.projections(1) would just be so much nicer.
+1.
But how? I think we do
Hi Vincent,
On 2019-05-22, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
> I am not a big fan of bundling everything into a single
> bigger object. What about returning a triple
> (V, projections, coprojections)?
I tend to argue that in the first place, SageMath is a maths software.
And
Hi Eric,
On 2019-05-22, Eric Gourgoulhon wrote:
> According to
> https://ipython.readthedocs.io/en/stable/config/integrating.html
> if _repr_latex_() returns None then it falls back to repr(). So a strategy
> could be to implement _repr_latex_ in SageObject (I guess all Cython
> objects are
Hi Eric,
On 2019-05-21, Eric Gourgoulhon wrote:
> Le lundi 20 mai 2019 07:55:30 UTC+2, Kwankyu Lee a écrit :
>>
>> . Moreover many sage objects currently are displayed broken if typeset.
>>
>
> In that case, a solution could be to introduce a new class,
> TypesetSageObject, say, to implement
Hi Kwankyu,
On 2019-05-10, Kwankyu Lee wrote:
> There is no ticket. It seems bad to create a ticket before you have a
> specific goal and a means to achieve it.
Why? You have specific examples. That should be enough for a ticket,
IMHO. If while working on the ticket it turns out that the
Dear Kwankyu,
thank you for your contribution and your report!
On 2019-05-10, Kwankyu Lee wrote:
> 1. It is very, but not terribly, slow compared with Magma. One may want to
> improve the speed.
Is there a ticket for it, which also points out what examples are slow and
how it compares with
Hi Bea,
On 2019-04-23, Bea Galiana wrote:
> I've been reading the general conventions about writing tests but I'm not
> really sure about where should I add it. I did take a look at others
> scripts where doctests have been added before and it seems I should I write
> it as a comment, so I
PS:
On 2019-04-01, Simon King wrote:
> I suppose that (coming from school) your implementation is not "for
> speed", but for education.
>
> There are a couple of implementations in Sage that have educational
> purpose (e.g., toy implementations of Buchberger's algori
Hi Quentin, hi all,
On 2019-04-01, Quentin Hillebrand wrote:
> Hello,
>
> For a school project, me and some classmates have implemented in Sage
> functions for the printing of Turing Machines along with the execution.
> We were wondering in what way those could be incorporated to Sage and if
>
Hi David,
On 2019-03-22, David Coudert wrote:
> Our interface to nauty geng is in Python, but the difficulty is not here.
>
>- It takes time to build graphs from graph6 strings, and also to build
>Sandpiles (12 for each graph)
>- The number of biconnected graphs with 12 nodes is
Hi!
Does either of you plan to open a ticket and make the functionality
available, that according to Jori is present in nauty but according
to Ai isn't wrapped in Sage?
Best regards,
Simon
On 2019-03-21, Jori Mäntysalo wrote:
> On Thu, 21 Mar 2019, Ai Bo wrote:
>
>> Is there a way to "random
1 - 100 of 2964 matches
Mail list logo
