Re: [sage-devel] removing pickles for old k-Schur implementation

2014-01-12 Thread Anne Schilling
Hi! I agree with Travis that we should just remove the jar, given that the old k-Schurs were deprecated for over a year! Best, Anne On Sun, Jan 12, 2014 at 10:44 PM, Travis Scrimshaw wrote: > Hey everyone, >This is not easy as I have been trying to fix this for a few hours (but > there is

Re: [sage-devel] removing pickles for old k-Schur implementation

2014-01-12 Thread Travis Scrimshaw
Hey everyone, This is not easy as I have been trying to fix this for a few hours (but there is always the possibility that I'm doing something wrong). Here's what I believe to be going on. 1 - The unreduce from UniqueRepresentation is overriding the __setstate__, which is then calling the __

[sage-devel] Re: Sage build system

2014-01-12 Thread Volker Braun
Another bullet point, related to being able to package and store the installed files: - downgrades should work and be fast, so you can easily go back to an old ticket -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this gro

Re: [sage-devel] Sage 6.x documentation

2014-01-12 Thread Harald Schilly
On Mon, Jan 13, 2014 at 6:26 AM, Minh Nguyen wrote: > I think the transition to git has messed up my > build scripts. ... > Anyway, someone updated the documentation (thanks!). Sorry for the > miscommunication that resulted in the delay. no problem, everyone needs a break sometimes ;-) I was

Re: [sage-devel] Re: Python as build-time dependency

2014-01-12 Thread Volker Braun
follow-up discussion on the build system please into this thread: https://groups.google.com/d/msg/sage-devel/WmykUtM4Gi0/qm6tH5i8b8UJ -- 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 i

[sage-devel] Sage build system

2014-01-12 Thread Volker Braun
[top-posted reply to start an appropriately-named thread] On Monday, January 13, 2014 12:26:30 AM UTC-5, William wrote: > I don't think this is off topic and I think you make a very good > point. Relocation (as I defined it) is not the goal. The goal is to > build user-installable binaries. I

[sage-devel] Sage build system

2014-01-12 Thread Volker Braun
[changed subject to end up top-posted] On Monday, January 13, 2014 12:26:30 AM UTC-5, William wrote: > > I don't think this is off topic and I think you make a very good > point. Relocation (as I defined it) is not the goal. The goal is to > build user-installable binaries. If what you sugges

Re: [sage-devel] Re: Python as build-time dependency

2014-01-12 Thread William Stein
On Sun, Jan 12, 2014 at 9:15 PM, Volker Braun wrote: > At the risk of veering even further off-topic, I would like to give up "tree > relocation" as it is currently defined. Its cumbersome (need to check that > we haven't been moved all the time) and insecure. > > For relocatable binaries, we buil

Re: [sage-devel] Sage 6.x documentation

2014-01-12 Thread Minh Nguyen
Hi, On Sun, Dec 22, 2013 at 7:40 PM, Marc Mezzarobba wrote: > As noticed by Paul Zimmermann, http://www.sagemath.org/doc/ still points > to the documentation of Sage 5.13. For regular manuals, it shouldn't > make any difference until sage-6.1 is released, however the developer > guide is out of d

Re: [sage-devel] Re: Python as build-time dependency

2014-01-12 Thread Volker Braun
At the risk of veering even further off-topic, I would like to give up "tree relocation" as it is currently defined. Its cumbersome (need to check that we haven't been moved all the time) and insecure. For relocatable binaries, we build with / rewrite rpaths to be relative and make all libtool

Re: [sage-devel] Re: Python as build-time dependency

2014-01-12 Thread William Stein
On Sun, Jan 12, 2014 at 8:09 PM, Francois Bissey wrote: > Relocation. Technically possible. In practise hard to achieve as it involves > rewriting > runpath inside binaries, this is highly OS dependent. The prefix solves > Volker's > LD_LIBRARY_PATH problem at the cost of relocation. Other gain

Re: [sage-devel] Re: Python as build-time dependency

2014-01-12 Thread Volker Braun
On Sunday, January 12, 2014 11:09:23 PM UTC-5, François wrote: > > OS X support. Almost 3 years ago with Georg we tackled it and I had sage > build > in a 32bit prefix on 10.5.8 up to sage 5.9 I think. There are a number of > prefix that > degraded that state. That is what I meant by "automat

RE: [sage-devel] Re: Python as build-time dependency

2014-01-12 Thread Francois Bissey
I should have invited myself to the conversation earlier I guess. I usually avoid those discussion because I could be seen as coming with a political agenda. Technically I don't really care what sage does so long as it doesn't get in the way of what I am doing with regards to gentoo/prefix. Whet

Re: [sage-devel] removing pickles for old k-Schur implementation

2014-01-12 Thread Andrew
Hi Anne, Have you tried writing a custom __setstate__ method for the kSchur functions? This should be all that is necessary. I ran into a similar problem when I moved Partition into the category framework and all that was required was def __setstate__(self, state): if isinstance(state,

Re: [sage-devel] Re: Python as build-time dependency

2014-01-12 Thread Michael Orlitzky
On 01/12/2014 03:51 PM, R. Andrew Ohana wrote: > I'm a fan of gentoo's package manager specification (PMS) [1], however > the only package manager that is fully compliant is portage, which I > don't think is appropriate for sage. In particular: Keep in mind that the alternative is a bunch of hand-

Re: [sage-devel] Re: Python as build-time dependency

2014-01-12 Thread R. Andrew Ohana
I'm a fan of gentoo's package manager specification (PMS) [1], however the only package manager that is fully compliant is portage, which I don't think is appropriate for sage. In particular: 1. It requires a noticeably bigger bootstrapping of the world. Lmonade reduces this to only ~20 more packa

Re: [sage-devel] Re: Python as build-time dependency

2014-01-12 Thread Felix Salfelder
On Sun, Jan 12, 2014 at 01:09:42PM -0500, Michael Orlitzky wrote: > Prefix is designed to run as an ordinary user on non-gentoo systems. If > you're on gentoo, you don't need it (unless you don't have root). Plenty > of us have been able to get it working, so if we made a concerted > effort, I'm su

Re: [sage-devel] Re: Python as build-time dependency

2014-01-12 Thread Volker Braun
On Sunday, January 12, 2014 8:09:42 AM UTC-10, Michael Orlitzky wrote: > > > lmnd currently does not work on OSX and other exotic platforms. > Prefix works on OSX, so whatever's wrong is fixable. I'm sure your help would be appreciated at lmona.de. We'll be happy to consider it when it is ready

Re: [sage-devel] Re: Python as build-time dependency

2014-01-12 Thread Michael Orlitzky
On 01/12/2014 12:03 PM, Volker Braun wrote: > On Sunday, January 12, 2014 6:41:21 AM UTC-10, Michael Orlitzky wrote: > > At this point I must conjure the semi-regular reminder that > "cross-platform homebrew" already exists in the form of Gentoo Prefix. > > > We are aware of gentoo prefi

Re: [sage-devel] Re: Python as build-time dependency

2014-01-12 Thread Volker Braun
On Sunday, January 12, 2014 6:41:21 AM UTC-10, Michael Orlitzky wrote: > > At this point I must conjure the semi-regular reminder that > "cross-platform homebrew" already exists in the form of Gentoo Prefix. > We are aware of gentoo prefix and lmnd. lmnd currently does not work on OSX and othe

Re: [sage-devel] Re: Python as build-time dependency

2014-01-12 Thread Michael Orlitzky
On 01/12/2014 04:16 AM, Javier López Peña wrote: > On Sunday, January 12, 2014 2:20:03 AM UTC, William wrote: > > Thanks for reminding people of conda. One issue is that Sage's build > system is far more than just for installing Python package -- it's > much, much more (e.g., Gap, Si

Re: [sage-devel] Re: Python as build-time dependency

2014-01-12 Thread Javier López Peña
On Sunday, January 12, 2014 2:20:03 AM UTC, William wrote: > > Thanks for reminding people of conda. One issue is that Sage's build > system is far more than just for installing Python package -- it's > much, much more (e.g., Gap, Singular, etc.). > conda started off as a python package manag