Re: [sage-devel] python3 status

There are a few guards in place * Doctests don't accept print statements any more * There is a unit test that checks that code is syntactically Py3 Thats not enough to catch .iteritems, for example, but we'll get better test coverage over time. On Saturday, October 14, 2017 at 11:51:01 AM

[sage-devel] Re: optional package mpfrcx not on the mirror

fixed! On Tuesday, October 10, 2017 at 10:17:12 AM UTC+2, Maarten Derickx wrote: > > This is probably because it is still in beta. The tarbal can be found at > https://trac.sagemath.org/ticket/11806 -- You received this message because you are subscribed to the Google Groups "sage-devel"

Re: [sage-devel] doctesting tab completion

On Thursday, September 28, 2017 at 9:26:57 AM UTC+2, Dima Pasechnik wrote: > > basically, the crash comes from importing being done in a separate thread > rather than the main > thread. So an alternative way to trigger this would be to use the > appropriate multprocessing/threading module. >

Re: [sage-devel] let's make FriCAS optional

M-x sage-mode On Wednesday, September 27, 2017 at 8:03:46 PM UTC+2, Martin R wrote: > > I vote for making sage part of emacs, actually. Well, in fact, it *is* > part of emacs. > > Martin > > Am Mittwoch, 27. September 2017 19:46:09 UTC+2 schrieb John H Palmieri: >> >> >> >> On Wednesday,

[sage-devel] Re: error building openblas

OpenBLAS 0.2.20 is out: https://trac.sagemath.org/ticket/23936 On Wednesday, September 27, 2017 at 8:23:37 PM UTC+2, Samuel Lelievre wrote: > > Wed 2017-09-27 17:33:29 UTC, Stan: > > > I just tried to compile sage 8.0 on the newest debian and a Lenovo X270 > laptop: > > > >>

[sage-devel] Re: Including 64-bit-only code in Sage

On Wednesday, September 20, 2017 at 12:12:33 PM UTC+2, Dima Pasechnik wrote: > > Still, why don't we start by including this code as an experimental > package? > Thats fine, but the way I understood Kiran he wants to make it standard. -- You received this message because you are subscribed

[sage-devel] Re: Including 64-bit-only code in Sage

IMHO its a code smell if your code doesn't work on 32-bit platforms. Remember, almost all 32 bit platforms are perfectly capable of working with 64-bit integers (just not as fast). But your code must be *correct* (e.g. use uint64_t), and not just coincidentally work on some compiler/platform

[sage-devel] Re: loading ipython at (Sage) python prompt (for debugging)

sage -gdb On Tuesday, September 19, 2017 at 3:47:18 PM UTC+2, Dima Pasechnik wrote: > > Dear all, > For #22679 I need to run Sage from a debugger (lldb or gdb); I know how to > start the debugger with the right executable: > > $ . src/bin/sage-env > $ lldb local/bin/python2.7 > > and then

Re: [sage-devel] Security in sage (was How much do we support optional packages)

On Monday, September 18, 2017 at 9:38:30 PM UTC+2, Nils Bruin wrote: > > In reality this is increasingly not the case anymore: sage pulls in > packages from "Pypi" when installing > A normal install (i.e. running "make") does not pull packages from pypi. Obviously we don't have the resources to

[sage-devel] Re: Updating supported platform webpage to mach the current buildbots

On Friday, September 15, 2017 at 7:45:48 PM UTC+2, Maarten Derickx wrote: > > > > On Friday, 15 September 2017 18:55:57 UTC+2, Volker Braun wrote: >> >> >> I haven't used it in a while as buildbot, it possibly still has the old >> domain name configu

[sage-devel] Re: Updating supported platform webpage to mach the current buildbots

On Friday, September 15, 2017 at 5:46:49 PM UTC+2, Dima Pasechnik wrote: > > dima-arando >> > > this one works and warms up my office > it's just not me who actually runs it, but, IIRC, Volker :-) > (it's also a patchbot, also called arando) > I haven't used it in a while as buildbot, it

Re: [sage-devel] Re: git trac is down ?

On Tuesday, September 12, 2017 at 10:00:32 PM UTC+2, Erik Bray wrote: > > It has *never* supported read-only access via HTTP or HTTPS. > Afaik we have always supported git:// access and our documentation explicitly recommends setting it up that way; Its also how the git-trac script configures

