Re: [sage-devel] Names of objects in sage

[Nils Bruin]

On Tuesday, July 10, 2018 at 2:39:35 AM UTC-7, Johan S. H. Rosenkilde wrote:
>
> but now use the standard nomenclature for coding theory with a short 
> field description: 
>
> sage: C = codes.random_linear_code(GF(25), 10, 3); C 
> [10, 3] linear code over GF(25) 
>
> My first reaction is to quote a stylistic rule: "Don't start sentences 
with a formula".  That rule exists to avoid  formulas running into each 
other (and to allow normal grammatical markers to help recognize the start 
and end of sentences). With this, for instance, you would have

sage: [C, C]
[[10, 3] linear code over GF(25), [10, 3] linear code over GF(25)] 

which can make people wonder what GF(25), [10, 3] signifies (when you end 
up with punctuation separating formulas, it's easy to read the punctuation 
as part of the formula). For that reason I would probably format it as

Linear code [10,3] over GF(25)

instead. In the examples you give the composition with other constructions 
turns out rather fortunate, but I would not trust that this would always be 
the case.

-- 
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: NTL 11.2.0

['Bill Hart' via sage-devel]

Hi Victor,

Thanks. That makes sense now. I was reading your diagram upside down! 
Indeed, on your diagram we use SSA below the diagonal.

The multimodular algorithm was not faster than Kronecker substitution for 
us. But I think that was simply because we don't have a small primes FFT, 
or something like that. I remember we discussed this once before.

Bill.

On Tuesday, 10 July 2018 14:09:05 UTC+2, Victor Shoup wrote:
>
> Bill,
>
> Above the diagonal, I believe Flint is using a Kronecker substitution 
> algorithm, while NTL is using a multi-modular FFT.  NTL always outperformed 
> Flint in this region. It is the region below the diagonal where both are 
> using Schoenhage-Strassen, and there you can see that NTL still lags behind 
> Flint somewhat, though not as much as it used to.
>
> The benchmark programs are available on the NTL web site, and I encourage 
> anyone who wants to run similar benchmarks on a different platform to do 
> so, and to verify that the benchmark software is fair.
>
> -Victor
>
> On Monday, July 9, 2018 at 8:33:12 AM UTC-4, Bill Hart wrote:
>>
>> These are ery interesting timings. In the region above the diagonal (and 
>> sufficiently far to the right - degree 12 I think), I believe we still use 
>> the SSA algorithm directly for polynomial arithmetic over Z. So your 
>> timings indicate that you are actually beating the Flint FFT directly.
>>
>> This is quite remarkable given the work that went into it on in Flint (it 
>> was already significantly faster than the FFT's in Magma and GMP, and 
>> faster than the Gaudry, Kruppa, Zimmermann FFT.
>>
>> I congratulate you on what must be some truly impressive work. (I keep 
>> telling whoever will listen that we should spend some time trying to catch 
>> back up with the NTL benchmarks you have been publishing, but there seems 
>> to be little opportunity to work on such projects these days, and there 
>> seems to be a real shortage of young people taking on challenges like this. 
>> We do know what needs to be done. It's more an issue of finding people who 
>> could actually carry out the work.)
>>
>> Anyway, thanks again for the impressive work you've been doing on NTL, 
>> for making your code Open Source, so that we can all learn from it, and for 
>> the benchmarks you have been making available!
>>
>> Bill.
>>
>> On Saturday, 7 July 2018 20:39:59 UTC+2, Victor Shoup wrote:
>>>
>>> I just released NTL 11.2.0 at http://www.shoup.net/ntl
>>>
>>> The main change is a new and improved implementation of the 
>>> Schoenhage-Strassen FFT for multiplication of polynomials over the 
>>> integers. The new implementation includes a truncated FFT algorithm, the 
>>> "sqrt 2" trick, and better engineered low-level "butterfly" code.  See 
>>> http://www.shoup.net/ntl/doc/tour-changes.html for details, including 
>>> some benchmarks.
>>>
>>> Also see http://www.shoup.net/ntl/benchmarks.pdf for an updated version 
>>> of NTL vs FLINT 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: Cysignals release / upgrade for Sage 8.3

[Erik Bray]

On Tue, Jul 10, 2018 at 3:46 PM Jeroen Demeyer  wrote:
>
> Should be easy, I'll do that.
>
> I already created the Sage ticket: https://trac.sagemath.org/ticket/25814

Thanks!

-- 
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: Cysignals release / upgrade for Sage 8.3

[Jeroen Demeyer]

Should be easy, I'll do that.

I already created the Sage ticket: https://trac.sagemath.org/ticket/25814

--
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] Cysignals release / upgrade for Sage 8.3

