Re: [sage-devel] maxima install should not consider local config files

I'll see if I can figure that out. The Lisp is ECL, which I'm not very familiar with. Bill On Wednesday, September 23, 2015 at 11:57:38 PM UTC-7, François wrote: > > > > On 24/09/2015, at 16:51, Bill Janssen > > wrote: > > > > Compiling Sage from

[sage-devel] Re: sage -update not working

PM UTC-7, Dima Pasechnik wrote: > > > > On Wednesday, 23 September 2015 15:38:11 UTC-7, Bill Janssen wrote: >> >> I downloaded the OS X version of Sage 6.8, unpacked it, and tried to run >> "sage -update". However, it fails immediately: >> > > 6.8

[sage-devel] maxima install should not consider local config files

Compiling Sage from scratch (6.8 sources) fails because the maxima install fails, because it loads ~/quicklisp/setup.lisp. Am I the first Lisp programmer to try this? Bill /usr/bin/install -c mgnuplot '/Volumes/datanew/local/sage-6.8/local/libexec/maxima/5.35.1' /bin/sh /Volumes/datanew/local

[sage-devel] sage -update not working

I downloaded the OS X version of Sage 6.8, unpacked it, and tried to run "sage -update". However, it fails immediately: touch /Volumes/datanew/local/sage-6.8/local/var/lib/sage/installed/prereq /Volumes/datanew/local/sage-6.8/build/pipestatus "sage-spkg -f bzip2-1.0.6.20140317 2>&1" "tee -a /V

Re: [sage-devel] updating sage-env LD_LIBRARY_PATH from spkg-install

code to detect this, and put out a warning to the user, telling them to add the required LD_LIBRARY_PATH setting to their sagerc file. Somewhat unsatisfactory. Bill On Monday, September 21, 2015 at 10:49:05 AM UTC-7, Jeroen Demeyer wrote: > > On 2015-09-21 19:23, Bill Janssen wrote: >

[sage-devel] updating sage-env LD_LIBRARY_PATH from spkg-install

I'm updating an old-style JModelica spkg to version 1.16, which just came out. On OS X, The CasADi subsystem now installs its dynamic libraries in a subdirectory of JModelica, a subdirectory which then has to be put on the LD_LIBRARY_PATH the Python interpreter is run with, as CasADi is package

[sage-devel] adventures with cdefs.h on OS X

Thought I'd share this in case anyone else blundered in the same way I just did... I installed 6.8 on an OS X Mavericks (10.9) system on which the "xcode-select --install" command had not been run. I ran "sage -upgrade" to upgrade it. I then tried to install a custom spkg, which failed in the

[sage-devel] Re: Problem building Sage after upgrading OS X 10.6.8 -> 10.9.1

I take it back. Apparently installing them from the Xcode app gives you the compilers, etc, but not the header files. Using xcode-select --install seems to yield both. Bill On Tuesday, September 15, 2015 at 4:50:47 PM UTC-7, Bill Janssen wrote: > > I've got this problem right now

[sage-devel] Re: Problem building Sage after upgrading OS X 10.6.8 -> 10.9.1

I've got this problem right now, with Sage 6.8, on 10.9. And I've run xcode-select --install from a terminal; it just outputs the line "xcode-select: note: install requested for command line developer tools" (which are already installed). Help! Bill On Wednesday, February 5, 2014 at 6:32:23

[sage-devel] Re: UTF-8 and old terminals (new startup banner)

It's hard to sufficiently emphasize how ugly this looks in an Emacs shell buffer. I use the Inconsolata font with emacs, and it doesn't have those characters (the dashes and corner characters), so Emacs goes to a different fixed-width font for them, and that font has a different width, so the

Re: [sage-devel] broken prompts in Emacs shell-mode

iveShell.colors = "NoColor" finally: curses.endwin() On Wednesday, September 25, 2013 7:52:54 AM UTC-7, Bill Janssen wrote: > > Better would be this: > > c = get_config() > > > try: > import curses > curses.initscr() > except: >

Re: [sage-devel] Re: How can an spkg extend the interactive Sage environment?

On Monday, September 30, 2013 11:50:36 PM UTC-7, Felix Salfelder wrote: > > On Mon, Sep 30, 2013 at 03:51:15PM -0700, Bill Janssen wrote: > > > However, I've also got to make sure that the environment variable > > > JMODELICA_HOME is set. Is there some way for an

[sage-devel] Re: How can an spkg extend the interactive Sage environment?

On Tuesday, October 1, 2013 1:39:42 AM UTC-7, Volker Braun wrote: > > Just patch the JModelica module to set the path on import. Requiring > global variables to point to your home dir is already so much bad practice > that I don't want to see the source code. > > Well, I hope you won't have to lo

