I found that when trying to access LATeX (MacTeX) calls in a Sage notebook
via MatPlotLib or directly Sage would report that it could not find some
TeX function. It appears that the PATH variable being used by the Sage app
is pointing to /usr/texbin, not /Library/TeX/texbin. As a workaround I
On 2017-01-19 17:44, William Stein wrote:
On Thu, Jan 19, 2017 at 9:39 AM, Jeroen Demeyer wrote:
On 2017-01-19 17:17, William Stein wrote:
... and presumably what we already decided is now completely
impossible to implement and banned from Python3?
I don't think we ever decided anything. F
On 2017-01-19 19:18, Travis Scrimshaw wrote:
I thought Frédéric actually removed that test (at my insistence)?
Maybe in a ticket which is not merged yet? In any case, that test is
still there in 7.5.1.
--
You received this message because you are subscribed to the Google Groups
"sage-devel"
Hi,
On 19/01/2017 18:44, William Stein wrote:
On Thu, Jan 19, 2017 at 9:39 AM, Jeroen Demeyer wrote:
On 2017-01-19 17:17, William Stein wrote:
... and presumably what we already decided is now completely
impossible to implement and banned from Python3?
I don't think we ever decided anythi
For the cmp problem, Jeroen as suggested implementing our own cmp function.
Thus, we just add this to the imports of every file that we don't want to
go to rich comparisons (i.e., that needs it), which tries calling __cmp__
then falls back to ordering. This should at least get all of Sage to
co
Hi,
A bit more clarification. I upgraded to 7.5.1 using sage --upgrade. There
is a copy of libiconv in /usr/local/lib and one that the Mac OS installs in
/usr/lib. The command "sage -installed" reports that iconv is installed.
This is obviously a minor problem, given that no one else has rep
Hello, this year's Google Summer of Code 2017 just started.
I assume we will try again to be part of it, and therefore I've
started the registration process.
The most important aspect is to have mentors and project proposals.
For that, I've started this year's wiki page as a copy of last year:
h
On Thu, Jan 19, 2017 at 9:39 AM, Jeroen Demeyer wrote:
> On 2017-01-19 17:17, William Stein wrote:
>>
>> ... and presumably what we already decided is now completely
>> impossible to implement and banned from Python3?
>
>
> I don't think we ever decided anything. For Parents, we use Robert
> Brads
On 2017-01-19 17:17, William Stein wrote:
... and presumably what we already decided is now completely
impossible to implement and banned from Python3?
I don't think we ever decided anything. For Parents, we use Robert
Bradshaw's implementation from 2008 but it's not documented what it does
o
On Thu, Jan 19, 2017 at 9:08 AM, Jeroen Demeyer wrote:
> On 2017-01-19 07:47, Frédéric Chapoton wrote:
>>
>> For 1C), the cmp problem has not been considered yet, but it is *huge*.
>
>
> An important part of the cmp() problem is that we need to decide *how*
> comparison of Sage objects should work
On 2017-01-19 07:47, Frédéric Chapoton wrote:
For 1C), the cmp problem has not been considered yet, but it is *huge*.
An important part of the cmp() problem is that we need to decide *how*
comparison of Sage objects should work.
For example, it seems that we cannot really agree on what shoul
Are you able to build Sage under/in homebrew?
On Thursday, January 19, 2017 at 3:01:49 PM UTC, Kosta wrote:
>
> Right now (pre-ticket) if you try to build sage on OSX Sierra and above,
> it will be built without
> OpenSSL support. I'm not sure what happens if you download a prebuilt
> package bu
On Thu, Jan 19, 2017 at 8:47 AM, Frédéric Chapoton wrote:
> Hello,
>
> let me try to summarize : we are still quite far from being python3
> compatible.
>
> There are two main milestones we must reach:
>
> 1) being able to build sage with python3 ;
> (with substeps: 1A) being able to cythonize al
Right now (pre-ticket) if you try to build sage on OSX Sierra and above, it
will be built without
OpenSSL support. I'm not sure what happens if you download a prebuilt
package but somehow I assumed
that if you don't have OpenSSL installed, then you can't use OpenSSL
(otherwise I don't understand
th
On Thursday, January 12, 2017 at 2:00:37 PM UTC+3, David Joyner wrote:
>
> On Thu, Jan 12, 2017 at 3:43 AM, GK >
> wrote:
> >
> >>
> >> I am not having any problem starting the notebook. You might genuinely
> be
> >> out of memory, or hard drive space.
> >>
> >
> > I am not having trouble
+1, please
Le jeudi 19 janvier 2017 09:48:58 UTC+1, Jori Mäntysalo a écrit :
>
> Could someone close all 49 wontfix-positive_review -tickets?
>
> IMO it would be nice to have this done after every stable release.
>
> --
> Jori Mäntysalo
>
--
You received this message because you are subscrib
On 2017-01-19 04:17, Travis Scrimshaw wrote:
Frédéric has been working on getting stuff Python3 compatible. When he
wakes up, he probably will give us an assessment. I believe he is able
to get Sage to compile with Python3 with perhaps a few small tickets.
Note the word "compile", which is not
Could someone close all 49 wontfix-positive_review -tickets?
IMO it would be nice to have this done after every stable release.
--
Jori Mäntysalo
There is no summary page for the cmp situation anywhere.
You can look at #16537 and #17175
To know how this was solved in some cases, look at the tickets here:
https://trac.sagemath.org/query?component=python3
having cmp in the title. Almost every case is different, because it can be
either py
19 matches
Mail list logo