[Erik Bray]

Hello,

There are a couple minor fixes in Cysignals since its last release
that pertain to Cygwin.  It be nice if, in time for the Sage 8.3
release, we could get a new release of Cysignals (e.g. 1.7.2) which
includes those fixes, and bump the version in Sage to that.

I'd be happy to do the release myself but I don't know if there's some
particular process for it.

Thanks,
E

-- 
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: Sage fails to build on Arch linux, possible recurrence of an old bug

[עמית וולצקי]

Gotcha. Many thanks.

2018-07-10 15:34 GMT+03:00 Antonio Rojas :

>
>
> El martes, 10 de julio de 2018, 14:21:03 (UTC+2), Amit Wolecki escribió:
>>
>> I see, thanks Antonio for the fix! To make sure I get the big picture -
>> distro package will use system services (e.g. python and especially pip)
>> whereas the built from source installation has it's own compiled python env
>> and is thus independent of the system installed python env. Do I get that
>> right?
>>
>>
> Yes, mostly right. Just note that sage uses a custom PYTHONUSERBASE, so
> packages installed with 'sage -pip --user' will only be available in sage
> and not in the system python. If you want a package to work both in sage
> and in regular python you should use 'pip2 install --user' directly
> instead.
>
-- 
You received this message because you are subscribed to a topic in the
Google Groups "sage-devel" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/sage-devel/ScwAA8qGYKw/unsubscribe.
To unsubscribe from this group and all its topics, 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: Sage fails to build on Arch linux, possible recurrence of an old bug

[Antonio Rojas]

El martes, 10 de julio de 2018, 14:21:03 (UTC+2), Amit Wolecki escribió:
>
> I see, thanks Antonio for the fix! To make sure I get the big picture - 
> distro package will use system services (e.g. python and especially pip) 
> whereas the built from source installation has it's own compiled python env 
> and is thus independent of the system installed python env. Do I get that 
> right?
>
>
Yes, mostly right. Just note that sage uses a custom PYTHONUSERBASE, so 
packages installed with 'sage -pip --user' will only be available in sage 
and not in the system python. If you want a package to work both in sage 
and in regular python you should use 'pip2 install --user' directly 
instead. 

-- 
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: Sage fails to build on Arch linux, possible recurrence of an old bug

[עמית וולצקי]

I see, thanks Antonio for the fix! To make sure I get the big picture -
distro package will use system services (e.g. python and especially pip)
whereas the built from source installation has it's own compiled python env
and is thus independent of the system installed python env. Do I get that
right?

2018-07-10 13:52 GMT+03:00 Antonio Rojas :

>
>
> El lunes, 9 de julio de 2018, 21:35:04 (UTC+2), Amit Wolecki escribió:
>>
>> Thank you all for the useful comments!
>> Antonio, I wasn't aware of the somewhat limiting way a repo installation
>> works, this remark made me try to stick to building from source.
>>
>>>
>>>
> Actually, scratch that. 'sage -i' will definitely not work as it's tightly
> tied to the upstream Sage directory structure. However, 'sage -pip' should
> simply work by calling the system pip. The reason why it didn't work is
> that our python2 pip command is renamed to pip2 so it doesn't conflict with
> the python3 version. I've now fixed that in 8.2-10 and 'sage -pip' works
> properly with the distro package.
>  Note that you should always call it with --user, installing system wide
> packages with pip on Arch is highly discouraged
>
-- 
You received this message because you are subscribed to a topic in the
Google Groups "sage-devel" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/sage-devel/ScwAA8qGYKw/unsubscribe.
To unsubscribe from this group and all its topics, 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: NTL 11.2.0

[Victor Shoup]

Bill,

Above the diagonal, I believe Flint is using a Kronecker substitution 
algorithm, while NTL is using a multi-modular FFT.  NTL always outperformed 
Flint in this region. It is the region below the diagonal where both are 
using Schoenhage-Strassen, and there you can see that NTL still lags behind 
Flint somewhat, though not as much as it used to.