[sage-devel] Re: How can an spkg extend the interactive Sage environment?

Hello? Anyone? On Monday, September 23, 2013 2:29:00 PM UTC-7, Bill Janssen wrote: > > I'm building JModelica for Sage. It installs into its own little private > directory (I'm using ${SAGE_LOCAL}/JModelica-1.11), including its Python > code. When I fire up the intera

Re: [sage-devel] broken prompts in Emacs shell-mode

Better would be this: c = get_config() try: import curses curses.initscr() except: pass else: try: if not curses.has_colors(): c.InteractiveShell.colors = "NoColor" finally: curses.endwin() This could also go into the regular Sage ipython startup

Re: [sage-devel] sage-env always sets LDFLAGS, which clobbers Numpy's distutils Fortran compiler support

On Tuesday, September 24, 2013 11:51:37 AM UTC-7, Felix Salfelder wrote: > > There's a difference between an empty value and "not defined", after > > all. > > there *is* a difference. in my experience there's nothing useful about > it. implicitly overriding (not appending!) flags from the envir

Re: [sage-devel] sage-env always sets LDFLAGS, which clobbers Numpy's distutils Fortran compiler support

hasn't set them that way. There's a difference between an empty value and "not defined", after all. Bill On Monday, September 23, 2013 11:19:43 PM UTC-7, Felix Salfelder wrote: > > On Mon, Sep 23, 2013 at 02:21:39PM -0700, Bill Janssen wrote: > > I was trying to

Re: [sage-devel] broken prompts in Emacs shell-mode

Thanks, Nils. That worked. Use "sage -ipython profile list" to find out where your profile is (it wasn't using ~/.ipython/, it was using ~/.sage/ipython-0.12/), then put the following lines into ~/.sage/ipython-0.12/profile_default/ipython_config.py: c = get_config() try: import curses

Re: [sage-devel] broken prompts in Emacs shell-mode

e's command line is ipython). > > William > > On Fri, Sep 20, 2013 at 10:54 AM, Bill Janssen > > > wrote: > > In an Emacs shell, Sage seems to be ignoring the TERM setting (dumb) and > > sending ANSI escape sequences to the terminal around the "

[sage-devel] Re: Parsing XML in Sage

I have an spkg for lxml (required for JModelica) and I intend to make it available in the near future. Bill On Tuesday, September 17, 2013 4:45:22 AM UTC-7, Nathann Cohen wrote: > > Hell everybody ! > > We have in Sage an interface with ISGCI [1], and most of the code it > contains amou

[sage-devel] How can an spkg extend the interactive Sage environment?

I'm building JModelica for Sage. It installs into its own little private directory (I'm using ${SAGE_LOCAL}/JModelica-1.11), including its Python code. When I fire up the interactive Sage prompt, I'd like it to be able to locate the JModelica Python modules. To do that, I need to integrate J

[sage-devel] sage-env always sets LDFLAGS, which clobbers Numpy's distutils Fortran compiler support

I was trying to compile the Python+Fortran Assimulo package on Sage (5.11) on OS X, and I couldn't figure out why the gfortran link step kept failing -- the correct linker flags for shared libraries weren't being used. Turns out that the "fcompiler" support in Numpy's distutils will *always* lo

[sage-devel] broken prompts in Emacs shell-mode

In an Emacs shell, Sage seems to be ignoring the TERM setting (dumb) and sending ANSI escape sequences to the terminal around the "sage:" prompt. [pippin:~] wjanssen% printenv TERM dumb [pippin:~] wjanssen% /local/sage-5.11/sage +---

[sage-devel] Re: talk about sage -i and sage -f in the developer's guide?

On Nov 15, 6:47 pm, William Stein wrote: > On Tue, Nov 15, 2011 at 5:46 PM, BillJanssen wrote: > >> One trivial thing you could do would be to build from source in /tmp/, > >> then just move your install to your home directory.  Sage supports > >> moving complete installs. > > > That's basically w

[sage-devel] Re: tentative PIL-1.1.7.p0.spkg

512, 512) L (512, 512) => L (512, 512) P (512, 512) => L (512, 512) Bill On Nov 22, 3:59 pm, John H Palmieri wrote: > On Tuesday, November 22, 2011 3:45:28 PM UTC-8, Bill Janssen wrote: > > > On Nov 22, 12:53 pm, John H Palmieri wrote: > > > So pil-1.1.6.p5 *is

[sage-devel] CPPFLAGS not preserved by sage-env

I'm guessing that CPPFLAGS should also be preserved by sage-env. Similar to CXXFLAGS and LDFLAGS, it's typically used to pass include options to the C preprocessor. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+

