Re: [sage-devel] Unable to compile JuPiMake

2023-12-20 Thread VulK
I can confirm: it is due to an extra space in the output of `polymake-config --cflags`. Now that you pointed this out I noticed that there is already a PR open on this https://github.com/sebasguts/JuPyMake/pull/5 with the same error message I got. My google-foo is failing me. Thanks again

Re: [sage-devel] Unable to compile JuPiMake

2023-12-20 Thread VulK
Hm, my next guess is then https://github.com/sebasguts/JuPyMake/issues/4 since I think that's also on Gentoo. I can be more certain in a few hours after polymake builds. It does look so: $ polymake-config --cflags | grep " " | wc -l 1 Let me try to fix this on the fly S. -- You

Re: [sage-devel] Re: quo_rem for multivariate Laurent polynomial rings

2021-01-17 Thread VulK
Oops, thanks for catching the mistake S. * dmo...@deductivepress.ca [2021-01-17 12:01:41]: I agree that this needs to be fixed. Offhand, I don't know what the answer should be (for example, (1/(x*y), 0) also seems reasonable), but (0,1) is certainly not correct. So please do open a ticket.

[sage-devel] quo_rem for multivariate Laurent polynomial rings

2021-01-17 Thread VulK
Dear all, can someone please confirm that the current behaviour of sage is not the expected one before I open a ticket about it? sage: R. = LaurentPolynomialRing(QQ) sage: q,r = (1/x).quo_rem(y) ; q,r (0, 1) sage: q*y + r == x False The correct

Re: [sage-devel] Re: trouble upgrading to latest stable version

2020-05-26 Thread VulK
Unpacking of lambda functions' arguments is, alas, no longer supported in python3. cf. https://www.python.org/dev/peps/pep-3113/ S. * Anne Schilling [2020-05-26 11:24:01]: Ok, success!!! Finally sage compiled for me using Matthias' suggestion of "./configure --without-system-freetype"

Re: [sage-devel] Proposal for Sage 9.2: require "./configure" before "make"

2020-04-18 Thread VulK
+1 for standard behaviour * John H Palmieri [2020-04-18 13:51:29]: Several of us are in favor of requiring that, in order to build Sage, people should have to run "./configure" before running "make". I would further propose that "make" should not itself then run "configure". Some

Re: [sage-devel] Re: Chain Complexes and homology

2019-11-27 Thread VulK
Hi Travis (and all), I already have a toy implementation and it is indeed worth including in sage. Given a chain complex it produces a new chain complex that has the same homology but whose differentials are much much smaller. You can look at it here:

Re: [sage-devel] Re: Chain Complexes and homology

2019-11-14 Thread VulK
I may be interested in helping out with this but I am definitely not knowledgeable enough on the math behind to tackle the task on my own. S. * John H Palmieri [2019-11-13 18:36:25]: Sage is not using very sophisticated methods for computing homology. If anyone wants to implement something

[sage-devel] Chain Complexes and homology

2019-11-13 Thread VulK
Dear All, I was looking into computing homology of a certain chain complex when I came across this paper arXiv:1903.00783v1. Apparently he claims that he has an algorithm to do so that is much faster than the one we currently have in sage. Did I understand correctly the claim? If so, would it

Re: [sage-devel] Re: Switch to Python 3 by default

2019-11-05 Thread VulK
ced? If so, should we just ignore the issue? S. * Dima Pasechnik [2019-11-05 10:29:52]: On Tue, Nov 5, 2019 at 10:19 AM VulK wrote: I am not sure I agree with setting this at build time: a jvm could be installed afterwards and/or updated independently of sage if the configuration of the

Re: [sage-devel] Re: Switch to Python 3 by default

2019-11-05 Thread VulK
I am not sure I agree with setting this at build time: a jvm could be installed afterwards and/or updated independently of sage S. * Michael Orlitzky [2019-11-04 08:49:18]: On 11/3/19 4:55 PM, VulK wrote: On the same note: the current implementation of `is_jvm_available` is not really

Re: [sage-devel] Re: Switch to Python 3 by default