The benchmark programs are available on the NTL web site, and I encourage 
anyone who wants to run similar benchmarks on a different platform to do 
so, and to verify that the benchmark software is fair.

-Victor

On Monday, July 9, 2018 at 8:33:12 AM UTC-4, Bill Hart wrote:
>
> These are ery interesting timings. In the region above the diagonal (and 
> sufficiently far to the right - degree 12 I think), I believe we still use 
> the SSA algorithm directly for polynomial arithmetic over Z. So your 
> timings indicate that you are actually beating the Flint FFT directly.
>
> This is quite remarkable given the work that went into it on in Flint (it 
> was already significantly faster than the FFT's in Magma and GMP, and 
> faster than the Gaudry, Kruppa, Zimmermann FFT.
>
> I congratulate you on what must be some truly impressive work. (I keep 
> telling whoever will listen that we should spend some time trying to catch 
> back up with the NTL benchmarks you have been publishing, but there seems 
> to be little opportunity to work on such projects these days, and there 
> seems to be a real shortage of young people taking on challenges like this. 
> We do know what needs to be done. It's more an issue of finding people who 
> could actually carry out the work.)
>
> Anyway, thanks again for the impressive work you've been doing on NTL, for 
> making your code Open Source, so that we can all learn from it, and for the 
> benchmarks you have been making available!
>
> Bill.
>
> On Saturday, 7 July 2018 20:39:59 UTC+2, Victor Shoup wrote:
>>
>> I just released NTL 11.2.0 at http://www.shoup.net/ntl
>>
>> The main change is a new and improved implementation of the 
>> Schoenhage-Strassen FFT for multiplication of polynomials over the 
>> integers. The new implementation includes a truncated FFT algorithm, the 
>> "sqrt 2" trick, and better engineered low-level "butterfly" code.  See 
>> http://www.shoup.net/ntl/doc/tour-changes.html for details, including 
>> some benchmarks.
>>
>> Also see http://www.shoup.net/ntl/benchmarks.pdf for an updated version 
>> of NTL vs FLINT 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] unable to compile sage-8.2

[kenichi fujisaki]

Ok, for the time being i did:
make -k



2018-07-10 12:25 GMT+02:00 kenichi fujisaki :

> it was posted by Samuel Lelievre on the 8th of July
>
> 2018-07-10 12:22 GMT+02:00 kenichi fujisaki :
>
>> Ah i see,
>> My apologies, Mr. Lelievre.
>> Let me clarify the situation, *I followed your suggestion about
>> cysignals trouble*
>>
>> 2018-07-10 11:38 GMT+02:00 kenichi fujisaki :
>>
>>> To get a recent enough version of curl, one way is to run
>>>
>>> sage -i curl
>>>
>>> Is not working
>>>
>>>
>>> >how can that "work fine even with macOS 10.6.8"? No worries.
>>> i've downloaded the curl source
>>> then
>>> cd curl-folder
>>> ./configure
>>> make
>>>
>>> finally, i got a brand new curl7.6
>>>
>>>
>>>
>>>
>>> 2018-07-10 11:19 GMT+02:00 Samuel Lelievre :
>>>


 Tue 2018-07-10 01:46:56 UTC, kenichi fujisaki:
 > I followed the method of Mr. Pasechnik.
 > (I had to get (compile) the newest version of cUrl.)
 > And it works fine even with macos10.6.8.
 > Thank you very much.

 Dima Pasechnik suggested to upgrade to macOS 10.13,
 how can that "work fine even with macOS 10.6.8"?   : )

 To get a recent enough version of curl, one way is to run

 sage -i curl

 > Now I'm fighting againt the package R [r-3.4.3.p0]:
 > How to fix this problem?

 You could install R separately and use this ticket:

 - Sage Trac ticket 25503:
   Allow the use of system's R installation
   https://trac.sagemath.org/ticket/25503

 Or if you don't need R at all you could tweak things
 to bypass the installation of R and rpy2.

 --
 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: Sage fails to build on Arch linux, possible recurrence of an old bug

[Antonio Rojas]