[sage-devel] Re: tentative PIL-1.1.7.p0.spkg

On Nov 22, 12:53 pm, John H Palmieri wrote: > So pil-1.1.6.p5 *is* the old one. pil-1.1.6.p4 is the old one. > Remove the "src" directory from that > one, replacing it with the new source.  Modify any patches as necessary, > along with the spkg-install, spkg-check, and SPKG.txt files, as I said

[sage-devel] Re: tentative PIL-1.1.7.p0.spkg

> You should build your new spkg by starting with the old one Except that the "old one" doesn't exist -- this is pil-1.1.7.p0, not pil-1.1.6.p5. Still not sure how to go about this -- an example (perhaps it's in the docs) would be helpful. -- To post to this group, send an email to sage-devel@g

[sage-devel] Re: MIME type for .spkg files?

> I'd suggest registering a real MIME type for it, something like > "application/vnd.sagemath-spkg". See http://www.iana.org/cgi-bin/mediatypes.pl. Bill -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr..

[sage-devel] Re: talk on Sage that I gave today

On Nov 22, 9:26 am, Bill Janssen wrote: > Nice graphic in there, William.  Page 8 in the PDF.  Just what I need > for a talk this afternoon.  Is it available as an image somwhere? Ah, got it. Pulled it out of the worksheet. Bill -- To post to this group, send an email to sage

[sage-devel] Re: tentative PIL-1.1.7.p0.spkg

On Nov 17, 5:07 pm, kcrisman wrote: > On Nov 17, 5:10 pm, Bill Janssen wrote: > > > OK, the libjpeg now builds in place. > > > I see that on my Ubuntu box, the spkg-check file isn't being run > > automatically.  Any ideas as to why that might be? > > Did you

[sage-devel] Re: tentative PIL-1.1.7.p0.spkg

OK, I'll look at that this long weekend. Bill On Nov 17, 2:07 pm, William Stein wrote: > On Thu, Nov 17, 2011 at 1:49 PM, Bill Janssen wrote: > >> Some issues with this spkg: > > >>  - The mercurial repository is completely missing. > > > Yes, it's

[sage-devel] Re: MIME type for .spkg files?

That would allow servers and browsers to agree on what they're passing around. It would also handle the case where it's maybe bzip2 one time and maybe tar the next time. Same for .sws, if that isn't already registered. Bill On Nov 18, 12:12 am, Jeroen Demeyer wrote: > On 2011-1

[sage-devel] Re: talk on Sage that I gave today

Nice graphic in there, William. Page 8 in the PDF. Just what I need for a talk this afternoon. Is it available as an image somwhere? Thanks. Bill On Nov 20, 12:05 am, William Stein wrote: > On Sat, Nov 19, 2011 at 11:50 PM, Thierry Dumont > > > > > > > > > > wrote: > > Le 20/11/2011 08:48,

[sage-devel] Re: tentative PIL-1.1.7.p0.spkg

OK, the libjpeg now builds in place. I see that on my Ubuntu box, the spkg-check file isn't being run automatically. Any ideas as to why that might be? Bill On Nov 17, 1:49 pm, Bill Janssen wrote: > >  - You shouldn't build libjpeg in /tmp/..., but probably in a subdirectory

[sage-devel] Re: tentative PIL-1.1.7.p0.spkg

> Some issues with this spkg: > >  - The mercurial repository is completely missing. Yes, it's not a patch to the Sage sources, so there's no Mercurial stuff as there would be if it were. >  - There are lots of backup files around ("SPKG.txt~", etc.). I've put up a new version which should fix t

[sage-devel] MIME type for .spkg files?

Is there a MIME type for .spkg files? -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sa

[sage-devel] tentative PIL-1.1.7.p0.spkg

I've put up my first try at a PIL 1.1.7 spkg at . Please tell me what I did wrong :-). I've tried this on OS X Leopard, and on Ubuntu64 10.04. This version includes a statically linked libjpeg, *doesn't* rummage around on the local machine trying to

[sage-devel] Re: integrating spkg-check and spkg-install?

nica library at http://www.leptonica.org/. In that case, there might be some reason to have both PIL and Leptonica use the same libjpeg. Bill On Nov 15, 11:58 pm, William Stein wrote: > On Tue, Nov 15, 2011 at 10:52 PM, Bill Janssen wrote: > >> > Again, installing libjpeg.dylib and/or libpng

[sage-devel] Re: integrating spkg-check and spkg-install?

> > Again, installing libjpeg.dylib and/or libpng.dylib into $SAGE_LOCAL/ > > lib has bad side effects on OS X, due to the use of DYLD_LIBRARY_PATH > > in the Sage framework overall.  So, maybe make it an optional spkg, > > but having it as a required or standard spkg would be bad. > > We already i