2019-11-03 Thread VulK
-11-03 19:16:35]: On Sun, 3 Nov 2019, 16:57 VulK, wrote: I have issues with a symlink when installing ipython: """ ... Successfully installed ipython-5.8.0 Cleaning up... Removed build tracker '/tmp/pip-req-tracker-x6b62y1w' real0m3.382s user0m3.027s s

Re: [sage-devel] Re: Switch to Python 3 by default

2019-11-03 Thread VulK
me note: the current implementation of `is_jvm_available` is not really robust and I should open a ticket about this; any suggestion for a better implementation? S. * Dima Pasechnik [2019-11-03 19:16:35]: On Sun, 3 Nov 2019, 16:57 VulK, wrote: I have issues with a symlink whe

Re: [sage-devel] Re: Switch to Python 3 by default

2019-11-03 Thread VulK
[dochtml] [discrete_] ValueError: invalid literal for int() with base 10: 'Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true\n8' S. * Dima Pasechnik [2019-11-03 19:16:35]: On Sun, 3 Nov 2019, 16:57 VulK, wrote: I have issues with a symlink when installing ipytho

Re: [sage-devel] Re: Switch to Python 3 by default

2019-11-03 Thread VulK
I have issues with a symlink when installing ipython: """ ... Successfully installed ipython-5.8.0 Cleaning up... Removed build tracker '/tmp/pip-req-tracker-x6b62y1w' real0m3.382s user0m3.027s sys 0m0.498s Copying package files from temporary location

Re: [sage-devel] Re: Switch to Python 3 by default

2019-11-03 Thread VulK
Building now S. * Frédéric Chapoton [2019-11-03 05:18:13]: Could please some of the many plus-one-ing people try the branch at #28660 and report there if it works for them, namely builds a working python3-sage by default ? Frédéric Le dimanche 27 octobre 2019 01:58:23 UTC+2, Volker Braun a

Re: [sage-devel] Switch to Python 3 by default

2019-10-27 Thread VulK
+1 * Samuel Lelievre [2019-10-26 22:29:40]: +1 -- 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 to sage-devel+unsubscr...@googlegroups.com. To view this

Re: [sage-devel] Re: UniqueRepresentation inheritance and __classcall__

2019-09-27 Thread VulK
Indeed it seems to be documented. Why is this not in the online documentation? S. * Travis Scrimshaw [2019-09-26 17:59:38]: There is also an example of this inheritance and discussion in one of the sage.structure.unique_representation examples. Best, Travis On Friday, September 27, 2019

Re: [sage-devel] Re: UniqueRepresentation inheritance and __classcall__

2019-09-26 Thread VulK
The prototype does, now I have to implement the real thing. Is there any way to add this info to the documentation? It took me a lot of trial and error to figure out how to do what I wanted. S. * Travis Scrimshaw [2019-09-26 15:11:07]: So it works now, correct? Best, Travis On Friday,

Re: [sage-devel] Re: UniqueRepresentation inheritance and __classcall__