El lunes, 9 de julio de 2018, 21:35:04 (UTC+2), Amit Wolecki escribió:
>
> Thank you all for the useful comments!
> Antonio, I wasn't aware of the somewhat limiting way a repo installation 
> works, this remark made me try to stick to building from source.
>
>>
>>
Actually, scratch that. 'sage -i' will definitely not work as it's tightly 
tied to the upstream Sage directory structure. However, 'sage -pip' should 
simply work by calling the system pip. The reason why it didn't work is 
that our python2 pip command is renamed to pip2 so it doesn't conflict with 
the python3 version. I've now fixed that in 8.2-10 and 'sage -pip' works 
properly with the distro package.
 Note that you should always call it with --user, installing system wide 
packages with pip on Arch is highly discouraged

-- 
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] How parallel should @parallel be?

[Erik Bray]

On Tue, Jul 10, 2018 at 12:43 PM Jeroen Demeyer  wrote:
>
> On 2018-07-10 12:37, Erik Bray wrote:
> > If I want to limit
> > parallelization on a machine that I'm concurrently using for other
> > work, that's kind of a decision a human has to make.
>
> One could argue the other way around: if I want Sage to use all
> resources on the machine that it's running on, that's kind of a decision
> a human has to make. In other words: guessing is hard.
>
> The default of 1 was certainly meant as feature: the idea being that
> parallellism is something that should be enabled explicitly. A bit like
> GNU make, which uses a single process by default but optionally supports
> multi-processing.

I think this is good argument, but it's also a bit of a problem in
that @parallel is supposed to be kind of "out-of-the-box"
parallelization, and if its default is not provide any parallelization
I envision users saying "I put @parallel on my code and it didn't run
any faster" (if anything it's slower).  So I don't think 1 is a good
low-end default for that alone.  Maybe instead min(2, os.cpu_count())
if you're going to argue from that end.

-- 
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] How parallel should @parallel be?

[Jeroen Demeyer]

On 2018-07-10 12:37, Erik Bray wrote:

If I want to limit
parallelization on a machine that I'm concurrently using for other
work, that's kind of a decision a human has to make.


One could argue the other way around: if I want Sage to use all 
resources on the machine that it's running on, that's kind of a decision 
a human has to make. In other words: guessing is hard.


The default of 1 was certainly meant as feature: the idea being that 
parallellism is something that should be enabled explicitly. A bit like 
GNU make, which uses a single process by default but optionally supports 
multi-processing.



Jeroen.

--
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] How parallel should @parallel be?

[Erik Bray]

On Mon, Jul 9, 2018 at 6:35 PM Julian Rüth  wrote:
>
> Hello.
>
> since Sage 8.2 sage.parallel.ncpus.ncpus() returns 1 if you have no 
> environment variables such as MAKE, SAGE_NUM_THREADS, MAKEOPTS set.
>
> This number is used by the @parallel decorator and similar constructions to 
> determine the number of processes to run in parallel. (Unless during 
> doctests, then it's set to 2 I think.)
>
> The question is: What is a good default for things such as @parallel when 
> SAGE_NUM_THREADS has not been set? I think that 1 is not a good one. The 
> actual number of cores/threads on a system probably isn't either on servers 
> with lots of cores. At some point we had `min(8, number of threads)` which 
> appears reasonable to me.
>
> Please join the discussion at https://trac.sagemath.org/ticket/24937 :)

For the sake of reference, the standard library's
`multiprocessing.Pool` [1] just uses `os.cpu_count()` by default, and
I don't really see a problem with that.  If I want to limit
parallelization on a machine that I'm concurrently using for other
work, that's kind of a decision a human has to make.  If I have 32
cores why would I want it limited to 8, by default, for example?

(No, most people's personal machines won't have 32 cores, though
that's not going to be so uncommon forever...)

[1] 
https://docs.python.org/3.7/library/multiprocessing.html?highlight=process#multiprocessing.pool.Pool

-- 
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] unable to compile sage-8.2

[kenichi fujisaki]

it was posted by Samuel Lelievre on the 8th of July

2018-07-10 12:22 GMT+02:00 kenichi fujisaki :

> Ah i see,
> My apologies, Mr. Lelievre.
> Let me clarify the situation, *I followed your suggestion about cysignals
> trouble*
>
> 2018-07-10 11:38 GMT+02:00 kenichi fujisaki :
>
>> To get a recent enough version of curl, one way is to run
>>
>> sage -i curl
>>
>> Is not working
>>
>>
>> >how can that "work fine even with macOS 10.6.8"? No worries.
>> i've downloaded the curl source
>> then
>> cd curl-folder
>> ./configure
>> make
>>
>> finally, i got a brand new curl7.6
>>
>>
>>
>>
>> 2018-07-10 11:19 GMT+02:00 Samuel Lelievre :
>>
>>>
>>>
>>> Tue 2018-07-10 01:46:56 UTC, kenichi fujisaki:
>>> > I followed the method of Mr. Pasechnik.
>>> > (I had to get (compile) the newest version of cUrl.)
>>> > And it works fine even with macos10.6.8.
>>> > Thank you very much.
>>>
>>> Dima Pasechnik suggested to upgrade to macOS 10.13,
>>> how can that "work fine even with macOS 10.6.8"?   : )
>>>
>>> To get a recent enough version of curl, one way is to run
>>>
>>> sage -i curl
>>>
>>> > Now I'm fighting againt the package R [r-3.4.3.p0]:
>>> > How to fix this problem?
>>>
>>> You could install R separately and use this ticket:
>>>
>>> - Sage Trac ticket 25503:
>>>   Allow the use of system's R installation
>>>   https://trac.sagemath.org/ticket/25503
>>>
>>> Or if you don't need R at all you could tweak things
>>> to bypass the installation of R and rpy2.
>>>
>>> --
>>> 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] unable to compile sage-8.2

