Re: [sage-devel] Re: Declaring a parent in a category as a finite enumerated set

[Kwankyu Lee]

One more nice example.

sage -t src/sage/combinat/integer_vector_weighted.py
**
File "src/sage/combinat/integer_vector_weighted.py", line 125, in 
sage.combinat.integer_vector_weighted.WeightedIntegerVectors_all.__init__
Failed example:
C.category()
Expected:
Join of Category of sets with grading and Category of infinite 
enumerated sets
Got:
Category of infinite enumerated sets with grading

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: giacpy depends (silently) on SageObject

[leif]

leif wrote:
> leif wrote:
>> leif wrote:
>>> Vincent Delecroix wrote:
 Hello,

 In the optional package giacpy there are some extension classes that
 depend on SageObject. Hence if I do some modification to SageObject and
 perform "make" the giacpy package is broken. Is there a solution to
 rebuild external packages that depends on sagelib when doing "make"?
>>>
>>> Try adding $(SAGERUNTIME) to its dependencies file, *before* the '|'.
> 
> Next suggestion (hopefully the last, and a working one):
> 
> Instead of $(SAGERUNTIME), add
> 
> $(SAGE_SRC)/build/cythonized/sage/structure/sage_object.c
> 
> (again, *before* the pipe, but still put $(SAGERUNTIME) after it).

P.S.:  (Sorry, forgot to mention:)

You obviously have to recreate Sage's Makefile after changing giacpy's
dependencies of course.


The probably easiest, but also the cleanest way is to bump giacpy's
(Sage) patch level (in its package-version.txt), i.e., append a '.p0' there.

I haven't tried with giacpy (as I don't want to spam my Sage
installations with further optional packages), but otherwise works for
me.  If I touch src/build/cythonized/sage/structure/sage_object.c (which
will also happen in case you modify sage_object.{pxd,pyx}), running
'make build' rebuilds the extension module and afterwards the package to
whose dependencies I had added what I mentioned above.


-leif


-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: giacpy depends (silently) on SageObject

[leif]

leif wrote:
> leif wrote:
>> Vincent Delecroix wrote:
>>> Hello,
>>>
>>> In the optional package giacpy there are some extension classes that
>>> depend on SageObject. Hence if I do some modification to SageObject and
>>> perform "make" the giacpy package is broken. Is there a solution to
>>> rebuild external packages that depends on sagelib when doing "make"?
>>
>> Try adding $(SAGERUNTIME) to its dependencies file, *before* the '|'.

Next suggestion (hopefully the last, and a working one):

Instead of $(SAGERUNTIME), add

$(SAGE_SRC)/build/cythonized/sage/structure/sage_object.c

(again, *before* the pipe, but still put $(SAGERUNTIME) after it).


-leif

>>
>> Unfortunately we don't have a file with a timestamp for the Sage library
>> in local/var/lib/sage/installed/ that could be touched.
> 
> And sagelib is a phony target, but you could abuse
> local/var/lib/sage/installed/ipython-* since $(SAGERUNTIME) depends on that.
> 
> Not sure what other (useless) rebuilds that would trigger though.
> 
> The only other way I see at the moment is to actually add the Sage
> sourcefile to giacpy's dependencies, but wait -- cysignals is already in
> giacpy's dependencies, so you could abuse
> local/var/lib/sage/installed/cysignals-* as well.
> 
> 
> Better open a ticket...
> 
> 
> -leif


-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: giacpy depends (silently) on SageObject

[leif]

leif wrote:
> Vincent Delecroix wrote:
>> Hello,
>>
>> In the optional package giacpy there are some extension classes that
>> depend on SageObject. Hence if I do some modification to SageObject and
>> perform "make" the giacpy package is broken. Is there a solution to
>> rebuild external packages that depends on sagelib when doing "make"?
> 
> Try adding $(SAGERUNTIME) to its dependencies file, *before* the '|'.
> 
> Unfortunately we don't have a file with a timestamp for the Sage library
> in local/var/lib/sage/installed/ that could be touched.

And sagelib is a phony target, but you could abuse
local/var/lib/sage/installed/ipython-* since $(SAGERUNTIME) depends on that.

Not sure what other (useless) rebuilds that would trigger though.

The only other way I see at the moment is to actually add the Sage
sourcefile to giacpy's dependencies, but wait -- cysignals is already in
giacpy's dependencies, so you could abuse
local/var/lib/sage/installed/cysignals-* as well.


Better open a ticket...


-leif


-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: giacpy depends (silently) on SageObject

[leif]

Vincent Delecroix wrote:
> Hello,
> 
> In the optional package giacpy there are some extension classes that
> depend on SageObject. Hence if I do some modification to SageObject and
> perform "make" the giacpy package is broken. Is there a solution to
> rebuild external packages that depends on sagelib when doing "make"?

Try adding $(SAGERUNTIME) to its dependencies file, *before* the '|'.

Unfortunately we don't have a file with a timestamp for the Sage library
in local/var/lib/sage/installed/ that could be touched.


-leif


-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] giacpy depends (silently) on SageObject

[Vincent Delecroix]

Hello,

In the optional package giacpy there are some extension classes that 
depend on SageObject. Hence if I do some modification to SageObject and 
perform "make" the giacpy package is broken. Is there a solution to 
rebuild external packages that depends on sagelib when doing "make"?


Cheers,
Vincent

--
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

[leif]