[sage-devel] Re: Question about libgap_enter/exit

On Friday, September 8, 2017 at 6:00:31 AM UTC+2, Nils Bruin wrote: > > On Thursday, September 7, 2017 at 9:49:33 AM UTC-7, Volker Braun wrote: >> >> First question: The GAP garbage collector might delete objects, or it >> might move existing objects around in memory (it

[sage-devel] Re: Question about libgap_enter/exit

The change will mostly be to remove the libGAP_ prefix for symbols, so it should be pretty easy to sed that out (or use a macro to be compatible with both). On Thursday, September 7, 2017 at 7:45:04 PM UTC+2, Dima Pasechnik wrote: > > I would not touch C API to libGAP with a stick, given that

[sage-devel] Re: From SageNB to jupyter

You can share worksheets just by uploading them to github, for example: http://nbviewer.jupyter.org/github/vbraun/torsion_cup_product/blob/master/Y0_cohomology_ring.ipynb https://github.com/vbraun/torsion_cup_product/blob/master/Y0_cohomology_ring.ipynb On Thursday, September 7, 2017 at

[sage-devel] Re: Question about libgap_enter/exit

For the record, using the libgap Python interface (i.e. from sage.libs.gap.libgap import libgap) automatically takes care of the libgap_enter/exit business. This is only an issue if you want to the libGAP C API directly, which is what Simon is presumably asking. On Thursday, September 7, 2017

[sage-devel] Re: Question about libgap_enter/exit

First question: The GAP garbage collector might delete objects, or it might move existing objects around in memory (it is a compacting garbage collector). If your code contains C pointers to GAP objects, bad things will happen after that. Not every libGAP_* function can invoke the garbage

[sage-devel] Re: Regression: sage 8.0 startup time

Not sure if I unterstand the question. You wait and then you fork() new processes as needed. There is no ready-made thing in Sage for that purpose afaik (is that the question?) On Saturday, August 26, 2017 at 9:47:02 PM UTC+2, Samuel Lelievre wrote: > > Volker wrote: > > > For server use you

[sage-devel] Re: Regression: sage 8.0 startup time

I agree that startup on a warm cache is mostly a kernel / filesystem ram cache benchmark. The actual drive hardware is irrelevant, but background processes hitting the disk cache at the same time do matter. On a warm cache and without background IO the sage -startuptime (i.e. importing

[sage-devel] Re: nbconvert new dependencies...

Afaik nbconvert always dependend on pandoc for certain types of output (like PDF). Just like LaTeX (which is also a dependency), users have to have typesetting tools installed. On Sunday, August 20, 2017 at 9:51:37 AM UTC+2, François Bissey wrote: > > Hi all, > > I am bit concerned by the

[sage-devel] Re: ZeroDivisionError while downloading a package

I've re-uploaded it... On Saturday, August 12, 2017 at 9:53:00 AM UTC+2, vdelecroix wrote: > > There is indeed a problem with checksums > > $ cat build/pkgs/deformation/package-version.txt > d05941b > $ cat build/pkgs/deformation/checksums.ini > tarball=deformation-VERSION.tar.bz2 >

[sage-devel] Re: polytopes_db not on the mirrors?

Maybe review https://trac.sagemath.org/ticket/22400 first? ;P On Friday, August 11, 2017 at 10:58:57 PM UTC+2, vdelecroix wrote: > > Got the following > > [Errno 404] Not Found: > '//sagepad.org/spkg/upstream/polytopes_db/polytopes_db-20170220.tar.bz2' > > Vincent > -- You received this

[sage-devel] Re: unable to build sage on mac

Is this an incremental update or build from scratch? In the latter case: make distclean && make On Wednesday, August 2, 2017 at 11:03:41 PM UTC+2, Paul DesJardin wrote: > > Hi, > > I'm trying to build Sage for a Mac (OSX v. 10.12.6) and it appears to bomb > out when trying to build cython.

[sage-devel] Re: Sage 8.0 Build Error on MacOS, [mpir-3.0.0.p0] Error building MPIR.

I made https://trac.sagemath.org/ticket/23549 -- 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,

[sage-devel] Re: Sage 8.0 Build Error on MacOS, [mpir-3.0.0.p0] Error building MPIR.

Can you try building sage with AS_INTEGRATED_ASSEMBLER=1 make On Saturday, July 29, 2017 at 4:53:40 PM UTC+2, Michael Frey wrote: > > I found this thread on the MPIR issues list: > https://github.com/wbhart/mpir/issues/217 > > It appears that the MacOS assembler is old. Is there to

[sage-devel] Re: What to do with the "Timed out" failures of patchbots?

Actual traceback looks like this: sage -t --long src/sage/graphs/matchpoly.pyx Timed out ** Tests run before process (pid=22979) timed out: sage: g = graphs.PetersenGraph() ## line 104 ## sage: g.matching_polynomial() ## line

[sage-devel] Re: What to do with the "Timed out" failures of patchbots?

I ran for i in `seq 0 1000` ; do sage -t --long src/sage/graphs/matchpoly.pyx ; done and hangs after 30-ish iterations. On Sunday, July 9, 2017 at 2:03:49 PM UTC+2, Eric Gourgoulhon wrote: > > > > Le dimanche 9 juillet 2017 07:10:37 UTC+2, Ralf Stephan a écrit : >> >> (5) Test manually not

Re: [sage-devel] What to do with the "Timed out" failures of patchbots?

I've recently added code to print enhanced tracebacks when we kill a test due to timeout (#23208), if you have gdb installed then you'll get some idea of what it was doing when it timed out. I've seen a few cases on the buildbot that point to FFPACK::CharPoly. This might be a bug in linbox that

[sage-devel] Re: What to do with the "Timed out" failures of patchbots?

(4) Try to find out why these tests time out and fix the underlying issue -- 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

Re: [sage-devel] Re: Is it possible to make an arm port of sage?

Up until about a year ago we had an ARM buiildbot on a Oxford University machine; But that seems to have disappeared (maybe Dima knows). On Sunday, July 2, 2017 at 6:58:40 PM UTC+2, William wrote: > > > > > On Jul 2, 2017, at 9:26 AM, aishen > wrote: > > or orange pi

[sage-devel] Re: Error installing OpenBlas on Linux Mint

Whats your CPU? This seems to be https://github.com/xianyi/OpenBLAS/issues/1139 Try building Sage with OPENBLAS_CONFIGURE="TARGET=ATOM" make On Saturday, July 1, 2017 at 8:02:33 PM UTC+2, Gabriel Lipnik wrote: > > Hey! > > I wanted to install Sage and got an error message while installing

[sage-devel] Re: Error installing spkg openblas-0.2.19.p0 in OS X

Your linker (xcode) is too old for haswell; Either upgrade to osx 10.10 + latest xcode or try OPENBLAS_CONFIGURE="TARGET=ATOM" make to build an openblas that doesn't take advantage of your cpu. On Saturday, July 1, 2017 at 7:24:39 PM UTC+2, J.M. Alonso wrote: > > I tried to install SAGE in

Re: [sage-devel] Re: Conda package for Sage

On Thursday, June 15, 2017 at 3:10:22 PM UTC+2, Nathan Dunfield wrote: > > but of course the Mac Mini has only 2 cores. > For the record, our OSX buildbot is a quad-core mac mini (i7-3720QM CPU @ 2.60GHz). CPU-wise its actually reasonable, but the box is just too small. Fan goes crazy if you

Re: [sage-devel] Re: Conda package for Sage

On Thursday, June 15, 2017 at 11:25:57 AM UTC+2, Jean-Pierre Flori wrote: > > And is unfortunately illegal according to Apple though I'm not a lawyer. > May or may not be legal depending on your jurisdiction. In the US its illegal according to the Psystar case. In Germany, most click-through

[sage-devel] Re: Sage Python 3 proposal

Sounds great! I also thought about building both py2+3 at the same time, it would be a great debugging help during the transition if you can easily run both. Then in 3 years we'll just cut out the py2 part and be done with it... -- You received this message because you are subscribed to the

Re: [sage-devel] Brainstorming about Sage dependencies from system packages

In fact, if we were to do some major changes to the build system we should consider building on top of conda. In particular, we shouldn't just crap arbitrary files into $SAGE_LOCAL during build, but turn each package into separate binary achive that then gets installed. * Going back in the

[sage-devel] Re: Error downloading cmake-3.8.0.tar.gz

ok fixed On Wednesday, May 24, 2017 at 10:52:13 AM UTC+2, Sébastien Labbé wrote: > > Tarball available at ​https://cmake.org/files/v3.8/cmake-3.8.0.tar.gz > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop

[sage-devel] Re: PyNormaliz-1.5.tar.gz not available on the mirrors

Ok fixed! On Sunday, May 21, 2017 at 3:52:32 AM UTC+2, Thierry (sage-googlesucks@xxx) wrote: > > Hi, > > apparently, PyNormaliz-1.5.tar.gz is not available on the mirrors, while > ticket #22684 was recently merged. > > It can be downloaded at > >

[sage-devel] Re: Poll for issue G1 a specific guideline for writing docstrings

I'd try to avoid the entire construct; Its the linguistic equivalent of if condition: return True else: return False Just say "Test condition" in the docstring. On Wednesday, May 17, 2017 at 4:07:29 PM UTC+2, Kwankyu Lee wrote: > > We do a poll for adopting an official guideline for

[sage-devel] Re: ImportError: This platform lacks a functioning sem_open implementation, ... see issue 3770

Is there something in the Python build log (logs/pkgs/python2-2.7.13.p1.log) that would explain the issue with semaphores? On Thursday, May 11, 2017 at 7:50:33 PM UTC+2, Kamil Pliszka wrote: > > Hi, > I have problem when compiling sage7.6: > > ... > [sagelib-7.6] building

[sage-devel] Re: Should RLF/CLF be exact ?

The lazy fields are not just wrappers around self._value: sage: a = RLF(0.1) sage: RealIntervalField(150)(a) 0.10? sage: RealIntervalField(150)(a._value) 0.1555111512312578270211815834046? On Monday, May 8, 2017 at 8:50:48 PM UTC+2,

Re: [sage-devel] building pdf docs fails

/trac.sagemath.org/ticket/22252, to compensate > for the fact that Sphinx no longer included it by default. The 'iftex' > package is part of TeXLive; I don't know about other TeX distributions. > > John > > > On Saturday, April 29, 2017 at 3:52:49 AM UTC-7, Volker Braun wrote:

Re: [sage-devel] building pdf docs fails

I don't have iftex.sty installed (Fedora 25), so its not required directly. Your tex installation might (erroneously) have it as a transitive dependency, though. I'd try with a clean build first. Otherwise install the iftex package: $ tlmgr search --file iftex.sty iftex:

Re: [sage-devel] Re: Trac slow

Did you run that from within UC Davis? There is quite a number of academic networks that subscribe to the "if we filter out ICMP at the network border we can't be hacked" fallacy. A better test would be: $ ssh g...@trac.sagemath.org PTY allocation request failed on channel 0 hello vbraun, this

Re: [sage-devel] Re: RR, coercion of numpy.float32() and clang - coercion experts needed

There is this: sage: import numpy as np sage: cm = sage.structure.element.coercion_model sage: cm.explain(polygen(RR), np.float32('1.5'), operator.mul) Action discovered. Right scalar multiplication by Real Double Field on Univariate Polynomial Ring in x over Real Field with 53 bits of

[sage-devel] Re: SageNB -> Jupyter conversion needs testers

g like > "Launch the browser? (yes/no)" > > > On Sunday, April 16, 2017 at 3:11:08 PM UTC+1, Volker Braun wrote: >> >> The token is a security measure so no other (local) user can run >> arbitrary code in your notebook. It is printed during startup (see below). >

[sage-devel] Re: SageNB -> Jupyter conversion needs testers

The token is a security measure so no other (local) user can run arbitrary code in your notebook. It is printed during startup (see below). Usually, jupyter will launch its own browser so the token is used automatically... $ sage -n

Re: [sage-devel] OSX Xcode 8.3 breaks openblas

It might be hardware specific; I take it you don't have a sandy bridge CPU? On Tuesday, April 11, 2017 at 12:19:26 AM UTC+2, John H Palmieri wrote: > > I ran Xcode to make sure it would update any component pieces and then ran > a build from scratch. Openblas built just fine for me (same Xcode

Re: [sage-devel] OSX Xcode 8.3 breaks openblas

This is now https://trac.sagemath.org/ticket/22794 -- 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,

Re: [sage-devel] OSX Xcode 8.3 breaks openblas

çois wrote: > > I may need to try a build from scratch, takes time (to build gcc mainly). > > François > > On 11/04/2017, at 09:58, Volker Braun <vbrau...@gmail.com > > wrote: > > > > Yes, same here: > > > > osx:~ vbraun$ xcode-select -v >

Re: [sage-devel] OSX Xcode 8.3 breaks openblas

rote: > > > > It makes shifting to clang a bit more urgent. I will look into that > particular fault > > ASAP. > > > > François > > > >> On 11/04/2017, at 07:58, Volker Braun <vbrau...@gmail.com > > wrote: > >> &g

[sage-devel] OSX Xcode 8.3 breaks openblas

The most recent Xcode update seems to have broken openblas on the OSX buildbot. Build log errors start at: gcc -c -O2 -DMAX_STACK_ALLOC=2048 -DEXPRECISION -m128bit-long-double -Wall -m64 -DF_INTERFACE_GFORT -fPIC -DNO_WARMUP -DMAX_CPU_NUMBER=8 -DASMNAME=_ -DASMFNAME=__ -DNAME=_ -DCNAME=

Re: [sage-devel] Re: help needed to debug a systematically killed Sage

On Friday, April 7, 2017 at 6:29:14 PM UTC+2, vdelecroix wrote: > > This went fine (see the attached log for imports)! next step? sage -gdb -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving

[sage-devel] Re: help needed to debug a systematically killed Sage

First step is probably to trace imports: sage -python -v import sage.all If that fails, gdb. On Friday, April 7, 2017 at 1:35:13 PM UTC+2, vdelecroix wrote: > > Dear all, > > I have trouble building Sage for the patchbot. My procedure consists > just in launching the attached script. It

[sage-devel] Re: sip package not on mirrors

fixed! On Friday, April 7, 2017 at 10:05:47 AM UTC+2, vdelecroix wrote: > > Hello, > > Even though sip is an optional package it is not available on the mirrors > > Attempting to download package sip-4.18.tar.gz from mirrors > >

[sage-devel] Re: Proposal: remove SAGE_LOCAL/lib/python

+1 On Thursday, April 6, 2017 at 12:10:25 AM UTC+2, John H Palmieri wrote: > > Did that subject line get your attention? > > I propose that we remove the symbolic link SAGE_LOCAL/lib/python, keeping > the two directories SAGE_LOCAL/lib/python2.7 and SAGE_LOCAL/lib/python3.5. > The link points

[sage-devel] Re: help required for debugging on apple

Whats problematic is that comparison is falling back to memory position in your patch. An integer like 4 is almost certainly allocated earlier than the symbolic pi; Repeated runs on the same computer are highly likely to end up in the same memory order but other operating systems / malloc

Re: [sage-devel] Sage 7.5 for Windows?

I'm building a 7.6 vm this weekend. IMHO the docker image is the second-best solution, the best being just installing Linux natively on your computer. Of course thats assuming that your goal is scientific computation. On the other hard, if you just want to get to a notebook with the least

[sage-devel] Re: Default display for equations in notebook

Instead of adding another %display option, why not fix the standard %display typeset? If mathjax can't display some object then it just shouldn't display using mathjax in jupyter. On Tuesday, March 21, 2017 at 12:31:08 AM UTC+1, Travis Scrimshaw wrote: > > Eric Gourgoulhon and I were

[sage-devel] Re: An "easy looking" computation in AA that sage can't do

Backtrace leads into cypari2 polredbest, possibly a pari bug: sage: a=AA(sqrt(sqrt(5))) : r=AA(sqrt((AA(sqrt(13))-a)^2+3)) : c=a+r : : d= AA(sqrt(r^2-a^2)) : : 2*a*c == c^2 - d^2 : ^C---

Re: [sage-devel] Sage 7.5 for Windows?

Yes, its scripted (https://bitbucket.org/vbraun/sage-virtual-appliance-buildscript). I'll try to remember to build one for Sage 7.6 which should be out soon... On Saturday, March 18, 2017 at 1:57:42 PM UTC+1, kcrisman wrote: > > > I don't know who maintains the VMs. But for a lighter-weight

[sage-devel] Re: PYTHONPATH breaks Python3

I noticed that, too. We should just remove it. I doesn't just break our own python3, it also is a major pain if you want to use gdb to debug stuff (which embeds python3 nowadays). On Saturday, March 11, 2017 at 1:28:52 AM UTC+1, vdelecroix wrote: > > Dear all, > > The installation of both

[sage-devel] Re: git trac try

Thats basically it. The script takes the develop branch and merges in the ticket. And in a "detached head", i.e. without messing up an existing branch. On Thursday, March 9, 2017 at 10:41:07 PM UTC+1, Paul Masson wrote: > > The documentation https://github.com/sagemath/git-trac-command at say

[sage-devel] Re: report on py3

On Wednesday, March 8, 2017 at 8:59:07 PM UTC+1, Frédéric Chapoton wrote: > > * fix the SAGE_PYTHON3 build > This should just be a matter of installing our python package dependencies into python3 as well as python2. I didn't think about that. We should definitely have some more regression

[sage-devel] Re: Sage creates some *.pyc files in src/sage

I'm pretty sure src/sage/env.py and version.py is imported during build by some scripts to figure out directory locations. The ipython_kernel.install is imported once to install the ipython kernel. On Tuesday, March 7, 2017 at 7:20:15 PM UTC+1, John H Palmieri wrote: > > If I run "make" in

[sage-devel] Re: Why is "TERM" removed when spawning something?

There are comments in the code about that, do they not answer your question? On Sunday, February 26, 2017 at 2:22:23 PM UTC+1, Simon King wrote: > > Hi! > > Trying to create a pexpect interface to Polymake, I came accross the > following problem: > > In sage.interfaces.expect.Expect._start,

[sage-devel] Re: PPL wrapper bug

sage: Cone1.__cmp__? Signature: Cone1.__cmp__(right) Docstring: Compare "self" and "right". INPUT: * "right" -- anything. OUTPUT: * 0 if "self" and "right" are cones of any kind in the same lattice with the same rays listed in the same order. 1 or -1

[sage-devel] Re: SageNB -> Jupyter conversion needs testers

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

Re: [sage-devel] Meaning of log2 etc.

Well log2 could be callable and (coerce to) a constant at the same time, so its not entirely clear that that train has departed... On Thursday, February 23, 2017 at 10:43:29 AM UTC-5, Michael Orlitzky wrote: > > On 02/23/2017 08:15 AM, Peleg Michaeli wrote: > > Is it not far better to have

Re: [sage-devel] patchbot error: HTTP Error 413: Request Entity Too Large

There is no general client request body size limit, this is a configuration setting for your wsgi server or reverse proxy that is in front of the patchbot. If you need help debugging this then post the relevant **server** log that shows the 413 being triggered. On Thursday, January 26, 2017

[sage-devel] Re: Timeouts on patchbots

I think there is also still an issue where openblas internal state becomes wedged when interrupting; I disabled multi-threading which made it much less frequent but it is not 100% reliable. I'm seeing random issues in /abvar/ occasionally on the buildbot. On Monday, February 13, 2017 at

[sage-devel] Re: What is the right way to deal with mpfr_t arrays/vectors/lists in cython?

On Sunday, February 5, 2017 at 11:38:25 AM UTC+1, mmarco wrote: > > cdef extern from "my_library.h": > mpfr_t* my_function (mpfr_t *_coef) > That isn't exactly idiomatic C++, but ok /home/mmarco/sage/local/lib/python2.7/site-packages/IPython/core/ultratb.pyc > in

[sage-devel] Re: doctesting of external packages

I would recommend the import statements. Then you can paste the doctest into Sage and it just works. Thats a big plus IMHO. Explicit is better than implicit. On Thursday, February 2, 2017 at 5:39:58 PM UTC+1, Christian Nassau wrote: > > Dear Sage Colleagues, > > The recently merged changes

[sage-devel] Re: Closing wontfix-tickets

Done On Thursday, January 19, 2017 at 9:48:58 AM UTC+1, Jori Mäntysalo wrote: > > 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

Re: [sage-devel] Re: Release note auto-generation RFC

On Friday, January 13, 2017 at 8:38:50 PM UTC+1, Jori Mäntysalo wrote: > > If #1 adds foo() to graphs and #2 adds bar(), then the list should have > something like "Graph enchancements: foo() and bar()." Which ticket should > contain that information? > Ticket #2 could delete

[sage-devel] Re: Release note auto-generation RFC

etc. > (This might even fit within some of ODK deliverables :-)) > > Dima > > > > On Wednesday, January 11, 2017 at 11:09:53 PM UTC, Volker Braun wrote: >> >> There is a somewhat painless approach to generating human-readable >> release notes using https://github.com/ha

[sage-devel] Re: Release note auto-generation RFC

Yes, to the Sage src tree. That is, we would add a newsfragments directory somewhere under $SAGE_ROOT. On Thursday, January 12, 2017 at 8:15:48 AM UTC+1, Simon King wrote: > > Hi Volker, > > On 2017-01-11, Volker Braun <vbrau...@gmail.com > wrote: > > There is a so

[sage-devel] Release note auto-generation RFC

There is a somewhat painless approach to generating human-readable release notes using https://github.com/hawkowl/towncrier. As far as the ticket author is concerned, if you think that your ticket #12435 is of wider interest and should be announced then all you'd have to do is add a file echo

[sage-devel] Re: releasing memory in compiled components

On Monday, January 9, 2017 at 9:08:46 PM UTC+1, Jean-Pierre Flori wrote: > > Isn't that the correct way to trigger Cytohn writin down an explicit call > to the destructor? > Right, every new'ed C++ object should be del'ed somewhere in the program. I misunderstood what you meant. -- You

[sage-devel] Re: releasing memory in compiled components

On Monday, January 9, 2017 at 4:45:19 PM UTC+1, Jean-Pierre Flori wrote: > > You can just use the Python "del" operator and Cython should translate it > to a destructor call. > No, there is the following caveat when cyclic Python references are involved: __dealloc__ is always called, but there

Re: [sage-devel] denominator() hangs on a large fraction

Most likely the pynac-0.7.2 update.. On Wednesday, January 4, 2017 at 5:19:36 PM UTC+1, Eric Gourgoulhon wrote: > > Works in Sage 7.5.beta5. > So the issue has been introduced somewhere between 7.5.beta6 and 7.5.rc1... > > > Le mercredi 4 janvier 2017 17:08:51 UTC+1, tdumont a écrit : > > >>

Re: [sage-devel] Re: threejs as standard package

On Thursday, December 29, 2016 at 11:48:24 AM UTC+1, Erik Bray wrote: > > I agree. In a way I see sage.env as that configuration file-- Of course its not unrelated, but I'd think of it as our internal api for accessing configuration data. The configuration file itself shouldn't be installed

Re: [sage-devel] Re: threejs as standard package

Instead of an ever-increasing list of undocumented environment variables like THEBE_DIR it would be nice to get that kind of runtime data from a configuration file... On Thursday, December 29, 2016 at 11:15:20 AM UTC+1, Erik Bray wrote: > > On Tue, Dec 27, 2016 at 11:34 PM, Paul Masson

Re: [sage-devel] Re: Problems Authenticating to Trac Server with Public Key

The ~/.gitolite/logs/ may have some clues about what is going on... -- 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

Re: [sage-devel] Re: Problems Authenticating to Trac Server with Public Key

On Saturday, December 24, 2016 at 2:08:42 PM UTC+1, Maxie Schmidt wrote: > > debug1: /home/maxie/.ssh/config line 4: Applying options for * > Thats a bit suspicious, I hope you know which options you are applying globally debug1: Offering RSA public key: /home/maxie/.ssh/id_rsa.pub > debug3:

Re: [sage-devel] Re: trac is down

e trac server? > > > On Sunday, December 18, 2016 at 5:47:04 PM UTC-6, Volker Braun wrote: >> >> works for me, too >> >> On Sunday, December 18, 2016 at 11:55:31 PM UTC+1, William wrote: >>> >>> The trac website is up for me and my uptimerobot

Re: [sage-devel] Re: trac is down

works for me, too On Sunday, December 18, 2016 at 11:55:31 PM UTC+1, William wrote: > > The trac website is up for me and my uptimerobot monitor hasn't shown any > downtime. > > On Sun, Dec 18, 2016 at 2:17 PM Maxie Schmidt > wrote: > >> The trac server ssh and website are

[sage-devel] Re: Problems Authenticating to Trac Server with Public Key

On Sunday, December 18, 2016 at 7:30:16 PM UTC+1, Maxie Schmidt wrote: > > The trac server and website are down right now for me as well. Here is the > output of "ssh -vvv myuse...@trac.sagemath.org " from > yesterday: > Thats to be expected, you don't have a unix user account on trac. Only

[sage-devel] Re: Problems Authenticating to Trac Server with Public Key

Can you run ssh -vv g...@trac.sagemath.org info and look through the debug info? On Saturday, December 17, 2016 at 7:27:21 PM UTC+1, Maxie Schmidt wrote: > > Hello. > > I have an account on and have uploaded my local id_rsa.pub key in the sage > math trac server web interface. The command

[sage-devel] Re: Cross-type comparisons

In the Python3 spirit, it would be nice to get a type error instead of ordering by id: $ python3 >>> 1 < 'a' Traceback (most recent call last): File "", line 1, in TypeError: unorderable types: int() < str() The current behavior is certainly not great, and was just defaulted because thats

Re: [sage-devel] Re: devising a speed comparison test between different types

On Sunday, December 4, 2016 at 5:58:45 PM UTC+1, Pierre wrote: > -- numpy.int32 or int.64: like "int" initially, but works mod 2^32 or > 2^64, and gives an overflow warning when it happens. No increase in > speed, for general reasons which I will just call "overhead" for lack > of a better

Re: [sage-devel] Re: three.js on 7.5 beta 5: cpu...

Well if the scene is static, the controls didn't change, and the canvas size didnt't change then your callback in requestAnimationFram should just do nothing instead of repainting the unchanged scene, right? On Saturday, December 3, 2016 at 9:46:50 PM UTC+1, Paul Masson wrote: > > > > On

Re: [sage-devel] SAGE_ATLAS_LIB vs openblas

+1 for the manual (bring your own .pc file) approach to blas configuration. Otherwise you'd need configure switches for all combinations of (blas+cblas+lapack) * (cflags+ldflags+libs) which would make it even more difficult to use. -- You received this message because you are subscribed to

Re: [sage-devel] Re: OpenSSL as a new systemwide Sage dependency ?

On Friday, December 2, 2016 at 9:39:13 AM UTC+1, Dima Pasechnik wrote: > > Do you understand the story about root certs here? Is it a missing python > code (in some package, existing or not?) that would be able to access OSX > certs store? > Apple has the root certs in their own keychain,

Re: [sage-devel] Re: OpenSSL as a new systemwide Sage dependency ?

On Linux, you can build Sage with and without openssl. If you ever hit the network you really should build with openssl(-devel) available, it will be picked up automatically. But its not a requirement. Though we should probably strongly recommend it in the installation instructions. GnuTLS and

[sage-devel] Re: OSX 10.12 openssl and other problems

Thats a big shit sandwich We could just copy Apple's openssl headers from the last version. Presumably they'll keep shipping the old library since Python keeps depending on it. Or are they planning to pull a 3.5mm plug here and ship Python without ssl in the next version? On Tuesday,

[sage-devel] Re: libgap and dynamic loading of GAP packages

You need the "unprefixed libgap" where the symbols are not prefixed. https://trac.sagemath.org/ticket/19915 On Tuesday, November 22, 2016 at 11:22:02 PM UTC+1, Nicolas M. Thiéry wrote: > >Dear Volker, Dima, Markus, > > For my research, I and several persons in the same area would

[sage-devel] Re: OpenSSL as a new systemwide Sage dependency ?

Actually OSX is foobar'ed even then, Apple's ancient openssl just doesn't support TLSv1.2. Some sites are already requiring that: osx:~ vbraun$ openssl s_client -connect www.kernel.org:443 CONNECTED(0003) write:errno=54 On Monday, November 21, 2016 at 12:21:31 PM UTC+1, Emmanuel

Re: [sage-devel] Checking out old branches

4, it checks >> out to a sibling folder /path/to/sage-7.4_merge_tree. Automating it is a >> bit more complicated though; if the merge fails and the user has to correct >> it manually, you either need a separate command to pull back into the main >> repository or a way to

Re: [sage-devel] Checking out old branches

Thats a wrong-way merge and is confusing if one ever wants to understand the history of the ticket. The convention is that the feature branch is first, and you merge in dependencies. On Sunday, November 20, 2016 at 2:31:57 AM UTC+1, David Roe wrote: > > I've implemented a new git-trac

<    1   2   3   4   5   6   7   8   9   10   >