[kenichi fujisaki]

Ah i see,
My apologies, Mr. Lelievre.
Let me clarify the situation, *I followed your suggestion about cysignals
trouble*

2018-07-10 11:38 GMT+02:00 kenichi fujisaki :

> To get a recent enough version of curl, one way is to run
>
> sage -i curl
>
> Is not working
>
>
> >how can that "work fine even with macOS 10.6.8"? No worries.
> i've downloaded the curl source
> then
> cd curl-folder
> ./configure
> make
>
> finally, i got a brand new curl7.6
>
>
>
>
> 2018-07-10 11:19 GMT+02:00 Samuel Lelievre :
>
>>
>>
>> Tue 2018-07-10 01:46:56 UTC, kenichi fujisaki:
>> > I followed the method of Mr. Pasechnik.
>> > (I had to get (compile) the newest version of cUrl.)
>> > And it works fine even with macos10.6.8.
>> > Thank you very much.
>>
>> Dima Pasechnik suggested to upgrade to macOS 10.13,
>> how can that "work fine even with macOS 10.6.8"?   : )
>>
>> To get a recent enough version of curl, one way is to run
>>
>> sage -i curl
>>
>> > Now I'm fighting againt the package R [r-3.4.3.p0]:
>> > How to fix this problem?
>>
>> You could install R separately and use this ticket:
>>
>> - Sage Trac ticket 25503:
>>   Allow the use of system's R installation
>>   https://trac.sagemath.org/ticket/25503
>>
>> Or if you don't need R at all you could tweak things
>> to bypass the installation of R and rpy2.
>>
>> --
>> 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] unable to compile sage-8.2

[kenichi fujisaki]

Ah i see,
My apologies, Mr. Lelievre.
Let me clarify the situation, *I followed your suggestion (Mr. Lelievre**)*.

2018-07-10 11:38 GMT+02:00 kenichi fujisaki :

> To get a recent enough version of curl, one way is to run
>
> sage -i curl
>
> Is not working
>
>
> >how can that "work fine even with macOS 10.6.8"? No worries.
> i've downloaded the curl source
> then
> cd curl-folder
> ./configure
> make
>
> finally, i got a brand new curl7.6
>
>
>
>
> 2018-07-10 11:19 GMT+02:00 Samuel Lelievre :
>
>>
>>
>> Tue 2018-07-10 01:46:56 UTC, kenichi fujisaki:
>> > I followed the method of Mr. Pasechnik.
>> > (I had to get (compile) the newest version of cUrl.)
>> > And it works fine even with macos10.6.8.
>> > Thank you very much.
>>
>> Dima Pasechnik suggested to upgrade to macOS 10.13,
>> how can that "work fine even with macOS 10.6.8"?   : )
>>
>> To get a recent enough version of curl, one way is to run
>>
>> sage -i curl
>>
>> > Now I'm fighting againt the package R [r-3.4.3.p0]:
>> > How to fix this problem?
>>
>> You could install R separately and use this ticket:
>>
>> - Sage Trac ticket 25503:
>>   Allow the use of system's R installation
>>   https://trac.sagemath.org/ticket/25503
>>
>> Or if you don't need R at all you could tweak things
>> to bypass the installation of R and rpy2.
>>
>> --
>> 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] unable to compile sage-8.2