Simon Brandhorst wrote:
> So far I am using precompiled binaries. They work. Now I am thinking on
> writing my own branch/contributing to sage so I followed the instructions on
> 
> http://doc.sagemath.org/html/en/developer/walk_through.html
> 
> to get a developer version of sage.
> Basically I just typed
> 
> git clone git://github.com/sagemath/sage.git
> cd sage
> git checkout develop
> make
> 
> And get an error Message:
> [singular-3.1.7p1.p2] checking size of long... (cached) 0
> [singular-3.1.7p1.p2] checking size of void*... 8
> [singular-3.1.7p1.p2] checking size of double... 8
> [singular-3.1.7p1.p2] checking size of size_t... 8
> [singular-3.1.7p1.p2] configure: error: need equal sizes for long and void*
> [singular-3.1.7p1.p2] configure: error: ./configure failed for omalloc
> [singular-3.1.7p1.p2] Unable to configure Singular.
> [singular-3.1.7p1.p2] Error building Singular (error in config).

sizeof(long) is zero...  Nice.


> (the log is too big to attach)

Well, the last lines should contain "The following packages may have
failed to build:" along with paths to the temporary build directory of
Singular and the log file created for that package.

Since Singular's 'configure' already failed, we'd need the config.log
file(s) from subfolders of the build directory mentioned.

Also logs/pkgs/singular-3.1.7p1.p2.log shouldn't be that long; from that
we could see /which/ 'configure' failed (presumably indeed that of
omalloc), as Singular consists of a couple of components with their own
'configure' scripts.


-leif


-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

[Nils Bruin]

On Wednesday, August 31, 2016 at 12:38:51 PM UTC-7, Simon Brandhorst wrote:
>
> So far I am using precompiled binaries. They work. Now I am thinking on 
> writing my own branch/contributing to sage so I followed the instructions on
>
> http://doc.sagemath.org/html/en/developer/walk_through.html
>
> to get a developer version of sage.
> Basically I just typed
>
> git clone git://github.com/sagemath/sage.git
> cd sage
> git checkout develop
> make
>
> And get an error Message:
> [singular-3.1.7p1.p2] checking size of long... (cached) 0
>
>
That's obviously wrong. It should get 8 there. You might want to do a:

$ grep "size of long" install.log

to see if on other occasions the system was able to figure out a more 
sensible value.

In any case, the first thing to try would be to figure out how to wipe the 
configure cache and hope that on a fresh run it will be able to figure out 
the right value.


-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Error building sage source "error: need equal sizes for long and void*"

[Simon Brandhorst]

Just in case some more hardware details:

Architecture:  x86_64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little Endian
CPU(s):8
On-line CPU(s) list:   0-7
Thread(s) per core:2
Core(s) per socket:4
Socket(s): 1
NUMA node(s):  1
Vendor ID: GenuineIntel
CPU family:6
Model: 60
Model name:Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz
Stepping:  3
CPU MHz:   2399.906
CPU max MHz:   3400.
CPU min MHz:   800.
BogoMIPS:  4789.26
Virtualization:VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache:  256K
L3 cache:  6144K
NUMA node0 CPU(s): 0-7
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall 
nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl 
xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor 
ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic 
movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm epb 
tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep 
bmi2 erms invpcid xsaveopt dtherm ida arat pln pts




H/W path   Device Class  Description

  system X761X (To be filled by O.E.M.)
