On Friday, June 3, 2016, Samuel Lelievre wrote:
>
>
> Le jeudi 2 juin 2016 22:33:45 UTC+2, Volker Braun a écrit :
>>
>> I'm guessing that this won't fly with upstream ;-)
>>
>> Is it really faster? A new __unary_div__ method everywhere? Is it really
>> faster than special-casing the 1/x case in _
On Thu, Jun 2, 2016 at 11:01 PM, Jori Mäntysalo wrote:
> Why do we have cached results?
>
> Beginners do something like
>
> for x in small_list:
> if x in SimpleThing(42).list():
> echo("Found!", x)
>
> Advanced users should know how to do
>
> temp = ComplicatedThing(10^6).list()
> mat
On Thu, Jun 2, 2016 at 9:45 PM, Kwankyu Lee wrote:
>> Suppose that our object X has a basis consisting of four 2x2 matrices,
>> in some abstract sense. Then your
>>
>>X.list()
>>
>> might very well return a tuple of four *mutable* 2x2 matrices. Then
>> this X.tuple() is still very much muta
On Thu, Jun 2, 2016 at 1:33 PM, Volker Braun wrote:
> I'm guessing that this won't fly with upstream ;-)
>
> Is it really faster? A new __unary_div__ method everywhere? Is it really
> faster than special-casing the 1/x case in __div__?
According to my unscientific benchmark just now there seems
On Thu, Jun 2, 2016 at 1:39 PM, Volker Braun wrote:
> On Thursday, June 2, 2016 at 5:34:49 PM UTC+2, William wrote:
>>
>> (1) No matter your grammar argument about deficiencies in the
>> technical language, it's a fact that the majority of English speakers
>> is going to consider this confusing.
On Thu, Jun 2, 2016 at 1:46 AM, Volker Braun wrote:
> No, generally method names are verbs and class names are nouns. There is no
> verb for "making a tuple" which is a bit of a deficiency in the English
> language if anything; But all those linguistic details pale in comparison to
> the glaring h
Hi,
Obviously I screwed up and just assumed, as a mathematician, that a
method called
__invert__
would be for computing the inverse of something.There is no sense
in which the bitwise version of that is the mathematical inverse of
an *integer*, so I didn't even consider that possibility.
On Mon, May 30, 2016 at 9:47 AM, Jori Mäntysalo wrote:
> On Mon, 30 May 2016, Erik Bray wrote:
>
>>> Imho many sage modules have grown too long, including but not limited to
>>> some 20kloc monsters. +1 to splitting things up!
>>
>>
>> Yikes! I'm not sure I've even run into any of those yet. 20k
On Mon, May 30, 2016 at 9:22 AM, Erik Bray wrote:
> Hi all,
>
> I recently needed to dive into the sage_setup.autogen.interpreters
> module in order to make some small changes.
Quick link:
https://github.com/sagemath/sage/blob/master/src/sage_setup/autogen/interpreters.py
It's the fast_callab
On Sun, May 29, 2016 at 12:22 AM, rjf wrote:
>
>
> On Friday, May 27, 2016 at 10:34:38 AM UTC-7, William wrote:
>>
>> On Fri, May 27, 2016 at 10:30 AM, rjf wrote:
>> > So you should claim authorship and copyright, and then declare that
>> > others
>> > may
>> > use it under whatever restrictions
On Fri, May 27, 2016 at 10:30 AM, rjf wrote:
> So you should claim authorship and copyright, and then declare that others
> may
> use it under whatever restrictions you determine. Personally, I find the
> MIT or
> Berkeley licenses much better than GPL, since they let anyone use the code
> for an
this post [1] which is about sympy moving to be "python3
only"...
[1] https://news.ycombinator.com/item?id=11738470
On Tue, May 24, 2016 at 8:53 PM, Fernando Perez wrote:
>
> On Tue, May 24, 2016 at 1:56 PM, William Stein wrote:
>>
>> We need a real strategy for migr
Hi,
I've been thinking more, and I'm really disturbed by this piecemeal
approach to getting Python 3, as least as far as it impacts *users*
(for developers it is great).
As mentioned before, I've been writing tons of code using Python 3 for
the last two weeks. There are *many* subtle ways in wh
uot; is used.
> 3) After that, remove support for "print a" completely.
>
> Best,
> Johan
I support your proposal above, with X=1. I don't want to have the
print statement forever.
-- William
>
>
>
> William Stein writes:
>
>> Breaking "print
On Tue, May 24, 2016 at 11:20 AM, Nils Bruin wrote:
> On Tuesday, May 24, 2016 at 10:21:34 AM UTC-7, William wrote:
>>
>> Breaking "print a" will cause a truly epic level of pain to our users for
>> no real gain... So much so that probably no matter what is decided here I
>> would fork sage to ad
Breaking "print a" will cause a truly epic level of pain to our users for
no real gain... So much so that probably no matter what is decided here I
would fork sage to add handling this to the pre-processor for sage on SMC.
I'm here from endless users (eg each year at the sage booth) about minor
de
On Mon, May 23, 2016 at 1:47 AM, John Cremona wrote:
> Are we not allowed to use
>
> print("x = %s" % x)
>
> any more?
It works fine in python3.
$ python3
Python 3.5.1+ (default, Mar 30 2016, 22:46:26)
[GCC 5.3.1 20160330] on linux
Type "help", "copyright", "credits" or "license" for more inform
On Sun, May 22, 2016 at 3:16 AM, Volker Braun wrote:
> PS: I'd be more than happy to get rid of the special casing for
> pretty_print, there is no reason to list iterators beyond backward
> compatibility for a pretty weird use case.
+1. There are many changes that should be made to show, and it'
On Fri, May 20, 2016 at 3:32 PM, D. S. McNeil wrote:
> On the subject of 3, for anyone who hasn't been following, a number of teams
> on the science stack have thought about Aaron's argument and are making
> plans:
>
> https://python3statement.github.io/
>
Thanks. To anybody else that clicks the
Fri, May 20, 2016 at 1:05 PM, Jeroen Demeyer wrote:
> On 2016-05-20 20:04, William Stein wrote:
>>
>> How much might it cost to get Sage to work with Python3?
>
>
> That's very difficult to say... many of the easy parts have been done. But
> we haven't really loo
Hi Sage-Devel,
I just spent the week teaching numpy and matplotlib in the context of
Sage. Walking around and watching why/how students got frustrated on
certain homework problems revealed one way we could improve Sage,
which would make Sage much more useful and natural overall.It
seems to me
Hi,
Somebody with possibly substantial grant funds asked me today: "How
much might it cost to get Sage to work with Python3?"
I don't know. Anybody have any thoughts? Is there anybody reading
this who wishes they could spend several months getting Sage to fully
work with Python3 instead of t
31 return master_fd, slave_fd
>
> /usr/lib/sagemath/local/lib/python/pty.pyc in _open_terminal()
> 68 continue
> 69 return (fd, '/dev/tty' + x + y)
> ---> 70 raise os.error, 'out of pty devices'
> 71
>
On Wednesday, May 18, 2016, Brian Beavers wrote:
> I've discovered why the notebook server (and administrative pages within)
> loads but notebooks do not load: WSL does not yet suppot pty. When I try to
> create a worksheet, back in the terminal Sage throws an error that it is
> out of pty instan
What you did gets discussed/advertised at the beginning of this podcast:
https://talkpython.fm/episodes/show/59/sagemath-open-source-is-ready-to-compete-in-the-classroom
On Tue, May 10, 2016 at 4:36 PM, Brian Beavers wrote:
> I don't know if any of you are Windows Insiders and are following th
https://talkpython.fm/episodes/show/59/sagemath-open-source-is-ready-to-compete-in-the-classroom
--
William (http://wstein.org)
--
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, sen
I forwarded this thread to him.
On Tue, May 17, 2016 at 6:28 AM, Travis Scrimshaw wrote:
> Has anyone asked Greg Bard if he was going?
>
> Best,
> Travis
>
>
>
> On Monday, May 16, 2016 at 9:49:05 PM UTC-5, kcrisman wrote:
>>
>>
>> On Saturday, May 14, 2016 at 12:05:24 PM UTC-4, wstein wrote:
>>>
On Sunday, May 8, 2016, Thierry wrote:
> On Sun, May 08, 2016 at 02:53:58PM -0700, William Stein wrote:
> > On Sunday, May 8, 2016, Thierry > wrote:
> >
> > > Hi,
> > >
> > > i have to witness that for Sage Debian Live, i currently have to fork
>
hat with binary-pkg to get a relocatable
> customized build ?
>
> Ciao,
> Thierry
>
>
>
>
>
> On Sun, May 08, 2016 at 12:00:41PM -0700, William Stein wrote:
> > On Sunday, May 8, 2016, Volker Braun > wrote:
> >
> > > On Sunday, May 8, 2016 at 6:1
On Sunday, May 8, 2016, Volker Braun wrote:
> On Sunday, May 8, 2016 at 6:19:43 AM UTC+2, William wrote:
>>
>> which is 593M.
>>
>
> Sounds a bit too small, the buildbot binaries are always about twice that.
>
Ok that's good to know and explains why the binaries didn't work. I'll try
building
On Sun, May 8, 2016 at 1:34 AM, Volker Braun wrote:
> On Sunday, May 8, 2016 at 6:54:38 AM UTC+2, William wrote:
>>
>> time rsync -axH /projects/sage/sage-dev/ sage-dev/
>
>
> Thats fine. The only caveat is that rpaths are still pointing to the source.
> Therefore
> a) the copy stops working if y
On Sat, May 7, 2016 at 12:18 PM, Volker Braun wrote:
> You can set it yourself in the environment after moving Sage, this may work
> with the aforementioned caveats about conflicts with system libraries. And
> change SAGE_LOCAL/lib/sage-current-location.txt to avoid the relocation
> error message.
over the yaml file but couldn't figure it out.
>>
>>
>>
>> I am sad that I can't copy existing sage installs, and I'm now even
>> sadder that I can't type "./sage -bdist" anymore. Two of the most
>> important things for making sag
On Sat, May 7, 2016 at 11:32 AM, Volker Braun wrote:
> On Saturday, May 7, 2016 at 5:46:20 PM UTC+2, William wrote:
>>
>> I read that github page, but I don't know what binary-pkg actually
>> does.
>
>
> It compiles Sage in a long directory path.
>
>>
>> For context, I used to (1) build a copy of
ow do you specify which sage install it
>> packages? Yes, I read over the yaml file but couldn't figure it out.
>>
>>
>>
>> I am sad that I can't copy existing sage installs, and I'm now even
>> sadder that I can't type "./sage -bdist&qu
gs for making sage dev easy for people are gone. If I
had the time, I would make a fork of Sage that restored exactly this
behavior then always merge it into sage...
William
>
>
>
> On Saturday, May 7, 2016 at 2:05:00 AM UTC+2, William Stein wrote:
>>
>> Either my bu
On Thu, May 5, 2016 at 5:46 AM, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
> Hello,
>
> I made yesterday at Sage days 73 a presentation using the Jupyter
> notebook. I gathered some of the desirable improvements needed before
> the transition
>
> * tab completion with jokers not supported
On Wed, May 4, 2016 at 5:17 PM, Luca De Feo wrote:
>> Can you also ask him about the license?
>
>
> You can read here http://www-polsys.lip6.fr/~jcf/FGb/Maple/tutorial-fgb.pdf
> that "FGb is freely distributed for academic use only". The question has
> been asked often: publishing the sources is o
On Wed, May 4, 2016 at 1:07 PM, Johan S. R. Nielsen
wrote:
> Michael Orlitzky writes:
>> I have a matrix m... how come,
>>
>> * m.rank gives me bullshit
>> * m.rank() works
>> * m.T() crashes
>> * m.T works?
>
> This is in my mind the most compelling reason to phase out properties in
> Sag
It (column 2 of [1]) says this should work (see [2] below also), but it doesn't:
A = matrix(QQ, [[1,2],[3,4]])
f(x) = x^3 - 2*x + 1
f(A) # FAIL -- this is maybe a bug though (the quickref says it should work)
Making f an actual polynomial (not symbolic) works.
[1]
https://wiki.sagemath.org/quic
On Wed, May 4, 2016 at 7:18 AM, Erik Bray wrote:
> On Wed, May 4, 2016 at 4:06 PM, William Stein wrote:
>> On Wed, May 4, 2016 at 6:13 AM, Erik Bray wrote:
>> [...]
>>> Anyways we can agree to disagree on this, and even within the Python
>>> community you'
On Wed, May 4, 2016 at 6:13 AM, Erik Bray wrote:
[...]
> Anyways we can agree to disagree on this, and even within the Python
> community you'll find different opinions, especially regarding things
> like how much calculation should be done in the getter of a property,
> or what kinds of exception
On Monday, May 2, 2016, Michael Orlitzky wrote:
> On 05/02/2016 06:07 AM, Erik Bray wrote:
> > On Mon, May 2, 2016 at 10:35 AM, Jeroen Demeyer > wrote:
> >> My vote:
> >>
> >>> [X] Phase out properties which perform any non-trivial computation
> >>
> >>
> >> In certain cases, properties might be
This ticket may be relevant: http://trac.sagemath.org/ticket/13093
On Sun, May 1, 2016 at 9:57 AM, Hao Chen wrote:
> Hi, this might be stupid, but I was wondering if integrating a newform
> against an arbitrary Manin symbol
> is implemented in Sage now? I have in mind something like
>
> sage: m =
For the record, a third option is to attempt to tab complete for 3
seconds (say), and interrupt if the result can't be computed that
quickly.
But I think Volker's answer is sufficient for now.
William
On Fri, Apr 29, 2016 at 7:12 AM, Volker Braun wrote:
> IPython (and hence Sage) can do tab com
On Wed, Apr 27, 2016 at 7:09 AM, Kwankyu Lee wrote:
> This discussion is hardening the terms: Sage core and external packages. But
> from the point of view of the people developing the would-be external
> packages, the official term would better be
>
> Sage extension,
> Sage library extension,
> S
Hi,
A few years ago Keith Clawson worked for me/UW partly on maintaining
sage development infrastructure. He bought the domain sagedev.org
somewhere, and set it up for some purposes. I have access to the
route 53 DNS entries for the domain, and was going to delete it, since
he has long stopped
+1. I've been really hoping for any movement toward py3. Thanks!!
On Thursday, April 21, 2016, Volker Braun wrote:
> +1
>
> As others mentioned, there are at least 3 similar cases where future
> imports should be used:
>
> * The sage library (this thread)
> * The preparser
> * Doctest runner
>
Similarly remove M Patel for similar reasons.
On Thursday, April 21, 2016, mmarco wrote:
> Ok, so that is a good reason to delete those packages, unless somebody
> steps in as a maintainer.
>
> El jueves, 21 de abril de 2016, 11:07:11 (UTC+2), John Cremona escribió:
>>
>> On 21 April 2016 at 09:
Hi,
How much disk space is it supposed to take to download and build Sage
from source these days...?
William
--
William (http://wstein.org)
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving email
Hi,
My one remark for this thread is that it is relatively easy to make
something pip installable. For example, somebody recently complained
that pygsl was only available via downloading files from sourceforce,
so I (very) easily made
https://pypi.python.org/pypi?:action=display&name=pygsl&ve
On Mon, Apr 18, 2016 at 6:03 PM, Kwankyu Lee wrote:
> Which one is correct?
>
> (1) "This is based on code by A and B"
> (2) "This is based on codes by A and B"
> (3) "This is based on the codes by A and B"
>
> I am just curious. I am not a native English speaker.
In American, (1) is correct.
I
On Sun, Apr 17, 2016 at 8:27 AM, Dima Pasechnik wrote:
>
>
> On Sunday, April 17, 2016 at 4:20:42 PM UTC+1, Dima Pasechnik wrote:
>>
>>
>>
>> On Sunday, April 17, 2016 at 4:15:12 PM UTC+1, William wrote:
>>>
>>> Dima:
>>> > sorry, William, I don't see what you mean.
>>> [...]
>>> > 2) Putting data
Dima:
> sorry, William, I don't see what you mean.
[...]
> 2) Putting data on your computer does not equal to installing crud on your
> computer, although people wearing tinfoil hats
> might disagree.
They do disagree. And they are right.
--
William (http://wstein.org)
--
You received this me
On Sunday, April 17, 2016, Dima Pasechnik wrote:
>
>
> On Sunday, April 17, 2016 at 2:14:09 AM UTC+1, kcrisman wrote:
>>
>>
>>
>>>
(1) Providing a source tarball from which one can build Sage without
internet access is a basic requirement from a company that provides
some funding f
On Sat, Apr 16, 2016 at 2:46 PM, paulmasson wrote:
> Are all of these repositories used merely for hosting files?
Yes, this one: https://github.com/sagemath/website
>
> Does any active development take place purely on Github, i.e., outside of
> the Trac system?
>
> --
> You received this message
On Sat, Apr 16, 2016 at 8:54 AM, Dima Pasechnik wrote:
>
>
> On Saturday, April 16, 2016 at 4:34:30 PM UTC+1, Jeroen Demeyer wrote:
>>
>> On 2016-04-16 17:29, Dima Pasechnik wrote:
>> > Any other largish Python-based project that does these kind of tarballs
>> > these days?
>>
>> The Sage source
On Fri, Apr 15, 2016 at 4:49 PM, mmarco wrote:
> That is a question that we have to address: if we allow this kind of
> external packages
It is not up to us to decide. Nobody can stop people from making
external Python packages that depend on Sage. Absolutely anybody with
any skills could read
On Fri, Apr 15, 2016 at 1:06 PM, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
[..]
> You can also do this "out of the distro" using "pip".
>
> If you want to add user packages you need to setup environment variables
> PYTONPATH and/or PYTHONHOME [1] pointing to the appropriate directory.
>
On Fri, Apr 15, 2016 at 2:59 PM, Volker Braun wrote:
> Is there really going to be much activity on SageNB in the future? I
> appreciate that you fixed the packaging and dependency nightmare, but it
> seems that we are now (i.e. after #14840) at the point where we are likely
> to just wait and eve
On Fri, Apr 15, 2016 at 9:21 AM, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
> +1 (both for Jeroen proposition and John intervention)
>
> Indeed the -1 from William is just about a general philosophy that he will
> be of no help implementing.
I would like to hear what Volker thinks. I wo
-1 to moving the sagenb code back into the sage git repo. The day I
removed sagenb from the sage git repo was, for me, a very happy day.
But +1 for having people who care have the ability to push to the repo
on github and generally take over maintenance.
On Fri, Apr 15, 2016 at 7:13 AM, William
On Fri, Apr 15, 2016 at 7:05 AM, Dima Pasechnik wrote:
> Who does have commit access to https://github.com/sagemath/sagenb ?
> (not me).
> Karl is obviously overwhelmed with other things.
> If I had this access I could have reviewed at least some of these tickets
> (we still would want to keep ups
On Thu, Apr 14, 2016 at 6:38 PM, Kwankyu Lee wrote:
>
>
> On Friday, April 15, 2016 at 6:54:44 AM UTC+9, kcrisman wrote:
>>
>>
>>> > These packages are nearly impossible to found from the sagemath
>>> > website!
>>>
>>> Chris -- who wrote abelfunctions -- is a Univ of Wash grad student I
>>> know.
On Thu, Apr 14, 2016 at 12:41 PM, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
> On 14/04/16 16:32, William Stein wrote:
>>
>> On Thu, Apr 14, 2016 at 12:23 PM, Jeroen Demeyer
>> wrote:
>>>
>>> On 2016-04-14 20:35, William Stein wrote:
&g
On Thu, Apr 14, 2016 at 12:23 PM, Jeroen Demeyer wrote:
> On 2016-04-14 20:35, William Stein wrote:
>>
>> However I'm only now starting to complain loudly and
>> repeatedly just because I'm seeing such a huge wasted opportunity.
>
>
> Instead of compla
On Thursday, April 14, 2016, Francesco Biscani wrote:
> On 14 April 2016 at 15:51, Erik Bray > wrote:
>
>> I disagree that Sage is all that special. Or at least, I don't
>> believe there's any need for it to be, whether or not it is currently.
>>
>
> If the past is any indication, you will find
On Tuesday, April 12, 2016, Volker Braun wrote:
> On Tuesday, April 12, 2016 at 9:59:40 PM UTC+2, William wrote:
>>
>> We might also be able to make it available
>> outside Sage, and it could suddenly be of huge value to the Python
>> world.
>
>
> In other words: If we change our mission to "the
On Tue, Apr 12, 2016 at 12:50 PM, kcrisman wrote:
>> It doesn't mean that the normal visible
>> public API of Sage changes
>> at all. Why do you think otherwise?
>
>
> Well, reading this thread made me think that. Because I don't see how we
> enforce all those "other pieces" working nicely tog
On Tue, Apr 12, 2016 at 7:11 AM, kcrisman wrote:
> This has been an interesting thread. In the end, I think that some (or a
> lot) of Sage's attractiveness to end users goes away if it becomes a bunch
> of possibly-updated packages that might or might not work with a current
> version of Sage. I
On Sat, Apr 9, 2016 at 2:49 AM, Dima Pasechnik wrote:
>> SMC does inform my frustration with the current limitations on Sage
>> development.
>
> I am afraid we see a conflict of interest here.
> It is in interests of SMC that Sage is very, very stable... Frozen.
I want Sage to be (massively) eas
On Friday, April 8, 2016, Dima Pasechnik wrote:
>
>
> On Friday, April 8, 2016 at 7:40:02 PM UTC+1, William wrote:
>>
>>
>>
>> On Friday, April 8, 2016, Volker Braun wrote:
>>
>>> On Friday, April 8, 2016 at 6:43:46 PM UTC+2, William wrote:
this "one other problem of Sage is that it do
On Friday, April 8, 2016, Volker Braun wrote:
> On Friday, April 8, 2016 at 6:43:46 PM UTC+2, William wrote:
>>
>> this "one other problem of Sage is that it does not define
>> clearly what's the public API and what's internal.
>
>
> IMHO thats just not true; What you get on the commandline (i.e.
On Fri, Apr 8, 2016 at 1:00 AM, Volker Braun wrote:
> On Friday, April 8, 2016 at 2:36:23 AM UTC+2, William wrote:
>>>
>>> Whats wrong with the obvious solution: make it a Python package
>>> (basically add setup.py) and then "sage -pip install
>>> https://github.com/vbraun/awesomepackage.git";. Cl
On Fri, Apr 8, 2016 at 9:33 AM, Luca De Feo wrote:
>> How often do you feel that changes in Sage breaks your code?
>
> Looking at my log (this project
> https://github.com/defeo/ss-isogeny-software)
>
> - Sage 6.2: module renamed in Pari/GP interface (without deprecation, as far
> as I recall)
> -
On Thursday, April 7, 2016, Volker Braun wrote:
> On Friday, April 8, 2016 at 1:26:07 AM UTC+2, William wrote:
>>
>> This thread is first and foremost about reducing the friction involved in
>> making code that depends on the Sage distribution available to the world.
>>
>
> Whats wrong with the o
On Thursday, April 7, 2016, Volker Braun wrote:
> On Friday, April 8, 2016 at 12:19:57 AM UTC+2, William wrote:
>>
>> > You mean like in the Linux kernel, which uses a single monolithic git
>> > repository?
>> I think you are being sarcastic.
>
>
> I'm only partially kidding. Why is the kernel no
On Thu, Apr 7, 2016 at 3:41 PM, Nicolas M. Thiery
wrote:
> On Thu, Apr 07, 2016 at 03:19:14PM -0700, William Stein wrote:
>> There are very good reasons to supporting both modularization and much
>> more standard approaches to packaging. ... Since -- based on responses --
>>
On Wed, Apr 6, 2016 at 12:51 AM, Volker Braun wrote:
> On Tuesday, April 5, 2016 at 8:44:45 PM UTC+2, William wrote:
>>
>> [...] toward standard open source practices.
>
>
> You mean like in the Linux kernel, which uses a single monolithic git
> repository?
I think you are being sarcastic. It's
On Thu, Apr 7, 2016 at 12:14 PM, Emil Widmann wrote:
> < I don't really wee why it could not be user-friendly, can you elaborate on
> this?
>
> I think cygwin is a lot slower than virtualisation - or has this changed?
In my benchmarking even native Windows *can be* a lot slower than
Linux in a VM
s not require you to
hardwire the genus at compile time -- BTW, contrary to what it says on
trac server, the current version of smalljac (and this has been true
for at least 5 years) handles genus 1 and 2 simultaneously out of the
box, there is no need to recompile.
Drew"
On Tue, Apr 5, 2016 at
Hi,
This was a comment I just put on trac #965: "I would make a completely
separate python package, maybe called pysmalljac, which builds
smalljac and makes it usable from Python. It would be on github and
pypi. That's how most Sage development should be done. What a
monster I've created by fol
On Thu, Mar 31, 2016 at 2:08 PM, Justin C. Walker wrote:
> Hi, all,
>
> I have couple of questions regarding "attributes" in Python/Sage:
>
> 1. If hasattr(X, "foo") returns True, does that mean that "X.foo" should not
> blow up?
What's the definition of "blow up"? I think X.foo could -- due t
On Thursday, March 31, 2016, VictorMiller wrote:
> The method rational_form for matrices just returns the class
> representative of the conjugacy class of a matrix by other rational
> matrices. A similar function PrimaryRationalForm in magma returns 3 things
> -- the class representative, a rati
Maybe it is time for another Sage Days at Microsoft... (we had one
there a few years ago).
On Thu, Mar 31, 2016 at 1:02 AM, Volker Braun wrote:
> On Thursday, March 31, 2016 at 9:23:56 AM UTC+2, bluescarni wrote:
>>
>> On the theme of hell freezing over, this also happened:
>>
>> https://blogs.ms
On Wed, Mar 30, 2016 at 11:37 AM, Volker Braun wrote:
> On Wednesday, March 30, 2016 at 8:15:06 PM UTC+2, William wrote:
>>
>> "the POSIX subsystem was essentially a checkbox feature to meet some
>> government contracting requirements. [...]"
>
>
> Thought that refers to the ancient "posix subsyst
On Wed, Mar 30, 2016 at 10:54 AM, Volker Braun wrote:
> Sounds like the devil is ice-skating to work today ;-)
>
> Of course MS had a posix layer since about forever, they just never did
> anything with it or really made it available for others to use...
"the POSIX subsystem was essentially a che
On Mon, Mar 28, 2016 at 10:15 AM, Volker Braun wrote:
> On Monday, March 28, 2016 at 5:54:34 PM UTC+2, Nils Bruin wrote:
>>
>> It's a simple one to set, though, and in many contexts it protects against
>> silly memory errors (e.g., on a multi-user machine
>
>
> But it doesn't help when you have mu
On Sun, Mar 20, 2016 at 4:39 PM, Volker Braun wrote:
> On Sunday, March 20, 2016 at 10:40:56 PM UTC+1, William wrote:
>>
>> That doesn't work since SMC uses normal Linux users, not lxc or docker
>> containers, so they do not have a virtual chroot'd filesystem.
>
>
> Well that explains why massive
On Sun, Mar 20, 2016 at 3:47 PM, Dima Pasechnik wrote:
>
>
> On Sunday, March 20, 2016 at 9:40:56 PM UTC, William wrote:
>>
>> On Fri, Mar 18, 2016 at 4:52 PM, Volker Braun wrote:
>> > On Friday, March 18, 2016 at 6:39:33 PM UTC+1, William wrote:
>> >>
>> >> 3. More generally, for SMC, it's usefu
On Fri, Mar 18, 2016 at 4:52 PM, Volker Braun wrote:
> On Friday, March 18, 2016 at 6:39:33 PM UTC+1, William wrote:
>>
>> 3. More generally, for SMC, it's useful, for the sake of Sage
>> development, to have a way to setup a sage dev environment as quickly
>> as possible for user experience reaso
On Friday, March 18, 2016, Dima Pasechnik wrote:
>
>
> On Friday, March 18, 2016 at 5:33:31 AM UTC, William wrote:
>>
>>
>>
>> On Thursday, March 17, 2016, David Roe wrote:
>>
>>> Here's a use case where the recent changes to relocatability are really
>>> annoying. I'd like 6 sage installs in a
> William can speak more to the technical details for SMC, but the project
> supposedly has 11GB of RAM, 6 cores (I don't know what kind) and 53GB of
> disk space.
The project lives on a GCE n1-standard-8 VM with Haswell processors in the
us-central1-c zone:
https://cloud.google.com/compute/pri
On Fri, Mar 18, 2016 at 9:55 AM, Dima Pasechnik wrote:
>
>
> On Friday, March 18, 2016 at 3:06:04 PM UTC, William wrote:
>>
>> On Fri, Mar 18, 2016 at 7:59 AM, Volker Braun wrote:
>> > I've had people at workshops trying to compile Sage (never mind using
>> > binaries) and they were SOL because t
On Fri, Mar 18, 2016 at 8:11 AM, Volker Braun wrote:
> On Friday, March 18, 2016 at 4:06:04 PM UTC+1, William wrote:
>>
>> > Also, your use case is a bit weird; Parallel installations on the same
>> > server?
>>
>> It's David's use case for Sage Days 71. It seems to me like a
>> reasonable use ca
On Fri, Mar 18, 2016 at 10:32 AM, Jeroen Demeyer wrote:
> On 2016-03-18 04:10, David Roe wrote:
>>
>> Here's a use case where the recent changes to relocatability are really
>> annoying. I'd like 6 sage installs in an SMC project so that different
>> groups at Sage Days 71 can work independently.
On Fri, Mar 18, 2016 at 7:49 AM, Volker Braun wrote:
> On Friday, March 18, 2016 at 1:04:57 PM UTC+1, William wrote:
>>
>> Yes definitely. It worked very well for precisely this use case for a
>> decade.
>
>
> It might have worked for you but it certainly didn't work for all users,
> there was a c
On Fri, Mar 18, 2016 at 6:45 AM, Dima Pasechnik wrote:
>
>
> On Friday, March 18, 2016 at 1:12:50 PM UTC, William wrote:
>>
>> On Fri, Mar 18, 2016 at 5:42 AM, Dima Pasechnik wrote:
>> >> Yes definitely. It worked very well for precisely this use case for a
>> >> decade.
>> >
>> >
>> > well, it w
On Fri, Mar 18, 2016 at 6:36 AM, Daniel Krenn wrote:
> On 2016-03-15 15:53, Daniel Krenn wrote:
>> Were there any changes to the way trac sends mails? I am asking because
>> the mails I receive are marked as "maybe spam"; the sage-trac mail from
>> about 46 hours ago was not marked.
>
> Trac is st
On Fri, Mar 18, 2016 at 7:59 AM, Volker Braun wrote:
> I've had people at workshops trying to compile Sage (never mind using
> binaries) and they were SOL because their system bash was linked against the
> wrong version of some library. If you can't compile it you surely can't use
> it 6 times.
D
601 - 700 of 9552 matches
Mail list logo