[kenichi fujisaki]

Ah i see,
My apologies, Mr. Lelievre.
Let me clarify the situation, *I followed of your suggestion (Mr. Lelievre*
*)*.


2018-07-10 11:38 GMT+02:00 kenichi fujisaki :

> To get a recent enough version of curl, one way is to run
>
> sage -i curl
>
> Is not working
>
>
> >how can that "work fine even with macOS 10.6.8"? No worries.
> i've downloaded the curl source
> then
> cd curl-folder
> ./configure
> make
>
> finally, i got a brand new curl7.6
>
>
>
>
> 2018-07-10 11:19 GMT+02:00 Samuel Lelievre :
>
>>
>>
>> Tue 2018-07-10 01:46:56 UTC, kenichi fujisaki:
>> > I followed the method of Mr. Pasechnik.
>> > (I had to get (compile) the newest version of cUrl.)
>> > And it works fine even with macos10.6.8.
>> > Thank you very much.
>>
>> Dima Pasechnik suggested to upgrade to macOS 10.13,
>> how can that "work fine even with macOS 10.6.8"?   : )
>>
>> To get a recent enough version of curl, one way is to run
>>
>> sage -i curl
>>
>> > Now I'm fighting againt the package R [r-3.4.3.p0]:
>> > How to fix this problem?
>>
>> You could install R separately and use this ticket:
>>
>> - Sage Trac ticket 25503:
>>   Allow the use of system's R installation
>>   https://trac.sagemath.org/ticket/25503
>>
>> Or if you don't need R at all you could tweak things
>> to bypass the installation of R and rpy2.
>>
>> --
>> 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] Names of objects in sage

[Johan S. H. Rosenkilde]

> The current implementations of _repr_ gets somewhat ridiculous when we 
> combine these naming conventions in classes like CombinatorialFreeModules 
> where we end up producing things like:
>
> sage: IwahoriHeckeAlgebra('A3',q,1)
> Iwahori-Hecke algebra of type A3 in q,1 over Univariate Polynomial Ring in q 
> over Finite Field of size 5
>
> If you happen to be working over nested multivariate polynomial rings, as I 
> happen to be at the moment, then it can take 3-4 lines to print the object. 
> Personally, in the last case I would rather print

For coding theory, we recently shortened the printing considerably for
the same reason. We used to have

sage: codes.random_linear_code(GF(25), 10, 3)
Linear code of length 10 and dimension 3 over Finite Field in z2 of size 5^2

but now use the standard nomenclature for coding theory with a short
field description:

sage: C = codes.random_linear_code(GF(25), 10, 3); C
[10, 3] linear code over GF(25)

This is especially very nice in composite constructions where the
printing of the code enters as a sub-string:

sage: C.encoder()
Generator matrix-based encoder for [10, 3] linear code over GF(25)

sage: C.punctured([0, 1])
Puncturing of [10, 3] linear code over GF(125) on position(s) [0, 1]

sage: codes.SubfieldSubcode(C, GF(5))
Subfield subcode of [10, 3] linear code over GF(125) down to GF(5)

One argument in favour of having a special convention here is that a
linear code is always over a finite field, so there's not much room for
confusion. The main argument against this kind of thing is of course
that it is Bad to go against the general Sage convention, and that it is
clumsy to have special printing code in each sub-module of Sage.

Best,
Johan

-- 
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] unable to compile sage-8.2

[kenichi fujisaki]

To get a recent enough version of curl, one way is to run

sage -i curl

Is not working


>how can that "work fine even with macOS 10.6.8"? No worries.
i've downloaded the curl source
then
cd curl-folder
./configure
make

finally, i got a brand new curl7.6




2018-07-10 11:19 GMT+02:00 Samuel Lelievre :