/0busX761X
/0/0  memory 64KiB BIOS
/0/3e processor  Intel(R) Core(TM) i7-4700HQ CPU @ 
2.40GHz
/0/3e/3f  memory 1MiB L2 cache
/0/3e/40  memory 256KiB L1 cache
/0/3e/41  memory 6MiB L3 cache
/0/42 memory 16GiB System Memory
/0/42/0   memory 8GiB SODIMM DDR3 Synchronous 1600 
MHz (0.6 ns)
/0/42/1   memory 8GiB SODIMM DDR3 Synchronous 1600 
MHz (0.6 ns)
/0/100bridge Xeon E3-1200 v3/4th Gen Core 
Processor DRAM Controller
/0/100/1  bridge Xeon E3-1200 v3/4th Gen Core 
Processor PCI Express x16 Controlle
/0/100/1/0displayGK106M [GeForce GTX 765M]
/0/100/1/0.1  multimedia GK106 HDMI Audio Controller
/0/100/2  display4th Gen Core Processor Integrated 
Graphics Controller
/0/100/14 bus8 Series/C220 Series Chipset 
Family USB xHCI
/0/100/14/0usb3   busxHCI Host Controller
/0/100/14/0/5 input  Razer Orochi
/0/100/14/0/7 communication  Bluetooth wireless interface
/0/100/14/0/8 multimedia USB 2.0 Webcam Device
/0/100/14/0/e input  MSI EPF USB
/0/100/14/1usb4   busxHCI Host Controller
/0/100/16 communication  8 Series/C220 Series Chipset 
Family MEI Controller #1
/0/100/1a bus8 Series/C220 Series Chipset 
Family USB EHCI #2
/0/100/1a/1usb1   busEHCI Host Controller
/0/100/1a/1/1 busUSB hub
/0/100/1b multimedia 8 Series/C220 Series Chipset High 
Definition Audio Controller
/0/100/1c bridge 8 Series/C220 Series Chipset 
Family PCI Express Root Port #1
/0/100/1c.2   bridge 8 Series/C220 Series Chipset 
Family PCI Express Root Port #3
/0/100/1c.3   bridge 8 Series/C220 Series Chipset 
Family PCI Express Root Port #4
/0/100/1c.3/0  enp4s0 networkKiller E220x Gigabit Ethernet 
Controller
/0/100/1c.4   bridge 8 Series/C220 Series Chipset 
Family PCI Express Root Port #5
/0/100/1c.4/0  wlp5s0 networkWireless 7260
/0/100/1d bus8 Series/C220 Series Chipset 
Family USB EHCI #1
/0/100/1d/1usb2   busEHCI Host Controller
/0/100/1d/1/1 busUSB hub
/0/100/1f bridge HM87 Express LPC Controller
/0/100/1f.2   storage8 Series/C220 Series Chipset 
Family 6-port SATA Controller 1 [AH
/0/100/1f.3   bus8 Series/C220 Series Chipset 
Family SMBus Controller
/0/1   scsi0  storage
/0/1/0.0.0 /dev/sda   disk   128GB SanDisk SD6SF1M1
/0/1/0.0.0/1   /dev/sda1  volume 498MiB Windows NTFS volume
/0/1/0.0.0/2   /dev/sda2  volume 99MiB Windows FAT volume
/0/1/0.0.0/3   /dev/sda3  volume 127MiB reserved partition
/0/1/0.0.0/4   /dev/sda4  volume 1023MiB Windows FAT volume
/0/1/0.0.0/5   /dev/sda5  volume 117GiB Windows NTFS volume
/0/2   scsi4  storage
/0/2/0.0.0 /dev/sdb   disk   1TB ST1000LM024 HN-M
/0/2/0.0.0/1   /dev/sdb1  

[sage-devel] Error building sage source "error: need equal sizes for long and void*"

[Simon Brandhorst]

So far I am using precompiled binaries. They work. Now I am thinking on 
writing my own branch/contributing to sage so I followed the instructions on

http://doc.sagemath.org/html/en/developer/walk_through.html

to get a developer version of sage.
Basically I just typed

git clone git://github.com/sagemath/sage.git
cd sage
git checkout develop
make

And get an error Message:
[singular-3.1.7p1.p2] checking size of long... (cached) 0
[singular-3.1.7p1.p2] checking size of void*... 8
[singular-3.1.7p1.p2] checking size of double... 8
[singular-3.1.7p1.p2] checking size of size_t... 8
[singular-3.1.7p1.p2] configure: error: need equal sizes for long and void*
[singular-3.1.7p1.p2] configure: error: ./configure failed for omalloc
[singular-3.1.7p1.p2] Unable to configure Singular.
[singular-3.1.7p1.p2] Error building Singular (error in config).

(the log is too big to attach)
What went wrong?

So here are the system details:



Linux 4.6.7-300.fc24.x86_64 #1 SMP Wed Aug 17 18:48:43 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

LSB Version:
:core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch
Distributor ID:Fedora
Description:Fedora release 24 (Twenty Four)
Release:24
Codename:TwentyFour

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Bug in FreeQuadraticModule.discriminant

[Simon Brandhorst]

Sorry for posting twice. Got confused after the first time since the post 
did not appear right away.

I can do the next step and open a ticket. Though first I have to get the 
source code of sage compiled... (was working with binaries before)

I'll post the log file in another thread.


On Wednesday, August 31, 2016 at 4:58:42 PM UTC+2, Frédéric Chapoton wrote:
>
> yes, indeed this is a bug. Thanks for reporting.
>
> Would you like to make the next step to solve that ? Then you should ask 
> for an account on trac.sagemath.org and open a ticket.
>
> Instructions are available here: 
> http://www.sagemath.org/git-developer-guide/
>
> Frederic
>
> Le mercredi 31 août 2016 15:38:17 UTC+2, Simon Brandhorst a écrit :
>>
>> {{{
>> sage: q=FreeQuadraticModule(ZZ,2,inner_product_matrix=1)
>> sage: q
>> Ambient free quadratic module of rank 2 over the principal ideal domain 
>> Integer Ring
>> Inner product matrix:
>> [1 0]
>> [0 1]
>> sage: q.determinant()
>> 1
>> sage: q.discriminant()
>> -2
>> }}}
>>
>>
>> This output is wrong. The discriminant should be -1. 
>>
>> The following is another related bug. I guess thats where the error of 
>> the first bug lies as well.
>>
>>
>> {{{
>> sage: q=FreeQuadraticModule(QQ,2,inner_product_matrix=1)
>> sage: q.determinant()
>> 1
>> sage: q.discriminant()
>>
>> ---
>> RuntimeError  Traceback (most recent call 
>> last)
>>  in ()
>> > 1 q.discriminant()
>>
>> /usr/lib/sagemath/local/lib/python2.7/site-packages/sage/modules/free_quadratic_module.pyc
>>  
>> in discriminant(self)
>> 377 else:
>> 378 r = (n-1)//2
>> --> 379 return (-1)^r*self.gram_matrix().determinant()
>> 380 
>> 381 def gram_matrix(self):
>>
>> sage/structure/element.pyx in sage.structure.element.Element.__xor__ 
>> (/usr/lib/sagemath//src/build/cythonized/sage/structure/element.c:8229)()
>>
>> RuntimeError: Use ** for exponentiation, not '^', which means xor
>> in Python, and has the wrong precedence.
>> }}}
>>
>> This occurred on two different machines running sage 7.0 and 7.2 on 
>> Ubuntu 14.04.4 LTS and Fedora 24
>> (both x64).
>>
>> Sorry if this is not following some conventions ... it is my first bug 
>> report. 
>>
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Good news on the Windows/Cygwin front

[Erik Bray]

On Wed, Aug 31, 2016 at 6:14 PM, Travis Scrimshaw  wrote:
> I was able to get Cygwin64 to build successfully using 7.4.beta2 + Pynac
> 0.6.9 upgrade (#21369) + interpreter hack (#19868). I did have an issue with
> twisted not picking up zope_interface, but I was able to fix it by forcing a
> reinstall of zope_interface and then building twisted again.
>
> For Cygwin32, I'm stuck at pycrypto (#21236).
>
> Best,
> Travis

Thanks for giving it a try!  I'm surprised actually that it worked,
since I still have a few patches that I haven't posted yet (though I
think those have more to do with getting some tests to pass, than
actually building).

I have a nicer patch for the autogen.interpreters issue, but it
depends on https://trac.sagemath.org/ticket/20730 being accepted
first.

I do hope to look into getting Cygwin32 builds working eventually too,
and will look at the issue with pycrypto if I get a chance.

Thanks,
Erik

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Good news on the Windows/Cygwin front

[Travis Scrimshaw]

I was able to get Cygwin64 to build successfully using 7.4.beta2 + Pynac 
0.6.9 upgrade (#21369) + interpreter hack (#19868). I did have an issue 
with twisted not picking up zope_interface, but I was able to fix it by 
forcing a reinstall of zope_interface and then building twisted again.

For Cygwin32, I'm stuck at pycrypto (#21236 
).

Best,
Travis

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Bug in FreeQuadraticModule.discriminant()

[John Cremona]

On 31 August 2016 at 16:24, leif  wrote:

> John Cremona wrote:
> > Indeed, that is a bug in line 371 of the file
> > sage/modules/free_quadratic_module.py -- an easy fix.
>
> ... and more than 8 years old.
>
> The check whether the rank is even or not is useless as well; '//' in
> Python is integer division (taking the floor).
>

Agreed (not that n is the 'rank' not r!


>
> (And the docstrings don't use proper markup...)
>
>
> > Perhaps someone ought to look through all occurrences of ^ in .py files
> > outside of docstrings (where they are OK thanks to preparsing).
>
> Well, there are a couple of valid xor uses in the Sage library as well.
>

Certainly, but a human would be able to work out which ones were really
supposed to be xor!

John


>
>
> -leif
>
> > On 31 August 2016 at 13:44, Simon Brandhorst  > > wrote:
> >
> >
> > {
> > sage: q=FreeQuadraticModule(ZZ,2,inner_product_matrix=1)
> > sage: q
> > Ambient free quadratic module of rank 2 over the principal ideal
> > domain Integer Ring
> > Inner product matrix:
> > [1 0]
> > [0 1]
> > sage: q.determinant()
> > 1
> > sage: q.discriminant()
> > -2
> > }
> > #The expected value here is -1
> >
> > The following example should clarity what is wrong.
> > {
> > sage: q=FreeQuadraticModule(QQ,2,inner_product_matrix=1)
> > sage: q.determinant()
> > 1
> > sage: q.discriminant()
> > 
> ---
> > RuntimeError  Traceback (most recent
> > call last)
> >  in ()
> > > 1 q.discriminant()
> >
> > /usr/lib/sagemath/local/lib/python2.7/site-packages/sage/
> modules/free_quadratic_module.pyc
> > in discriminant(self)
> > 377 else:
> > 378 r = (n-1)//2
> > --> 379 return (-1)^r*self.gram_matrix().determinant()
> > 380
> > 381 def gram_matrix(self):
> >
> > sage/structure/element.pyx in sage.structure.element.Element.__xor__
> > (/usr/lib/sagemath//src/build/cythonized/sage/structure/
> element.c:8229)()
> >
> > RuntimeError: Use ** for exponentiation, not '^', which means xor
> > in Python, and has the wrong precedence.
> > }
> >
> > This happened with sage 7.0 and 7.2 on two different machines.
> > (Ubuntu 14.04.4 LTS, and fedora 24)
>
>
> --
> 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 post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Bug in FreeQuadraticModule.discriminant()

[leif]

John Cremona wrote:
> Indeed, that is a bug in line 371 of the file
> sage/modules/free_quadratic_module.py -- an easy fix.

... and more than 8 years old.

The check whether the rank is even or not is useless as well; '//' in
Python is integer division (taking the floor).

(And the docstrings don't use proper markup...)


> Perhaps someone ought to look through all occurrences of ^ in .py files
> outside of docstrings (where they are OK thanks to preparsing).

Well, there are a couple of valid xor uses in the Sage library as well.


-leif

> On 31 August 2016 at 13:44, Simon Brandhorst  > wrote:
> 
> 
> {
> sage: q=FreeQuadraticModule(ZZ,2,inner_product_matrix=1)
> sage: q
> Ambient free quadratic module of rank 2 over the principal ideal
> domain Integer Ring
> Inner product matrix:
> [1 0]
> [0 1]
> sage: q.determinant()
> 1
> sage: q.discriminant()
> -2
> }
> #The expected value here is -1
> 
> The following example should clarity what is wrong.
> {
> sage: q=FreeQuadraticModule(QQ,2,inner_product_matrix=1)
> sage: q.determinant()
> 1
> sage: q.discriminant()
> 
> ---
> RuntimeError  Traceback (most recent
> call last)
>  in ()
> > 1 q.discriminant()
> 
> 
> /usr/lib/sagemath/local/lib/python2.7/site-packages/sage/modules/free_quadratic_module.pyc
> in discriminant(self)
> 377 else:
> 378 r = (n-1)//2
> --> 379 return (-1)^r*self.gram_matrix().determinant()
> 380
> 381 def gram_matrix(self):
> 
> sage/structure/element.pyx in sage.structure.element.Element.__xor__
> (/usr/lib/sagemath//src/build/cythonized/sage/structure/element.c:8229)()
> 
> RuntimeError: Use ** for exponentiation, not '^', which means xor
> in Python, and has the wrong precedence.
> }
> 
> This happened with sage 7.0 and 7.2 on two different machines.
> (Ubuntu 14.04.4 LTS, and fedora 24)


-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Bug in FreeQuadraticModule.discriminant

[Frédéric Chapoton]

yes, indeed this is a bug. Thanks for reporting.

Would you like to make the next step to solve that ? Then you should ask 
for an account on trac.sagemath.org and open a ticket.

Instructions are available here: 
http://www.sagemath.org/git-developer-guide/

Frederic

Le mercredi 31 août 2016 15:38:17 UTC+2, Simon Brandhorst a écrit :
>
> {{{
> sage: q=FreeQuadraticModule(ZZ,2,inner_product_matrix=1)
> sage: q
> Ambient free quadratic module of rank 2 over the principal ideal domain 
> Integer Ring
> Inner product matrix:
> [1 0]
> [0 1]
> sage: q.determinant()
> 1
> sage: q.discriminant()
> -2
> }}}
>
>
> This output is wrong. The discriminant should be -1. 
>
> The following is another related bug. I guess thats where the error of the 
> first bug lies as well.
>
>
> {{{
> sage: q=FreeQuadraticModule(QQ,2,inner_product_matrix=1)
> sage: q.determinant()
> 1
> sage: q.discriminant()
> ---
> RuntimeError  Traceback (most recent call last)
>  in ()
> > 1 q.discriminant()
>
> /usr/lib/sagemath/local/lib/python2.7/site-packages/sage/modules/free_quadratic_module.pyc
>  
> in discriminant(self)
> 377 else:
> 378 r = (n-1)//2
> --> 379 return (-1)^r*self.gram_matrix().determinant()
> 380 
> 381 def gram_matrix(self):
>
> sage/structure/element.pyx in sage.structure.element.Element.__xor__ 
> (/usr/lib/sagemath//src/build/cythonized/sage/structure/element.c:8229)()
>
> RuntimeError: Use ** for exponentiation, not '^', which means xor
> in Python, and has the wrong precedence.
> }}}
>
> This occurred on two different machines running sage 7.0 and 7.2 on Ubuntu 
> 14.04.4 LTS and Fedora 24
> (both x64).
>
> Sorry if this is not following some conventions ... it is my first bug 
> report. 
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] disallow mixing of pos.char.ring elements and symbolic variables

[Vincent Delecroix]

On 31/08/16 02:36, Ralf Stephan wrote:

On Tuesday, August 30, 2016 at 5:45:16 PM UTC+2, vdelecroix wrote:


sage: x = SR.variable(domain = GF(3))
sage: n = SR.variable(domain = ZZ)



This is good design(TM). The usage however duplicates
Sage's polynomial rings,so why burden calculus with that?


Because the symbolic expression "x^n" is  *not* a polynomial! Moreover, 
with finite fields, polynomial function is different from polynomial. 
Namely, x^3 = x  for any x in GF(3) but these are not equal as polynomials.


Vincent

--
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Bug in FreeQuadraticModule.discriminant()

[John Cremona]

Indeed, that is a bug in line 371 of the file sage/
modules/free_quadratic_module.py -- an easy fix.

Perhaps someone ought to look through all occurrences of ^ in .py files
outside of docstrings (where they are OK thanks to preparsing).

John

On 31 August 2016 at 13:44, Simon Brandhorst  wrote:

>
> {
> sage: q=FreeQuadraticModule(ZZ,2,inner_product_matrix=1)
> sage: q
> Ambient free quadratic module of rank 2 over the principal ideal domain
> Integer Ring
> Inner product matrix:
> [1 0]
> [0 1]
> sage: q.determinant()
> 1
> sage: q.discriminant()
> -2
> }
> #The expected value here is -1
>
> The following example should clarity what is wrong.
> {
> sage: q=FreeQuadraticModule(QQ,2,inner_product_matrix=1)
> sage: q.determinant()
> 1
> sage: q.discriminant()
> 
> ---
> RuntimeError  Traceback (most recent call
> last)
>  in ()
> > 1 q.discriminant()
>
> /usr/lib/sagemath/local/lib/python2.7/site-packages/sage/
> modules/free_quadratic_module.pyc in discriminant(self)
> 377 else:
> 378 r = (n-1)//2
> --> 379 return (-1)^r*self.gram_matrix().determinant()
> 380
> 381 def gram_matrix(self):
>
> sage/structure/element.pyx in sage.structure.element.Element.__xor__
> (/usr/lib/sagemath//src/build/cythonized/sage/structure/element.c:8229)()
>
> RuntimeError: Use ** for exponentiation, not '^', which means xor
> in Python, and has the wrong precedence.
> }
>
> This happened with sage 7.0 and 7.2 on two different machines.
> (Ubuntu 14.04.4 LTS, and fedora 24)
>
> --
> 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 post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Sage Days 82, Women in Sage

[Viviane Pons]

Dear all,

the first ever workshop for women in Sage in Europe (the previous ones were
in the US) will be organized January 9 - 13, 2017 by Jessica Striker,
Jennifer Balakrishnan, and myself.

We will rent a house in Paris area and organize coding sprints, tutorials,
and presentations.

All Sage levels are welcome: from novice to expert.

All informations are here: https://wiki.sagemath.org/days82

Applications are due October 31. **Food and lodging are provided by the
conference**

Please share this among your departments and students.

Best

Viviane

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-combinat-devel] Sage Days 82, Women in Sage

[Viviane Pons]

Dear all,

the first ever workshop for women in Sage in Europe (the previous ones were
in the US) will be organized January 9 - 13, 2017 by Jessica Striker,
Jennifer Balakrishnan, and myself.

We will rent a house in Paris area and organize coding sprints, tutorials,
and presentations.

All Sage levels are welcome: from novice to expert.

All informations are here: https://wiki.sagemath.org/days82

Applications are due October 31. **Food and lodging are provided by the
conference**

Please share this among your departments and students.

Best

Viviane

-- 
You received this message because you are subscribed to the Google Groups 
"sage-combinat-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-combinat-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-combinat-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-combinat-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Bug in FreeQuadraticModule.discriminant

[Simon Brandhorst]

{{{
sage: q=FreeQuadraticModule(ZZ,2,inner_product_matrix=1)
sage: q
Ambient free quadratic module of rank 2 over the principal ideal domain 
Integer Ring
Inner product matrix:
[1 0]
[0 1]
sage: q.determinant()
1
sage: q.discriminant()
-2
}}}


This output is wrong. The discriminant should be -1. 

The following is another related bug. I guess thats where the error of the 
first bug lies as well.


{{{
sage: q=FreeQuadraticModule(QQ,2,inner_product_matrix=1)
sage: q.determinant()
1
sage: q.discriminant()
---
RuntimeError  Traceback (most recent call last)
 in ()
> 1 q.discriminant()

/usr/lib/sagemath/local/lib/python2.7/site-packages/sage/modules/free_quadratic_module.pyc
 
in discriminant(self)
377 else:
378 r = (n-1)//2
--> 379 return (-1)^r*self.gram_matrix().determinant()
380 
381 def gram_matrix(self):

sage/structure/element.pyx in sage.structure.element.Element.__xor__ 
(/usr/lib/sagemath//src/build/cythonized/sage/structure/element.c:8229)()

RuntimeError: Use ** for exponentiation, not '^', which means xor
in Python, and has the wrong precedence.
}}}

This occurred on two different machines running sage 7.0 and 7.2 on Ubuntu 
14.04.4 LTS and Fedora 24
(both x64).

Sorry if this is not following some conventions ... it is my first bug 
report. 

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Bug in FreeQuadraticModule.discriminant()

[Simon Brandhorst]

{
sage: q=FreeQuadraticModule(ZZ,2,inner_product_matrix=1)
sage: q
Ambient free quadratic module of rank 2 over the principal ideal domain 
Integer Ring
Inner product matrix:
[1 0]
[0 1]
sage: q.determinant()
1
sage: q.discriminant()
-2
}
#The expected value here is -1

The following example should clarity what is wrong. 
{
sage: q=FreeQuadraticModule(QQ,2,inner_product_matrix=1)
sage: q.determinant()
1
sage: q.discriminant()
---
RuntimeError  Traceback (most recent call last)
 in ()
> 1 q.discriminant()

/usr/lib/sagemath/local/lib/python2.7/site-packages/sage/modules/free_quadratic_module.pyc
 
in discriminant(self)
377 else:
378 r = (n-1)//2
--> 379 return (-1)^r*self.gram_matrix().determinant()
380 
381 def gram_matrix(self):

sage/structure/element.pyx in sage.structure.element.Element.__xor__ 
(/usr/lib/sagemath//src/build/cythonized/sage/structure/element.c:8229)()

RuntimeError: Use ** for exponentiation, not '^', which means xor
in Python, and has the wrong precedence.
}

This happened with sage 7.0 and 7.2 on two different machines. 
(Ubuntu 14.04.4 LTS, and fedora 24)

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Should we close all tickets with milestone "sage-duplicate/invalid/wontfix"?

[leif]

leif wrote:
> Erik Bray wrote:
>> On Tue, Aug 30, 2016 at 10:12 PM, Jeroen Demeyer  
>> wrote:
>>> On 2016-08-30 19:44, leif wrote:

 Anyway, our current policy is that *only* the release manager is allowed
 to close tickets, so I wouldn't do without first asking.
>>>
>>>
>>> I have the "power" to close tickets, but I don't do that because of this
>>> reason. The only exceptions are tickets which are obviously mistakes or
>>> spam.
>>
>> I think it' should be fine to close tickets so long as it's already
>> been signed off on as close-able in some sense or another.
> 
> Well, we once had release notes...
> 
>  where also tickets closed (but not merged) within the current
> release cycle were listed.
> 
> Since duplicate/invalid/wontfix is a *milestone* (!), it's not easy to
> recover these when they've already been closed.  In fact, also
> duplicates were closed /after/ the other ticket(s) fixing an issue had
> been merged and released.

P.S.:  I of course meant "duplicates" in the sense of being superseded
by another ticket, not such reporting exactly the same issue.  Still,
also positively reviewed /true/ duplicates were closed by the release
manager, after releasing the next "stable" release.


-leif


-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Should we close all tickets with milestone "sage-duplicate/invalid/wontfix"?

[leif]

Erik Bray wrote:
> On Tue, Aug 30, 2016 at 10:12 PM, Jeroen Demeyer  
> wrote:
>> On 2016-08-30 19:44, leif wrote:
>>>
>>> Anyway, our current policy is that *only* the release manager is allowed
>>> to close tickets, so I wouldn't do without first asking.
>>
>>
>> I have the "power" to close tickets, but I don't do that because of this
>> reason. The only exceptions are tickets which are obviously mistakes or
>> spam.
> 
> I think it' should be fine to close tickets so long as it's already
> been signed off on as close-able in some sense or another.

Well, we once had release notes...

... where also tickets closed (but not merged) within the current
release cycle were listed.

Since duplicate/invalid/wontfix is a *milestone* (!), it's not easy to
recover these when they've already been closed.  In fact, also
duplicates were closed /after/ the other ticket(s) fixing an issue had
been merged and released.


-leif


-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] increasing verbose level for sub-routines

[David Loeffler]

I'm surprised at the apparent consensus that the only solution is to
re-implement "verbose" by some totally different method. I came across this
issue before and I found a perfectly acceptable fix, which I didn't bother
to make a ticket for because I didn't know if anyone else cared about this
issue until I saw this thread.

The current implementation of "verbose" controls which messages to show
according to the name of the Python module containing the code; and it
extracts the module name from the Python interpreter state. Unfortunately,
this doesn't play well with Cython modules, so if verbose is called from
Cython code, it ends up going back up the call stack until it finds a
Python module. Because Sage's matrix algebra routines have lots of
diagnostic messages built in (definitely a Good Thing), and they are almost
all implemented in Cython, this often leads to a slew of unwanted messages
about matrix arithmetic, as in Daniel's example.

The solution I found was simply to add an optional extra argument to
"verbose", specifying a string to use in place of the auto-detected module
name (extending a mechanism that's already there for the function name);
and then to grep through the Cython files in the Sage library, adjusting a
few dozen calls to "verbose" to give the module name explicitly each time.
This worked perfectly.

I'd be happy to make a ticket for this, if others agree that it's
preferable to reinventing the wheel.

David

On 26 August 2016 at 18:27, Daniel Krenn  wrote:

> On 2016-08-09 19:31, William Stein wrote:
> > The only good way is to rip out the "verbose" thing and replace it
> > with the Python logging module. Then its easy to have different
> > loggers for your code and for the flint interface, and make them log
> > in different levels and/or different output streams.
> >
> > You don't have rip out verbose and replace it.  Just switch to using
> > the built in Python logging module for what you're doing.   We should
> > also reimplement verbose on top of pythons built in logging module
> > (probably just a few lines of code to do that).  I'm very surprised
> > nobody has done this already.
>
> I've started this at
>   https://trac.sagemath.org/ticket/21349
>
> Daniel
>
> --
> 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 post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: missing emails from trac

[leif]

Erik Bray wrote:
> On Wed, Aug 31, 2016 at 1:02 AM, leif  wrote:
>> leif wrote:
>>> Dima Pasechnik wrote:

 On Tuesday, August 30, 2016 at 5:20:37 PM UTC, leif wrote:

 FWIW, I now have *significant* delay in (apparently) *all*
 notifications
 from trac, even between those for the same ticket where the comments
 were made within a few minutes.


 please post (or email me)  headers in an example of your message.
>>>
>>> Thanks, but that was probably exceptional.  (I noticed receiving
>>> notifications for three consecutive comments with a delay of about 30,
>>> 60, and 90 minutes, while they were made within 13 minutes.)
>>>
>>> I now received some further notifications (from different tickets and
>>> not by me) "in time", so I'll wait and see how it behaves the next days.
>>
>> P.S.:  Looking at the headers, the delay happened *within* sendgrid, so
>> there's presumably nothing we can (or have to) do, other than perhaps
>> changing the provider in case the situation worsens.
> 
> I wonder if it has to do with the destination too though (albeit not
> entirely either, since as you wrote it used to work fine for you).
> Some combination of sendgrid and the destination then.

I'd rather guess it depends (besides sysload and traffic of course) on
the /content/ of the messages, I have no idea what
filterfoo*.sendgrid.net does though.  (The delayed trac messages seemed
harmless, didn't even contain links other than those added by trac IIRC.)


-leif


-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: missing emails from trac

[Erik Bray]

On Wed, Aug 31, 2016 at 1:02 AM, leif  wrote:
> leif wrote:
>> Dima Pasechnik wrote:
>>>
>>> On Tuesday, August 30, 2016 at 5:20:37 PM UTC, leif wrote:
>>>
>>> FWIW, I now have *significant* delay in (apparently) *all*
>>> notifications
>>> from trac, even between those for the same ticket where the comments
>>> were made within a few minutes.
>>>
>>>
>>> please post (or email me)  headers in an example of your message.
>>
>> Thanks, but that was probably exceptional.  (I noticed receiving
>> notifications for three consecutive comments with a delay of about 30,
>> 60, and 90 minutes, while they were made within 13 minutes.)
>>
>> I now received some further notifications (from different tickets and
>> not by me) "in time", so I'll wait and see how it behaves the next days.
>
> P.S.:  Looking at the headers, the delay happened *within* sendgrid, so
> there's presumably nothing we can (or have to) do, other than perhaps
> changing the provider in case the situation worsens.

I wonder if it has to do with the destination too though (albeit not
entirely either, since as you wrote it used to work fine for you).
Some combination of sendgrid and the destination then.

Trac e-mails arrive in my gmail, as you said, sometimes before the web
page is even done reloading.  Haven't had a single problem.

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Should we close all tickets with milestone "sage-duplicate/invalid/wontfix"?

[Erik Bray]

On Tue, Aug 30, 2016 at 10:12 PM, Jeroen Demeyer  wrote:
> On 2016-08-30 19:44, leif wrote:
>>
>> Anyway, our current policy is that *only* the release manager is allowed
>> to close tickets, so I wouldn't do without first asking.
>
>
> I have the "power" to close tickets, but I don't do that because of this
> reason. The only exceptions are tickets which are obviously mistakes or
> spam.

I think it' should be fine to close tickets so long as it's already
been signed off on as close-able in some sense or another.

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: [Yet again] Sage's R vs system's R

[Emmanuel Charpentier]

Le mardi 30 août 2016 19:33:20 UTC+2, leif a écrit :


> > Making R optional *will* break existing code. 
>
> How do you come to that conclusion? 
>

To be precise : any code relying on R being standard and using it without 
bothering checking this assumption.
I have such code myself (e. g. a couple of pedagogic notebooks confronting 
explicit symbolic integration + function evaluation, numerical integration 
and Monte-Carlo integration, which uses R for the latter).

>
> Making R optional just means people using R (or the interface to it) 
> would have to "manually" (=explicitly) install it then (or in the 
> future, perhaps have to configure Sage '--with-R' or something like that). 
>

(Wouldn't that be "sage -i R" ? ) Indeed. Yet another chore during Sge 
maintainance easily avoided with standard R binary, partially avoided 
with a standard R interface.

HTH,

--
Emmanuel Charpentier

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Patchbot tmonteil-debian-jessie-32 has "No space left on device"

[Thierry]

Hi,

i noticed that one hour ago after Frederic told me there was an issue, i
relaunched the patchbot after some cleanup.

Thanks for the reporting anyway !

Ciao,
Thierry



On Wed, Aug 31, 2016 at 10:57:17AM +0200, Jeroen Demeyer wrote:
> The patchbot tmonteil-debian-jessie-32 is spamming all tickets as
> BuildFailed because of "No space left on device".
> 
> See for example 
> https://patchbot.sagemath.org/log/21126/debian/8.3/i686/3.16.0-4-586/tmonteil-debian-jessie-32/2016-08-31%2001:20:27?short
> 
> -- 
> 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 post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: missing emails from trac

[Jeroen Demeyer]

On 2016-08-30 23:10, Dima Pasechnik wrote:

please post (or email me)  headers in an example of your message.


Here is a worse example, a delay of 2 hours and 40 minutes:

Received: from o1.30nn.fshared.sendgrid.net 
(o1.30nn.fshared.sendgrid.net [167.89.55.59])

(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by relay1.ugent.be (Postfix) with ESMTPS id 54E4A7611A
for ; Tue, 30 Aug 2016 22:37:50 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sagemath.org;

h=content-type:mime-version:from:to:references:in-reply-to:reply-to:subject;
s=s1; bh=HorxxI+aXXry/S10wecA/ST/B74=; b=CghOnDsuepxY5oOQVM+koq3
oG5CXKC9S5F/yOvrhw2I4KDj5fVpvm6zK61roebS+TbZzrSkS4jmbo3Ppt92BbqJ
Ae4RxXD2r8RyfVcp4rgloqr/n6qnbRiwEIDPiUyAeL5QjEJ/QESOtxlFLeMaJBLI
IdtSyVjkI/V4o2mpMBYo=
Received: by filter0588p1mdw1.sendgrid.net with SMTP id 
filter0588p1mdw1.4751.57C5C919C

2016-08-30 17:57:45.109316281 + UTC

--
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: missing emails from trac

[Jeroen Demeyer]

On 2016-08-30 23:10, Dima Pasechnik wrote:

please post (or email me)  headers in an example of your message.


Just an example of one notification with a small delay. Here you see a 
delay of 6 minutes (note the different timezone, CEST==UTC+2).


[...]
Received: from o1.30nn.fshared.sendgrid.net 
(o1.30nn.fshared.sendgrid.net [167.89.55.59])

(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by relay2.ugent.be (Postfix) with ESMTPS id 2A4EE10639F
for ; Wed, 31 Aug 2016 10:58:08 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sagemath.org;

h=mime-version:content-type:content-transfer-encoding:from:subject:reply-to:references:in-reply-to;
s=s1; bh=WgW01/o6RpUgLjOnF9KFcynAqVQ=; b=t7Hhf1rBqiC8PAogtFBj4cl
SAzB3cYJRlG6lCxh3X5E8Xh9fH9QtrH0RzJ8Ixqizc+KVSUs+adCCebVfzAE7AEa
qcVkD4wvTUf4pLQ6NQNxBZm7qitj5QxMfoyGMaOxdD6JedXi8CUQQbQvQMCmbo0R
yHjw88XaXD2rjHVX3zGw=
Received: by filter0218p1las1.sendgrid.net with SMTP id 
filter0218p1las1.9128.57C69AB924

2016-08-31 08:52:09.465745637 + UTC
[...]

--
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Patchbot tmonteil-debian-jessie-32 has "No space left on device"

[Jeroen Demeyer]

The patchbot tmonteil-debian-jessie-32 is spamming all tickets as 
BuildFailed because of "No space left on device".


See for example 
https://patchbot.sagemath.org/log/21126/debian/8.3/i686/3.16.0-4-586/tmonteil-debian-jessie-32/2016-08-31%2001:20:27?short


--
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.