2019-09-26 Thread VulK
Oops, I think that I figured out where the mistake was. Here is the correct code: class OldFoo(UniqueRepresentation): @staticmethod def __classcall__(self, data, **kwargs): hashable_data = tuple(data) kwargs['some_default_option'] = 'bar' return super(OldFoo,

Re: [sage-devel] Re: UniqueRepresentation inheritance and __classcall__

2019-09-26 Thread VulK
Thank you Travis for your reply. Here is an attempt at implementing your suggestion that does not work: it looks like OldFoo.__classcall__ is skipped and OldFoo.__init__ is run directly instead. This is not what I want: I would like the preparsing in OldFoo to still be performed after the

[sage-devel] UniqueRepresentation inheritance and __classcall__

2019-09-25 Thread VulK
Dear All, I would like to make a new class inheriting from a class based on UniqueRepresentation. My goal, among other things, is to preparse the arguments a little before calling the class I am inheriting from. Unfortunately this class also does some preparsing via __classcall__ to make

Re: [sage-devel] Re: CHomP

2019-05-04 Thread VulK
Thanks I'll have a look into that. S. * John H Palmieri [2019-05-03 10:57:31]: On Friday, May 3, 2019 at 10:22:25 AM UTC-7, Salvatore Stella wrote: Hi All, has anyone tried installing CHomP recently? For me it fails applying patches. It is an old-style package and apparently it is very

[sage-devel] CHomP

2019-05-03 Thread VulK
Hi All, has anyone tried installing CHomP recently? For me it fails applying patches. It is an old-style package and apparently it is very stale; does it provide any tangible speedup in `ChainComplex_class.homology` compared to the default pari algorithm? Thanks S. -- You received this

Re: [sage-devel] Re: CachedInParentMethod clear cache

2019-01-08 Thread VulK
I was being stupid and pretended to clear the cache by hand *facepalm*. I can confirm that doing things properly everything works as expected. Sorry about the noise S. * Nils Bruin [2019-01-08 08:47:54]: On Tuesday, January 8, 2019 at 6:21:39 AM UTC-8, Salvatore Stella wrote: Dear all,

Re: [sage-devel] Re: CachedInParentMethod clear cache

2019-01-08 Thread VulK
Dear all, sorry for disappearing on this. I am a little confused: if both parent and element refer to the same cache how is it possible that clearing one does not clear the other? S. * E. Madison Bray [2019-01-08 14:49:36]: On Tue, Jan 8, 2019 at 1:51 AM Nils Bruin wrote: On Monday,

[sage-devel] Inheriting from MPolynomialRing_libsingular crashes sage

2018-12-23 Thread VulK
Dear All, I just came acreoss the following strange behavior: {{{ sage: from sage.rings.polynomial.multi_polynomial_libsingular import MPolynomialRing_libsingular # This works as expected sage: MPolynomialRing_libsingular(QQ, 2, ['x','y'], 'degrevlex') Multivariate Polynomial Ring

Re: [sage-devel] Re: Delaying 8.5 or fast-tracking 8.6?

2018-12-20 Thread VulK
Same here * 'Martin R' via sage-devel [2018-12-20 00:36:35]: I have very little time, but if someone posts very precise compilation instructions to upgrade from current develop, I would let my computer play with it in the background. (currently compiling 8.5.rc1) In particular: was gap 4.10

[sage-devel] CachedInParentMethod clear cache

2018-12-18 Thread VulK
Dear All, I am working on some multivariate polynomial ring and I need to be able to repeatedly evaluate some elements numerically. Since the elements I am evaluating are few while the number of evaluations is high I thought to cache the result of this evaluation. Every now and then I need to

Re: [sage-devel] Re: Implementing rings of coordinates

2018-11-23 Thread VulK
There is now a ticket (#26741) ready for review in which the changes have been implemented. I decided not to refactor __call__ because the number of failing doctest was quite big. Maybe this is a project for a separate ticket. I have no idea on how to test reliably if the changes introduced

Re: [sage-devel] Re: Implementing rings of coordinates

2018-11-22 Thread VulK
You make a very good point, I'll try to be careful. I doubt this is a case of efficiency since now __call__ goes through redundant cases and even has an argument that is not used anywhere. Anyway I will cobble together something and we can do speed testing before merging. * Nils Bruin

Re: [sage-devel] Re: Implementing rings of coordinates

2018-11-22 Thread VulK
After a more accurate inspection, it appears that MPolynomialRing_polydict is in quite a bad shape. First of all it redefines __call__ which, if I read [1] correctly, should not be done. Second, within the many cases in __call__ one can find: {{{ 510 elif isinstance(x, dict): 511

Re: [sage-devel] Re: Implementing rings of coordinates

2018-11-22 Thread VulK
Done: https://trac.sagemath.org/ticket/26741 It appears that the change messes up with coercions. More details in the ticket description. S. * Simon King [2018-11-22 14:10:14]: On 2018-11-22, Simon King wrote: However, I believe it is bad usage to hard-code a certain class as output of

Re: [sage-devel] Re: Implementing rings of coordinates

2018-11-21 Thread VulK
funtionality to the elements. Thanks S. * Simon King [2018-11-21 12:03:24]: Dear S., On 2018-11-20, VulK wrote: I am trying to implement the ring of coordinates of a Lie group in the perspective of Peter-Weyl theorem. Concretely I would like to define a polynomial ring with infinitely many

Re: [sage-devel] Re: Implementing rings of coordinates

2018-11-21 Thread VulK
-20, VulK wrote: I am trying to implement the ring of coordinates of a Lie group in the perspective of Peter-Weyl theorem. Concretely I would like to define a polynomial ring with infinitely many generators each depending on two points on a lattice. These generators satisfy many relations

[sage-devel] Implementing rings of coordinates

2018-11-20 Thread VulK
Dear all, I am trying to implement the ring of coordinates of a Lie group in the perspective of Peter-Weyl theorem. Concretely I would like to define a polynomial ring with infinitely many generators each depending on two points on a lattice. These generators satisfy many relations but, for

Re: [sage-devel] first python3 build of sage

2017-04-20 Thread VulK
Indeed if one comments line 847 in src/setup.py the files looks to be there. Sage crashes anyway but now: VulK@bunion /mnt/backup/sage-py3 (git)-[my_py3] % ./sage -sh Starting subshell with Sage environment variables set. Don't forget to exit when you are done. Beware: * Do not do anything

Re: [sage-devel] first python3 build of sage

2017-04-20 Thread VulK
It looks to me that the various .so files get compiled but then removed just before the build finishes. Here is a snippet of the log: byte-compiling /mnt/backup/sage-py3/local/lib/python3.5/site-packages/sage/stats/r.py to r.cpython-35.pyc byte-compiling

[sage-devel] Re: How do I handle a bug I do not have time to fix?

2017-02-27 Thread VulK
Sorry for the mess, I just read the procedure on the developer's manual. I'll be creating a new ticket for the stopgap in a second. S. * Travis Scrimshaw [2017-02-27 09:01:03]: Hey Salvatore, The typical approach is to put a stopgap, but it is best to do it in such a

[sage-devel] Re: How do I handle a bug I do not have time to fix?

2017-02-27 Thread VulK
Hi Travis, thank you for the info. Could you please check that the branch public/ticket/22381 currently attached to the ticket is acceptable? Issues arise with any kind of input but only when there are frozen variables so I added the stopgap any time they are present. Is there a fast lane to

[sage-devel] How do I handle a bug I do not have time to fix?

2017-02-27 Thread VulK
Dear all, some time ago I reported a bug in the implementation of `ClusterQuiver` which yields wrong answers. The relevant ticket is #22381. To give you an idea things like this happen: {{{ sage: B = Matrix([[0,1,0],[-1,0,1],[0,-1,0],[2,0,0]]) sage: Q = ClusterQuiver(B)

Re: [sage-devel] A strange bug I cant't reproduce in any simpler way (LaurentPolynomialRing)

2017-02-20 Thread VulK
I just did it, it seems to work. Thanks S. * Daniel Krenn <kr...@aon.at> [2017-02-20 20:47:03]: On 2017-02-20 19:24, VulK wrote: Dear All, I just found a bug I can't really reproduce in any simpler way than the one I have here. I did not open a ticket yet on this because I would like t

[sage-devel] A strange bug I cant't reproduce in any simpler way (LaurentPolynomialRing)

2017-02-20 Thread VulK
Dear All, I just found a bug I can't really reproduce in any simpler way than the one I have here. I did not open a ticket yet on this because I would like to have a simpler way to explain the issue first. Any idea? {{{ sage: LQ = LaurentPolynomialRing(QQ, 'x0, x1, x2, y0, y1, y2,

Re: [sage-devel] RFC: correct way to deal with particular methods

2016-11-14 Thread VulK
on edit at line 384. The methods being wrapped are at lines 1047 and 2150. Thanks S. * Johan S. H. Rosenkilde <maill...@atuin.dk> [2016-11-07 09:45:57]: VulK writes: The first question is about which is the correct way to implement methods that are not always defined. I agree

[sage-devel] RFC: correct way to deal with particular methods

2016-11-06 Thread VulK
Dear all, I am writing to you to ask your opinion on the best way to address two issues that were raised during the review of #21254. People are quite unhappy on how these are addressed right now so I figured it would be better to ask for opinions on how to best implement them. The first

[sage-devel] Regression introduced by #21670 ?

2016-10-15 Thread VulK
We do our best to make it stable, but... A crash report was automatically generated with the following information: - A verbatim copy of the crash traceback. - A copy of your input history during this session. - Data on your current Sage configuration. It was left in the file named:

Re: [sage-devel] Sage and pylint

2016-09-22 Thread VulK
pylint complains only about the second. Best S. * Erik Bray <erik.m.b...@gmail.com> [2016-09-22 17:24:05]: On Fri, Sep 16, 2016 at 1:12 PM, VulK <etn45...@gmail.com> wrote: Hi, I thought this was a question for sage-devel because it is about tickets I am currently workin

Re: [sage-devel] Re: Sage's references: new policy?

2016-09-21 Thread VulK
* Thierry [2016-09-21 18:35:25]: Hi, bikeshedding for bikeshedding: - if we decide to centralize everything in a single file (but we should be aware that a backward move (e.g. for modularization) will require some work), why not using bibtex (there must be

Re: [sage-devel] Sage and pylint

2016-09-16 Thread VulK
hierry On Fri, Sep 16, 2016 at 12:55:29PM +0200, VulK wrote: Dear all, I am trying to use pylint to validate some of the code in a patch I wrote for sage and, unsurprisingly, I am getting several complaints because my system-wide pylint can't resolve modules like sage.something. What is the corre

[sage-devel] Sage and pylint

2016-09-16 Thread VulK
Dear all, I am trying to use pylint to validate some of the code in a patch I wrote for sage and, unsurprisingly, I am getting several complaints because my system-wide pylint can't resolve modules like sage.something. What is the correct way of doing this? Is there any other alternative to

Re: [sage-devel] line_profiler (%lprun) also broken from IPython upgrade

2016-09-01 Thread VulK
these might be useful: https://github.com/rkern/line_profiler/issues/61 https://github.com/rkern/line_profiler/issues/62 https://github.com/rkern/line_profiler/pull/65 https://github.com/rkern/line_profiler/pull/68 Best S. * Travis Scrimshaw [2016-09-01 07:03:31]: >I

Re: [sage-devel] Re: broken %attach and %debug ?

2016-08-26 Thread VulK
gt; [2016-08-26 16:23:53]: > VulK wrote: > >>and me too, this is really very annoying that %attach is broken.. > > +1 > > > > A related question: why do we implement %attach in sage rather than making a > > patch for upstream IPython? > > Yo

Re: [sage-devel] Re: broken %attach and %debug ?

2016-08-26 Thread VulK
>and me too, this is really very annoying that %attach is broken.. +1 A related question: why do we implement %attach in sage rather than making a patch for upstream IPython? S. * Frédéric Chapoton [2016-08-26 06:01:23]: >and me too, this is really very

Re: [sage-devel] Re: Iterators and KeyboardInterrupt

2016-08-23 Thread VulK
Indeed RecursivelyEnumeratedSet seems to be a good fit for my needs. The only problem I encountered so far is that it does not handle KeybordInterrupts nicely either: if you interrupt the computation of graded_component(n) then graded_component(m) with m [2016-08-23 00:51:34]: > > Are you

[sage-devel] Re: Iterators and KeyboardInterrupt

2016-08-22 Thread VulK
Hi All, thank you very much for all the inputs! > Breath-first search = Search & pray? ;-) > > (Possibly infinite apnoea can't be healthy.) /me fails :) > Well, one usually implements checkpoints for such things (continually > saving state to optionally resume later if interrupted). I am not

[sage-devel] Iterators and KeyboardInterrupt

2016-08-22 Thread VulK
Dear All, in a ticket (#21254) I recently created with Dylan Rupel I need to explore a (possibly) infinite n-regular tree in a breath-first search. The way it is implemented right now is via iterators. I am writing to you to ask if there is a preferred way to deal with user interaction and

Re: [sage-devel] Re: py3: what to do with cmp ?

2016-08-14 Thread VulK
you got me: I was including $SAGE_ROOT/src/build/ now the numbers agree S. * leif <not.rea...@online.de> [2016-08-14 16:55:23]: > leif wrote: > > VulK wrote: > >> Really weird, his is what I have: > >> > >> $ cd $SAGE_ROOT/src > >> $ grep __c

Re: [sage-devel] Re: py3: what to do with cmp ?

2016-08-14 Thread VulK
rea...@online.de> [2016-08-14 15:41:51]: > leif wrote: > > VulK wrote: > >> Getting rid of __cmp__ would be the cleaner way but a simple grep on > >> $SAGE_ROOT/src gives 915 occurrences of __cmp__, 624 of which are > >> definitions. > > ? I'm gettin

Re: [sage-devel] py3: what to do with cmp ?

2016-08-14 Thread VulK
Getting rid of __cmp__ would be the cleaner way but a simple grep on $SAGE_ROOT/src gives 915 occurrences of __cmp__, 624 of which are definitions. Is there any way we can automate the process? S. * Frédéric Chapoton [2016-08-14 05:41:01]: >As an intermediate step in

Re: [sage-devel] Re: Sage on Bash on Ubuntu on Windows

2016-08-03 Thread VulK
* leif <not.rea...@online.de> [2016-08-03 11:03:38]: > VulK wrote: > > On the topic of performances I just came across this post on phoronix: > > http://www.phoronix.com/scan.php?page=article=windows-10-lxcore=1 > > > > TL;DR: benchmarks give surprisingly

Re: [sage-devel] Re: Sage on Bash on Ubuntu on Windows

2016-08-03 Thread VulK
On the topic of performances I just came across this post on phoronix: http://www.phoronix.com/scan.php?page=article=windows-10-lxcore=1 TL;DR: benchmarks give surprisingly good performances provided you do not access the filesystem. At the moment, while running sage could be ok, this would make

Re: [sage-devel] Sage on Bash on Ubuntu on Windows

2016-07-26 Thread VulK
. * Erik Bray <erik.m.b...@gmail.com> [2016-07-26 13:25:31]: > On Tue, Jul 26, 2016 at 10:19 AM, VulK <etn45...@gmail.com> wrote: > > Hi All, > > Some time ago I briefly played with Bash on Ubuntu on Windows with some > > limited success. The situation dramaticall

[sage-devel] Sage on Bash on Ubuntu on Windows

2016-07-26 Thread VulK
Corporation. All rights reserved. C:\Users\VulK>bash root@DESKTOP-U13FH0M:/mnt/c/Users/VulK# uname -a Linux DESKTOP-U13FH0M 3.4.0+ #1 PREEMPT Thu Aug 1 17:06:05 CST 2013 x86_64 x86_64 x86_64 GNU/Linux root@DESKTOP-U13FH0M:~# apt-add-repository -y ppa:a

Re: [sage-devel] Re: Heavy-computation @property in Matrix class

2016-04-27 Thread VulK
A.current_seed as a property or should I stick to methods? Thanks S. * Johan S. R. Nielsen <santaph...@gmail.com> [2016-04-27 14:24:33]: > VulK writes: > > sage: B = matrix() > > sage: B.T.roo > > > > and get > > > > sage: B.T.rook_vector > > I see, did

Re: [sage-devel] Re: Heavy-computation @property in Matrix class

2016-04-27 Thread VulK
This example is dumb because it does not give any real benefit but it will do. On the command line you could run something like sage: B = matrix() sage: B.T.roo and get sage: B.T.rook_vector but sage: sage: B.transpose().roo will complete to useless stuff. Now as I said this does not make

Re: [sage-devel] Re: Heavy-computation @property in Matrix class

2016-04-27 Thread VulK
One advantage of properties over methods is that they autocomplete S. * Johan S. R. Nielsen [2016-04-27 13:22:57]: > > Would it be feasible to let properties return some kind of "Undefined" > > or "NotImplemented" or "None", rather than throwing an exception? > > That

Re: [sage-devel] Re: LaurentPolynomialRing and PolynomialRing behave inconsistently -- Request For Comments

2016-04-24 Thread VulK
Dear All, sorry for the late reply: my todo list came knocking at my door and required immediate attention. I did a small test and it appears that both Polynomial and LaurentPolynomial behave in the same way with respect to coercion. On the other hand their behavior under conversion is different.

[sage-devel] LaurentPolynomialRing and PolynomialRing behave inconsistently -- Request For Comments

2016-04-08 Thread VulK
Dear All, for some project I have been working on for some time I found myself interested in comparing elements of two different LaurentPolynomialRing. Unfortunately, at the moment this is somewhat broken. The current behaviour is this: sage: L1 = LaurentPolynomialRing(ZZ, 'x0,x1,x2,y0,y1,y2')

Re: [sage-devel] The package system: redundancy

2016-03-07 Thread VulK
Sorry, apparently I am late to the patch by few minutes thanks for the pointers though, I'll keep surfing trac for related work in progress. As for gcc on my machine being reinstalled by sage I guess I do have an old version: 4.7 Thanks S. * Jeroen Demeyer

Re: [sage-devel] Re: Trac - internal error

2016-01-15 Thread VulK
Same here: http://trac.sagemath.org/ticket/19667 S. * Johan S. R. Nielsen [2016-01-15 16:40:37]: > Same thing here, #19251. > > Johan > > david.lu...@inria.fr writes: > > > Hello, > > > > Same thing with some of tickets: #19653, #19666, #19722, #19422 and #19623 > > >

[sage-devel] Re: Various issues with LaurentPolynomialRing

2015-11-06 Thread VulK
Here is a quick patch for one of the listed issues: http://trac.sagemath.org/ticket/19538 S. * Travis Scrimshaw [2015-11-04 16:37:17]: >Hey Salvatore, > > first of all thank you for your answer, it looks like you are one of > the > person I pester the

[sage-combinat-devel] More LaurentPolynomialRing insanity

2015-11-03 Thread VulK
Dear all, I just noted the following: sage: R = LaurentPolynomialRing(ZZ,'x,y') sage: T = R.remove_var('x') sage: T.inject_variables() Defining y sage: y in T True sage: y in R True As one should expect, now for a second try sage: R = LaurentPolynomialRing(ZZ,'x,y,z') sage: T =

Re: [sage-combinat-devel] More LaurentPolynomialRing insanity

2015-11-03 Thread VulK
Thank you for the pointer, I will move the discussion there. S. * Nicolas M. Thiery <nicolas.thi...@u-psud.fr> [2015-11-03 17:04:31]: > On Tue, Nov 03, 2015 at 04:37:25PM +0100, VulK wrote: > > I just noted the following: > > > > sage: R = LaurentPolynomia

[sage-combinat-devel] Fast polynomial powers

2015-10-21 Thread VulK
Dear all, As some of you might know I am trying to optimize the way in which cluster algebras are implemented in sage. In my current implementation one of the biggest bottleneck happens when I take powers of polynomials in n variables (n is usually much smaller than 10) with integer

[sage-combinat-devel] Re: Fraction field elements are not simplified

2015-10-14 Thread VulK
Dear All, here is a brief status update on this issue. TL;DR: Laurent Polynomial Ring does not provide a gcd implementation. Recall that we are in this situation: sage: L = LaurentPolynomialRing(LaurentPolynomialRing(ZZ,'t'),'x') sage: R = L.fraction_field() sage: R.inject_variables() Defining x

[sage-combinat-devel] Fraction field elements are not simplified

2015-10-09 Thread VulK
Dear all, I just noted the following odd behaviour: sage: L = LaurentPolynomialRing(ZZ, 'x').fraction_field() sage: L.inject_variables() Defining x sage: x/x 1 As one should expect but if we change the base ring then things get messy: sage: L =

Re: [sage-combinat-devel] Root systems do not define variables correctly

2012-07-13 Thread VulK
Hi, I guess injecting simple roots would be my choice. If not possible, at least, it would be cleaner to remove inject_variables from the auto completion list for A. S. * Nicolas M. Thiery nicolas.thi...@u-psud.fr [2012-07-12 23:47:34]: On Thu, Jul 12, 2012 at 11:08:54PM -0400, VulK wrote: I

[sage-combinat-devel] Root systems do not define variables correctly

2012-07-12 Thread VulK
Hi, I just noticed the following odd behaviour: sage: L=RootSystem(['A',2]).root_lattice() sage: L.inject_variables() --- ValueErrorTraceback (most recent call last)

Re: [sage-combinat-devel] B-matrix class of finite type cluster algebras

2012-03-10 Thread VulK
Sorry I meant there are problem applying trac_6588-categories-root_systems-review-nt.patch S. * Christian Stump christian.st...@gmail.com [2012-03-10 18:43:30]: Dear Salvatore,        sage: S=ClusterSeed(['E',8])        sage: T=S.principal_extension()        sage: T.b_matrix_class()