>
>
> Tue 2018-07-10 01:46:56 UTC, kenichi fujisaki:
> > I followed the method of Mr. Pasechnik.
> > (I had to get (compile) the newest version of cUrl.)
> > And it works fine even with macos10.6.8.
> > Thank you very much.
>
> Dima Pasechnik suggested to upgrade to macOS 10.13,
> how can that "work fine even with macOS 10.6.8"?   : )
>
> To get a recent enough version of curl, one way is to run
>
> sage -i curl
>
> > Now I'm fighting againt the package R [r-3.4.3.p0]:
> > How to fix this problem?
>
> You could install R separately and use this ticket:
>
> - Sage Trac ticket 25503:
>   Allow the use of system's R installation
>   https://trac.sagemath.org/ticket/25503
>
> Or if you don't need R at all you could tweak things
> to bypass the installation of R and rpy2.
>
> --
> 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] unable to compile sage-8.2

[Samuel Lelievre]

Tue 2018-07-10 01:46:56 UTC, kenichi fujisaki:
> I followed the method of Mr. Pasechnik.
> (I had to get (compile) the newest version of cUrl.)
> And it works fine even with macos10.6.8.
> Thank you very much.

Dima Pasechnik suggested to upgrade to macOS 10.13,
how can that "work fine even with macOS 10.6.8"?   : )

To get a recent enough version of curl, one way is to run

sage -i curl

> Now I'm fighting againt the package R [r-3.4.3.p0]:
> How to fix this problem?

You could install R separately and use this ticket:

- Sage Trac ticket 25503:
  Allow the use of system's R installation
  https://trac.sagemath.org/ticket/25503

Or if you don't need R at all you could tweak things
to bypass the installation of R and rpy2.

-- 
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: Two-vertex graphs and is_prime()

[Jori Mäntysalo]

On Tue, 10 Jul 2018, david.coud...@inria.fr wrote:


A clique is a "series" module in the modular decomposition because its 
complement is not connected.
See the survey https://arxiv.org/pdf/0912.1457
* A module is of type parallel if G is not connected but its complement it
* A module is of type series if G is connected but its complement is not. In 
particular, a clique gives a series module

It is also written in the paper that the smallest prime graph is the P4.

sage: [graphs.PathGraph(i).is_prime() for i in range(5)]
[True, True, False, False, True]


I think the question is similar to asking if number 1 is prime. Directly 
by definition given in the doc there can not be a non-prime graph of at 
most 2 vertices, as there can't be nontrivial module. (Assuming that 
"trivial" means empty subset, single element or the whole graph.)


Anyways, I left this for others to decide.

--
Jori Mäntysalo

[sage-devel] Re: Two-vertex graphs and is_prime()

[David . Coudert]

A clique is a "series" module in the modular decomposition because its 
complement is not connected.
See the survey https://arxiv.org/pdf/0912.1457 
* A module is of type parallel if G is not connected but its complement it
* A module is of type series if G is connected but its complement is not. 
In particular, a clique gives a series module

It is also written in the paper that the smallest prime graph is the P4.

sage: [graphs.PathGraph(i).is_prime() for i in range(5)]
[True, True, False, False, True]


Le lundi 9 juillet 2018 07:47:16 UTC+2, Jori Mäntysalo a écrit :
>
> Graph({1:[2]}).is_prime() returns False, and the documentation says "A 
> graph is prime if all its modules are trivial (i.e. empty, all of the 
> graph or singletons)". 
>
> Is this an error, or are the two-element graphs by convention classified 
> as prime graphs? 
>
> -- 
> Jori Mäntysalo 
>

-- 
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] Matplotlib plotting style 'classic' hardcoded to Sage

[Eric Gourgoulhon]

HI,

Le lundi 9 juillet 2018 12:53:24 UTC+2, Kwankyu Lee a écrit :
>
> Consulting 
>
> https://matplotlib.org/users/dflt_style_changes.html
>
> we may keep specifically only the math font of the classic style by:
>
> mpl.rcParams['mathtext.fontset'] = 'cm'
> mpl.rcParams['mathtext.rm'] = 'serif'
>
> and adopt the default matplotlib-2 style generally. 
>

Indeed this would be a good solution. Without it, the math output is really 
ugly, as shown in this example. 

IIRC, this was the main reason to set the default style to 'classic' while 
upgrading to Matplotlib 2.1.
Let me stress that when using Jupyter notebooks with %display latex, it is 
nice to have exactly the same fonts in legend labels of plots as in MathJax 
outputs.

Best wishes,

Eric.

-- 
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.