[sage-devel] question about patch level in spkg file names

I'm a bit unclear on what the value of patchlevel should be in my new PIL package. I carry over the two patches from pil-1.1.6.p4, but it's a new PIL version, so I'm thinking pil-1.1.7.p0. Would that be correct? -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscri

[sage-devel] Re: integrating spkg-check and spkg-install?

On Nov 15, 7:01 pm, Bill Janssen wrote: > Are there any spkgs elsewhere in Sage which require libjpeg?  If so, > what version of it?  I know that scipy has an imread function; anyone > know what does it do for JPEG? I looked it up; it uses PIL. -- To post to this group, send an emai

[sage-devel] Re: integrating spkg-check and spkg-install?

> >> On Tue, Nov 15, 2011 at 2:10 PM, Bill Janssen > >> wrote: > >> > On Nov 15, 1:02 pm, "Georg S. Weber" > >> > wrote: > >> >> Some people buidling > >> >> Sage from source do *want* a libjpeg on their system to

[sage-devel] Re: integrating spkg-check and spkg-install?

On Nov 15, 12:29 pm, "Georg S. Weber" wrote: > it installs quite some files e.g. under $SAGE_LOCAL/bin/ which > no Sage user needs (or even knows of, I guess), thus "polluting" the > tree without having cleanup mechansims at hand. I've just reviewed the scripts in Imaging-1.1.7/Scripts/, and I se

[sage-devel] Re: talk about sage -i and sage -f in the developer's guide?

> One trivial thing you could do would be to build from source in /tmp/, > then just move your install to your home directory.  Sage supports > moving complete installs. That's basically what I am doing. Still breaks because it's trying to do stuff in ~janssen/.sage/ as part of the build. I can

[sage-devel] Re: why unpack the source packages?

The only real advantages of keeping the upstream sources packaged is that (1) you can know what's in them, check md5sums, etc., and (2) there's less chance of introducing hard-to-find errors by fat- fingering a particular unpacked source file. But I'm happy to unpack, too. On Nov 15, 2:01 pm, Maa

[sage-devel] Re: talk about sage -i and sage -f in the developer's guide?

On Nov 15, 1:29 pm, "Georg S. Weber" wrote: > On 15 Nov., 18:51, Bill Janssen wrote: > > > It would be nice if the developer's guide talked about using sage -i > > and sage -f to test new spkg's.  In the section about building spkg's, > > pe

[sage-devel] Re: integrating spkg-check and spkg-install?

On Nov 15, 1:02 pm, "Georg S. Weber" wrote: > Some people buidling > Sage from source do *want* a libjpeg on their system to be taken into > accont by their PIL in Sage! Really? Do you have user studies or other evidence of that I could look at on that? It's surprising to me; I'd think that one

[sage-devel] Re: why unpack the source packages?

Fine with me. But if the src directory is allowed to be a modified version of upstream, why not just integrate the Sage-specific patches directly into the sources, too? Bill On Nov 15, 11:29 am, William Stein wrote: > On Tue, Nov 15, 2011 at 11:13 AM, Bill Janssen wrote: > > I'm

[sage-devel] Re: integrating spkg-check and spkg-install?

ribution. I've decided to run the PIL selftest.py after building PIL, but before installing it. I'll write some other tests to be run by spkg-check which will specifically test the integration with Sage. Bill On Nov 15, 12:29 pm, "Georg S. Weber" wrote: > On 15 Nov.,

[sage-devel] why unpack the source packages?

I'm a bit unclear as to why third-party source packages are unpacked in an spkg? Since the patching protocol is very strict, would it make sense for me to include Imaging-1.1.7.tar in the "src" directory of the spkg, instead of unpacking it into raw files? -- To post to this group, send an email

[sage-devel] integrating spkg-check and spkg-install?

I'm building a new spkg for PIL 1.1.7. I'd like to build PIL, then run its test suite, then if that passes, install it. Should I just do all of that in spkg-install, or should I run the test suite in spkg-check? If I install it before I test it, that means that broken code could overwrite workin

[sage-devel] Re: example of sage-check file?

Sorry, I mean "spkg-check". Bill On Nov 15, 10:40 am, Bill Janssen wrote: > Can someone please point me to an example of a sage-check file?  I > don't see any explanation in the developer docs. -- To post to this group, send an email to sage-devel@googlegroups.com To

[sage-devel] example of sage-check file?

Can someone please point me to an example of a sage-check file? I don't see any explanation in the developer docs. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, vi

[sage-devel] talk about sage -i and sage -f in the developer's guide?

It would be nice if the developer's guide talked about using sage -i and sage -f to test new spkg's. In the section about building spkg's, perhaps. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@goog