On Saturday, March 25, 2023 at 1:56:23 PM UTC-7 Emmanuel Charpentier wrote:
A possible solution could mimin the mathematica interface, which raises an
exception when called on an system without a mathematica engine installed
: it prints an inforrmative message
pointing to the possible solution
On Sat, Mar 25, 2023 at 8:56 PM Emmanuel Charpentier
wrote:
>
> Ahem... There are two components to consider :
>
> - the package by itself
>
> - its interface to Sagemath.
>
> Case in point : the Mathematica interface, which is standard (*i. e.*
> installed in all cases), but active if and only i
Ahem... There are two components to consider :
- the package by itself
- its interface to Sagemath.
Case in point : the Mathematica interface, which is standard (*i. e.*
installed in all cases), but active if and only if Mathematica (or the
Wolfram engine) is present in the target system.
Thi
I've opened issue https://github.com/sagemath/sage/issues/35347 for this
On Saturday, March 25, 2023 at 1:40:19 PM UTC-7 Matthias Koeppe wrote:
> On Saturday, March 25, 2023 at 12:52:00 PM UTC-7 Dima Pasechnik wrote:
>
> I propose to introduce the notion of semistandard package.
>
>
> "Semista
+1
On Sat, Mar 25, 2023 at 1:40 PM Matthias Koeppe
wrote:
>
> On Saturday, March 25, 2023 at 12:52:00 PM UTC-7 Dima Pasechnik wrote:
>
> I propose to introduce the notion of semistandard package.
>
>
> "Semistandard" sounds good to me.
>
> We have a few more packages that are of this type:
> - s
On Saturday, March 25, 2023 at 12:52:00 PM UTC-7 Dima Pasechnik wrote:
I propose to introduce the notion of semistandard package.
"Semistandard" sounds good to me.
We have a few more packages that are of this type:
- sqlite is only installed if we build our own copy of python3
- openssl is on
I propose to introduce the notion of semistandard package.
Or perhaps weakly standard one?
Substandard would be too confusing IMHO...
On Sat, 25 Mar 2023, 19:43 William Stein, wrote:
> On Sat, Mar 25, 2023 at 12:13 PM Dima Pasechnik wrote:
> >
> >
> >
> > On Sat, 25 Mar 2023, 18:57 Matthias K
On Sat, Mar 25, 2023 at 12:13 PM Dima Pasechnik wrote:
>
>
>
> On Sat, 25 Mar 2023, 18:57 Matthias Koeppe, wrote:
>>
>> On Saturday, March 25, 2023 at 9:29:32 AM UTC-7 William Stein wrote:
>>
>> It seems to me that these days there are three
>> types of packages:
>>
>>
>> ...at least...
>>
>>
>>
On Sat, Mar 25, 2023 at 11:53 AM Matthias Koeppe
wrote:
>
> rpy2 is built by default when a suitable system R is detected.
Thanks. This is exactly my understanding.
The Sage docs https://doc.sagemath.org/html/en/developer/packaging.html define
standard, optional and experimental packages. The d
On Sat, 25 Mar 2023, 18:57 Matthias Koeppe,
wrote:
> On Saturday, March 25, 2023 at 9:29:32 AM UTC-7 William Stein wrote:
>
> It seems to me that these days there are three
> types of packages:
>
>
> ...at least...
>
>
> - definitely installed in every copy of sage. An example is pari.
>
>
pari c
On Saturday, March 25, 2023 at 9:29:32 AM UTC-7 William Stein wrote:
My guess is that rpy2 and all code that depends on R should be made
optional packages and marked #optional in the docs, etc.,
and it's just a bug that hasn't been done?
Details? Where do you think it is missing?
--
You r
On Saturday, March 25, 2023 at 9:29:32 AM UTC-7 William Stein wrote:
It seems to me that these days there are three
types of packages:
...at least...
- definitely installed in every copy of sage. An example is pari.
- there's an attempt to install them when sage gets built, if
conditions a
rpy2 is built by default when a suitable system R is detected.
On Saturday, March 25, 2023 at 9:29:32 AM UTC-7 William Stein wrote:
> Hi,
>
> According to
>
> https://doc.sagemath.org/html/en/reference/spkg/rpy2.html#spkg-rpy2
>
> the rpy2 package is a "standard package". However, I just checked
13 matches
Mail list logo
