Re: [sage-devel] Re: Methods for polyhedron are ring dependant?

2015-10-13 Thread Jan Keitel
base_RDF.py says > > The point > > (.5*v0 + .5*v1) - 1e-7*v2 > > is definitely not in the regular pentagon. But Sage answers that it is. > > If you start taking barycenters, this is the kind of things you can run > into. > > >> On 13/10/15 08:30, J

Re: [sage-devel] Re: Methods for polyhedron are ring dependant?

2015-10-13 Thread Jan Keitel
False > > sage: v = (.5*v0 + .5*v1) - 1e-7*v2 > sage: v in P > True > > Everything is fine with base_ring=AA (and using exact vectors of course). > > Vincent > > On 13/10/15 08:30, Jan Keitel wrote: > > Hi Vincent, > > > > that'

Re: [sage-devel] Re: Methods for polyhedron are ring dependant?

2015-10-13 Thread Jan Keitel
is an entirely different question - all I'm saying is that _is_positive checks (with fuzziness) whether that the argument is non-negative, but not whether it is non-zero. Maybe that is what should be changed. Am Dienstag, 13. Oktober 2015 12:19:50 UTC+2 schrieb vdelecroix: > > On 13/

[sage-devel] Re: Methods for polyhedron are ring dependant?

2015-10-13 Thread Jan Keitel
In this particular case the problem can probably be resolved by being a bit stricter with the check in interior_contains: Instead of checking return self.polyhedron()._is_positive( self.eval(Vobj) ) one should have return self.polyhedron()._is_positive( self.eval(Vobj) ) and not self.polyhedr

[sage-devel] Re: topcom vs TOPCOM

2015-08-04 Thread Jan Keitel
So what's the procedure for this? If I understand correctly, it needs to be removed from MIRROR/optional/list. Am Montag, 3. August 2015 15:13:55 UTC+2 schrieb Volker Braun: > > Agree, should be removed. > > On Monday, August 3, 2015 at 2:31:06 PM UTC+2, Jan Keitel wrote: >

[sage-devel] topcom vs TOPCOM

2015-08-03 Thread Jan Keitel
I just noticed that sage -optional lists two different TOPCOM packages, namely topcom and TOPCOM. Installing the former works, while the installation of the latter spits out the following: jkeitel@pcl337b:~/sage/sage> ./sage -i TOPCOM Attempting to download package TOPCOM >>> Checking online lis

[sage-devel] Re: git port blocked

2015-07-23 Thread Jan Keitel
Same here: jkeitel@pcl337b:~/sage/sage> git pull trac develop ssh: connect to host trac.sagemath.org port : Connection timed out fatal: Could not read from remote repository. Am Donnerstag, 23. Juli 2015 13:23:34 UTC+2 schrieb Jeroen Demeyer: > > On my machine, "git fetch" no longer works an

[sage-devel] Re: Poll: Supplemental graphical visualizations

2015-05-04 Thread Jan Keitel
[X] Yes, I want graphical user interfaces that make use of the graphical abilities Am Dienstag, 5. Mai 2015 00:54:15 UTC+8 schrieb Volker Braun: > > Since the last poll about graphics was immediately derailed by unrelated > command line questions, let me try once more: Should selected objects >

[sage-devel] Re: Patchbot fails after first attempt

2015-04-21 Thread Jan Keitel
ot and relaunch it with a config file chosen >>> using >>> >>> --config=CONFIG specify the config file >>> >>> Frederic >>> >>> >>> Le mardi 21 avril 2015 16:06:30 UTC+2, Jan Keitel a écrit : >>>>

[sage-devel] Re: Patchbot fails after first attempt

2015-04-21 Thread Jan Keitel
> > In principle, it should update itself at every develop release. But let us > see what happen when 6.7.beta0 is out. > > Frederic > > Le mardi 14 avril 2015 11:49:48 UTC+2, Jan Keitel a écrit : >> >> Whatever the problem was before, it is gone now - at least it just

[sage-devel] Re: Bad display of tuples in Sage 6.6 notebooks

2015-04-17 Thread Jan Keitel
The culprit is the following line in sage.repl.rich_output.backend_base.py: mathjax = MathJax().eval(obj, mode='plain', combine_all=True) If combine_all is set to False, then the tuples render as expected. Volker, is there a reason for changing this or should I open a ticket? By the way, it's

[sage-devel] Re: Patchbot fails after first attempt

2015-04-14 Thread Jan Keitel
ot-2.3.2.spkg > 2) pull the develop branch of sage > git pull trac develop > git ch develop -b patchbot/base > 3) run the patchbot with sage -patchbot --skip-base ? > > Fred > > Le lundi 13 avril 2015 21:03:44 UTC+2, Jan Keitel a écrit : >> >> Could you mayb

[sage-devel] Re: Patchbot fails after first attempt

2015-04-13 Thread Jan Keitel
be full. I'm not sure what's going wrong. Best, Jan Am Montag, 13. April 2015 17:28:52 UTC+2 schrieb Jan Keitel: > > No worries, thanks for all the support. I'll try a clean install again > tomorrow and this time, I'll save the full log. > > As far as 15047 is co

[sage-devel] Re: Patchbot fails after first attempt

2015-04-13 Thread Jan Keitel
.2 available, but it will only work with sage > -patchbot --skip-base > > sorry for the trouble. I try do do my best to enhance the patchbot, but > there may be some road bumps during the process. > > Frederic > > Le lundi 13 avril 2015 16:27:23 UTC+2, Jan Keitel a écrit : &g

[sage-devel] Re: Patchbot fails after first attempt

2015-04-13 Thread Jan Keitel
> and tell me what happens ? > > Another sanity check would be > > sage -patchbot --skip-base --plugin-only --ticket=18177 > > or whatever ticket you want. > > Frederic > Le lundi 13 avril 2015 14:51:53 UTC+2, Jan Keitel a écrit : >> >> Hi there, >>

[sage-devel] Patchbot fails after first attempt

2015-04-13 Thread Jan Keitel
Hi there, I just installed a patchbot (2.3.1) in a clean Sage installation. After building Sage correctly (I had built it before), it failed while building the documentation with the following message: .. [reference] structure: 10 todos, 38 index, 2 citations, 37 modules [reference] tenso

[sage-devel] Re: Importing patches fails after calling dev.git.am()

2014-05-21 Thread Jan Keitel
Thank you Simon - that did the trick. :-) Am Dienstag, 20. Mai 2014 21:22:13 UTC+2 schrieb Simon King: > > Hi! > > On 2014-05-20, Jan Keitel > wrote: > > git: 'am' is not a git command. See 'git --help'. > > Did you mean one of these? > &g

[sage-devel] Importing patches fails after calling dev.git.am()

2014-05-20 Thread Jan Keitel
Hi there, I'm posting here instead of opening a ticket right away because I'm not sure whether the error I'm getting is my fault or not. The scenario is the following: I import a patch that does not apply cleanly and take care of the .rej files by hand. After I'm done with that, I tell the dev

[sage-devel] Re: "The name of this deprecated function can not be determined"

2014-04-08 Thread Jan Keitel
Am Montag, 7. April 2014 23:36:01 UTC+2 schrieb Andrey Novoseltsev: > Hello, > > I am trying to deprecate a function with an alias which seems to be very > straightforward: > http://git.sagemath.org/sage.git/commit/?id=2080f3cf0365f4b568ce1129f3d0dc448fe80f11 > but it results in the following err