Not currently (though we have "Unknown"). The main problem is the
interaction with Python booleans and the operators "or", "and", "not"
(which are *not* logical operators). The Sage "Unknown" is badly
broken for these reasons
sage: not Unknown # waiting for Unknown
True
sage: Unknown or False
When developing a software which aims to prove something, it seems
necessary to be able to return something in
{True, False, Indeterminate}.
Of course, there are many possibilities to do this, but is there a
"canonical" one in Sage ?
In C++, for example, there exists the Boost Tribool library
(h
On Tuesday, November 15, 2016 at 2:34:00 AM UTC+1, Paul Masson wrote:
>
> Or is the current recommendation to always merge develop after every new
> beta?
>
I think it's to use it sparingly. That the history from git log is gobbled
is IMO a git bug.
The branch I've been working on has been und
On Tuesday, November 15, 2016 at 4:36:01 AM UTC+1, Nils Bruin wrote:
>
> ... The "abs" in the global namespace is just the generic python one:
> abs(a) dispatches to a.__abs__()
>
> sage: class A(object):
> : def __abs__(self):
> : return "abs"
> :
> sage: a=A()
> sage
On Monday, November 14, 2016 at 12:49:17 PM UTC-8, Paul Masson wrote:
>
> Doesn't the explicit alias to abs_symbolic put abs into the global name
> space as a symbolic function? Why does an import of abs create more
> problems than the alias? Is this a general Python problem or something
> speci
An op-ed by a prof. at Berkeley entitled "Mathematical Software: Is It
Mathematics or Is It Software?" should be of interest to this group.
http://www.ams.org/journals/notices/201611/
I'm told that discussion on the Notices website is highly encouraged!
- kcrisman
--
You received this message be
On Monday, November 14, 2016 at 3:51:49 PM UTC-8, Dima Pasechnik wrote:
>
> Did you have a pressing need to build an old branch?
> I'd normally first rebase over the latest beta, and then build.
>
What do you mean by "rebase" precisely? Just merging the current develop
branch or something else?
Did you have a pressing need to build an old branch?
I'd normally first rebase over the latest beta, and then build.
On Monday, November 14, 2016 at 10:56:35 PM UTC, Paul Masson wrote:
>
> I'm running into an problem that after building 7.5.beta1 or 7.5.beta2,
> building a branch based on 7.4.bet
I'm running into an problem that after building 7.5.beta1 or 7.5.beta2,
building a branch based on 7.4.beta5 fails for two packages: cysignals-1.1.1
and mistune-0.7.3. The only way I've found around it so far is to run make
dist-clean && make but that takes more time than should be necessary.
I
Dear All,
sorry for the late reply and thank you very much for the input.
As far as having methods not always defined the consensus here is leaning
towards making sublcasses but I am quite reluctant to do that because of
future things I want to implement. Down the road there are going to be m
The recommended (for power users) way to run the virtual machine is using
their host browser, just go to http://localhost:8000. This requires a
non-broken windows networking stack, though (and various dodgy windows
programs can interfere).
In the kiosk mode you can still go back,e.g. open a not
Since abs is declared in functions/other.py as an explicit alias of
abs_symbolic, I figured it wouldn't hurt to import if from that file but on
https://trac.sagemath.org/ticket/21657 it leads to a variety of failed
doctests. Some of these are coercion errors and others are more severe. I'd
like
On Mon, Nov 14, 2016 at 12:46 PM, William Stein wrote:
> On Mon, Nov 14, 2016 at 12:40 PM, Dima Pasechnik wrote:
>>
>>
>> On Monday, November 14, 2016 at 2:21:32 PM UTC, Stan wrote:
>>>
>>> Dear all,
>>>
>>> A student of mine has been using SMC because the sage appliance in
>>> virtualbox did not
On Mon, Nov 14, 2016 at 12:40 PM, Dima Pasechnik wrote:
>
>
> On Monday, November 14, 2016 at 2:21:32 PM UTC, Stan wrote:
>>
>> Dear all,
>>
>> A student of mine has been using SMC because the sage appliance in
>> virtualbox did not appear very useful with the jupyter notebook. Now that he
>> enco
On Monday, November 14, 2016 at 5:44:01 PM UTC, William wrote:
>
> On Mon, Nov 14, 2016 at 8:40 AM, Erik Bray > wrote:
> > On Mon, Nov 14, 2016 at 4:49 PM, William Stein > wrote:
> >> On Mon, Nov 14, 2016 at 6:21 AM, Stan >
> wrote:
> >>> Dear all,
> >>>
> >>> A student of mine has been u
On Monday, November 14, 2016 at 2:21:32 PM UTC, Stan wrote:
>
> Dear all,
>
> A student of mine has been using SMC because the sage appliance in
> virtualbox did not appear very useful with the jupyter notebook. Now that
> he encountered a critical bug in SMC (reported offline), he is back with
On Mon, Nov 14, 2016 at 8:40 AM, Erik Bray wrote:
> On Mon, Nov 14, 2016 at 4:49 PM, William Stein wrote:
>> On Mon, Nov 14, 2016 at 6:21 AM, Stan wrote:
>>> Dear all,
>>>
>>> A student of mine has been using SMC because the sage appliance in
>>> virtualbox did not appear very useful with the ju
On Mon, Nov 14, 2016 at 4:49 PM, William Stein wrote:
> On Mon, Nov 14, 2016 at 6:21 AM, Stan wrote:
>> Dear all,
>>
>> A student of mine has been using SMC because the sage appliance in
>> virtualbox did not appear very useful with the jupyter notebook. Now that he
>> encountered a critical bug
On Mon, Nov 14, 2016 at 6:21 AM, Stan wrote:
> Dear all,
>
> A student of mine has been using SMC because the sage appliance in
> virtualbox did not appear very useful with the jupyter notebook. Now that he
> encountered a critical bug in SMC (reported offline), he is back with the
I'm not aware
Dear all,
A student of mine has been using SMC because the sage appliance in
virtualbox did not appear very useful with the jupyter notebook. Now that
he encountered a critical bug in SMC (reported offline), he is back with
the sage appliance in VB but it is truly a nightmare. The installation
20 matches
Mail list logo
