[sage-devel] Re: Trac attachment limit

Maybe we could create packages.sagemath.org? 2016-07-25 21:33:39 UTC+2, Andrey Novoseltsev: > Creating my own site just for the sake of posting a package > (which I am doing once a year or less) is a bit of an overkill. -- You received this message because you are subscribed to the Google Group

Re: [sage-devel] Re: survey ==> Python3

On 2016-07-25 18:01, Volker Braun wrote: A language that did not change in the last 20 years is dead, plain and simple. I totally agree with this. Backwards compatibility is good to have, but it doesn't stand above everything else. A good example that comes to my mind is LaTeX: packages const

Re: [sage-devel] Re: survey ==> Python3

On 2016-07-25 22:28, Francesco Biscani wrote: Fair enough. At the same time though I do believe that the existence of the GIL in the most widespread Python implementation has effectively dragged back the language as a whole in terms of parallel programming. This is getting off-topic, but I thin

[sage-devel] Sage on Bash on Ubuntu on Windows

Hi All, Some time ago I briefly played with Bash on Ubuntu on Windows with some limited success. The situation dramatically improved recently. I would risk saying that our nightmares to support windows are nearly over. Microsoft Windows [Version 10.0.14393] (c) 2016 Microsoft Corp

[sage-devel] Chelsea Manning and SageMath

Chelsea Manning mentions SageMath as a way of researching lattice based crypto, in a message read out at the Hope Conference. https://medium.com/@xychelsea/endless-lemons-4f706c28bed9#.wgw60w29o Bill. -- You received this message because you are subscribed to the Google Groups "sage-devel" gr

Re: [sage-devel] Trac notifications again

William did update our sendgrid settings to 40,000 mails per month, which should be more than enough; although we should see how it goes in busier times. Dima On Monday, July 25, 2016 at 8:44:56 PM UTC+1, Dima Pasechnik wrote: > > I just mailed you the credentials to your UW address. > Dima >

Re: [sage-devel] Re: survey ==> Python3

On Mon, Jul 25, 2016 at 10:28 PM, Francesco Biscani wrote: > On 25 July 2016 at 17:21, Erik Bray wrote: >> >> The GIL is an implementation detail and has nothing to do with the >> language. It could (in principle) be removed at any time without >> breaking existing code, and does not exist in ot

Re: [sage-devel] Sage on Bash on Ubuntu on Windows

On Tue, Jul 26, 2016 at 10:19 AM, VulK wrote: > Hi All, > Some time ago I briefly played with Bash on Ubuntu on Windows with some > limited success. The situation dramatically improved recently. I would risk > saying that our nightmares to support windows are nearly over. > > > Microsoft W

Re: [sage-devel] Sage on Bash on Ubuntu on Windows

I am not proposing this as our final solution since, as you point out, it is a suboptimal hack on many respects; I am just saying that we can use this today (actually from Aug 2nd) to bring anyone running windows 10 on the sage bandwagon with minimal effort on our side. If I am not mistaken Bash sh

Re: [sage-devel] Sage on Bash on Ubuntu on Windows

On Tue, Jul 26, 2016 at 1:42 PM, VulK wrote: > I am not proposing this as our final solution since, as you point out, it is > a suboptimal hack on many respects; I am just saying that we can use this > today (actually from Aug 2nd) to bring anyone running windows 10 on the sage > bandwagon with mi

Re: [sage-devel] Sage on Bash on Ubuntu on Windows

On Tuesday, July 26, 2016 at 1:25:34 PM UTC+2, Erik Bray wrote: > > 2) Currently this feature is intended as a developer tool only; On the plus side every user who is interested in Sage will immensely benefit from the scientific software universe that opens up by installing the ubuntu-on-windo

Re: [sage-devel] Re: Unhandled case in EllipticCurve_from_cubic

On 25 Jul 2016 17:03, "leif" wrote: > > Jeroen Demeyer wrote: > > On 2016-07-25 13:07, John Cremona wrote: > >> Can someone make a trac ticket for this please? > > > > Done: https://trac.sagemath.org/ticket/21092 > > Ooops, race condition (I did look at the trac timeline!). > > On behalf of John (

[sage-devel] please review #20802

Now would be a good time to review the one blocker that I fixed: https://trac.sagemath.org/ticket/20802 -- 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

Re: [sage-devel] Sage on Bash on Ubuntu on Windows

On Tue, 26 Jul 2016, VulK wrote: Clearly performance are not going to be good, native applications are the way to go for this; on the other hand I am not sure it is much (or at all?) slower than a virtual machine setup. Virtualization is not emulation. CPU-intensive applications have more tha

Re: [sage-devel] Sage on Bash on Ubuntu on Windows

I don't see any reason why Sage under the WSL should be much slower than a native app. I strongly suspect it will be way faster and certainly infinitely better than Cygwin. On Tuesday, 26 July 2016 14:10:57 UTC+2, Jori Mäntysalo wrote: > > On Tue, 26 Jul 2016, VulK wrote: > > > Clearly performa

[sage-devel] Re: Chelsea Manning and SageMath

I am really happy to see her using (and endorsing) Sage. Apparently she will publish some code in November. I am not completely sure she is talking about lattice based crypto. There are other possibilities, (code-based, isogenies...) for which Sage could also be useful. Maybe this will attract

Re: [sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

It seems like something is wrong with make. What does "make --version" give? Do you have any unusual environment variables set? Can you show the output of "set"? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and

Re: [sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

Got it! Your Makefile is corrupted, see this part: [...] inst_pkgconf = $(INST)/pkgconf-0.9.7 inst_pkgconfig = $(INST)/pkgconfig-1.1.0 inst_planarity = $(INST)/planarity-2.2.0 inst_plantri = $(INST)/plantri-4.5 inst_polytopes_db = $(INST)/polytopes_db-20120220 inst_ppl = $(INST)/ppl-1.1 # All s

[sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

Paul Masson wrote: > > MacBook-Retina:~ Masson$ cd > Downloads/GitHub/sage/local/var/lib/sage/installed > > MacBook-Retina:installed Masson$ ls > > arb-2.8.1.p0gcc-4.9.3.p1mpfr-3.1.4patch-2.7.5 > > bzip2-1.0.6-20150304gf2x-1.1.p1mpir-2.7.2pkgconf-0.9.7 > > flint-2.5.2.p0mpc-1.0.3.p0ntl-9.6.2.p

[sage-devel] Re: Trac attachment limit

Samuel Lelievre wrote: > Maybe we could create packages.sagemath.org? And/or create a trac plug-in which saves uploaded spkgs there/elsewhere, i.e., to a location which doesn't get backed up [the way trac attachments currently get]. Erik? :P -leif > 2016-07-25 21:33:39 UTC+2, Andrey Novoseltse

[sage-devel] Re: survey ==> Python3

Jeroen Demeyer wrote: > On 2016-07-25 18:01, Volker Braun wrote: >> A language that did not change in the last 20 years is dead, plain and >> simple. > > I totally agree with this. Backwards compatibility is good to have, but > it doesn't stand above everything else. A good example that comes to m

Re: [sage-devel] Sage on Bash on Ubuntu on Windows

On 26/07/16 07:52, Volker Braun wrote: On Tuesday, July 26, 2016 at 1:25:34 PM UTC+2, Erik Bray wrote: 2) Currently this feature is intended as a developer tool only; On the plus side every user who is interested in Sage will immensely benefit from the scientific software universe that ope

Re: [sage-devel] Sage on Bash on Ubuntu on Windows

On Tue, Jul 26, 2016 at 4:25 PM, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > > > On 26/07/16 07:52, Volker Braun wrote: >> >> On Tuesday, July 26, 2016 at 1:25:34 PM UTC+2, Erik Bray wrote: >>> >>> >>> 2) Currently this feature is intended as a developer tool only; >> >> >> >> On the plu

[sage-devel] Re: Sage on Bash on Ubuntu on Windows

Jori Mäntysalo wrote: > On Tue, 26 Jul 2016, VulK wrote: > >> Clearly performance are not going to be good, native applications are >> the way to go for this; on the other hand I am not sure it is much (or >> at all?) slower than a virtual machine setup. > > Virtualization is not emulation. CPU-i

[sage-devel] Re: Sage on Bash on Ubuntu on Windows

Erik Bray wrote: > On Tue, Jul 26, 2016 at 4:25 PM, Vincent Delecroix > <20100.delecr...@gmail.com> wrote: >> >> >> On 26/07/16 07:52, Volker Braun wrote: >>> >>> On Tuesday, July 26, 2016 at 1:25:34 PM UTC+2, Erik Bray wrote: 2) Currently this feature is intended as a developer tool

Re: [sage-devel] Re: Sage on Bash on Ubuntu on Windows

On Tue, Jul 26, 2016 at 6:21 PM, leif wrote: > Erik Bray wrote: >> On Tue, Jul 26, 2016 at 4:25 PM, Vincent Delecroix >> <20100.delecr...@gmail.com> wrote: >>> >>> >>> On 26/07/16 07:52, Volker Braun wrote: On Tuesday, July 26, 2016 at 1:25:34 PM UTC+2, Erik Bray wrote: > > >

Re: [sage-devel] Re: Sage on Bash on Ubuntu on Windows

On Tue, Jul 26, 2016 at 9:21 AM, leif wrote: >> OS bashing will not be tolerated. > > But company bashing will... ;-) > > Microsoft used to have a POSIX layer also; no idea what happened to that > (and how usable it actually was/is). > > But it never made it into mainstream Windows AFAIK. In the

Re: [sage-devel] Re: Trac attachment limit

On Tue, Jul 26, 2016 at 6:44 AM, leif wrote: > Samuel Lelievre wrote: >> Maybe we could create packages.sagemath.org? > > And/or create a trac plug-in which saves uploaded spkgs there/elsewhere, > i.e., to a location which doesn't get backed up [the way trac > attachments currently get]. Good ide

Re: [sage-devel] Re: Sage on Bash on Ubuntu on Windows

On Tue, Jul 26, 2016 at 6:33 PM, William Stein wrote: > On Tue, Jul 26, 2016 at 9:21 AM, leif wrote: >>> OS bashing will not be tolerated. >> >> But company bashing will... ;-) >> >> Microsoft used to have a POSIX layer also; no idea what happened to that >> (and how usable it actually was/is). >

Re: [sage-devel] Re: Sage on Bash on Ubuntu on Windows

On Tue, Jul 26, 2016 at 9:37 AM, Erik Bray wrote: > On Tue, Jul 26, 2016 at 6:33 PM, William Stein wrote: >> On Tue, Jul 26, 2016 at 9:21 AM, leif wrote: OS bashing will not be tolerated. >>> >>> But company bashing will... ;-) >>> >>> Microsoft used to have a POSIX layer also; no idea what

[sage-devel] Incorrect links to external references in doc build

Hi all, I recently completed a run of `make doc`, after which I ran the tests, and there's a test that's failing: $ ./sage -t src/doc/common/conf.py too many failed tests, not using stored timings Running doctests with ID 2016-07-26-18-50-41-ca650119. Git branch: cygwin Using --optional=mpir,pyth

[sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

Jeroen Demeyer wrote: > Got it! Your Makefile is corrupted, I wouldn't say it's "corrupted", it's misgenerated: All packages (alphabetically) starting with ptyprocess are /consistently/ missing. So apparently already the loop in filtered_packages_list() for DIR in $SAGE_ROOT/build/pkgs/*; c

[sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

leif wrote: > Jeroen Demeyer wrote: >> Got it! Your Makefile is corrupted, > > I wouldn't say it's "corrupted", it's misgenerated: All packages > (alphabetically) starting with ptyprocess are /consistently/ missing. > > So apparently already the loop in filtered_packages_list() > >for DIR i

[sage-devel] [ANN] Nemo 0.5 released

Hi all, We are pleased to release Nemo 0.5. For new users, instructions on how to get Nemo are on our website: http://nemocas.org/downloads.html For existing Nemo users: as we have moved the Nemo repository to a GitHub community, we recommend removing your existing Nemo with Pkg.rm("Nemo") and

[sage-devel] Re: Sage on Bash on Ubuntu on Windows

William Stein wrote: > Regarding the above discussion about speed, what combination of > OS/Virtualization/Emulations/Native/etc. is actually fastest is not > something that can be determined by "pure thought", since there are > two additional factors (which I saw a lot in work of Bill Hart, Jason

Re: [sage-devel] Re: patchbot server not responding

Hello, I can log on patchbot.sagemath.org (as well as R. Bradshaw, R. A. Ohana and M. Marco) I do not have the technical comptetence to move the patchbot server elsewhere. This probably involves at least setting up a web server and copying the report database (which is at least 20GB large, and

Re: [sage-devel] Re: Sage on Bash on Ubuntu on Windows

On Tue, Jul 26, 2016 at 11:39 AM, leif wrote: > William Stein wrote: >> Regarding the above discussion about speed, what combination of >> OS/Virtualization/Emulations/Native/etc. is actually fastest is not >> something that can be determined by "pure thought", since there are >> two additional fa

[sage-devel] Re: Trac attachment limit

William Stein wrote: > On Tue, Jul 26, 2016 at 6:44 AM, leif wrote: >> Samuel Lelievre wrote: >>> Maybe we could create packages.sagemath.org? >> >> And/or create a trac plug-in which saves uploaded spkgs there/elsewhere, >> i.e., to a location which doesn't get backed up [the way trac >> attachme

[sage-devel] Incorrect links to external references in doc build

This Trac ticket looks related: https://trac.sagemath.org/ticket/21044 -- 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: Sage on Bash on Ubuntu on Windows

The MPIR code runs ok on Windows, though it is always some small factor behind Linux (usually 15% where we've bothered to check). So far we've been unable to superoptimise for that platform because the OS just never gets quiet enough for the superoptimiser to work. However, there can be other r

Re: [sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

MacBook-Retina:~ Masson$ make --version GNU Make 3.81 Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. This program built for i386-apple-d

Re: [sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

On Tuesday, July 26, 2016 at 6:25:12 AM UTC-7, Jeroen Demeyer wrote: > > Got it! Your Makefile is corrupted, see this part: > > [...] > inst_pkgconf = $(INST)/pkgconf-0.9.7 > inst_pkgconfig = $(INST)/pkgconfig-1.1.0 > inst_planarity = $(INST)/planarity-2.2.0 > inst_plantri = $(INST)/plantri-

Re: [sage-devel] Re: survey ==> Python3

> > That would be difficult to substantiate I think. > If you look at languages with "true" multithreading, what they provide are not only the basic building blocks which Python also has (threads, locks, mutexes, condition variables, etc.), but also a whole conceptual model of how a multi-threaded

[sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

Running "configure" resulted in a makefile that terminates at the same package. Here's some possibly relevant error messages from the configure process: planarity-2.2.0 plantri-4.5 polytopes_db-20120220 "/Users/Masson/Downloads/GitHub/sage/build/pkgs/prompt_toolkit/type" is missi

[sage-devel] Re: Trac attachment limit

What about a "packages" repository on GitHub just to store files? On Tuesday, July 26, 2016 at 12:07:45 AM UTC-7, Samuel Lelievre wrote: > > Maybe we could create packages.sagemath.org? > > 2016-07-25 21:33:39 UTC+2, Andrey Novoseltsev: > > > Creating my own site just for the sake of posting a pa

Re: [sage-devel] Re: symbolic computation with Chevalley generators for algebraic groups

I recently looked at Computing in Groups of Lie Type by Cohen, Murray and Taylor. The basic approach to representation and calculation which is taken there is essentially the one I had in mind. Plus they've worked a number of details I thought I w

[sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

The error message here led me to look at the "prompt_toolkit" package. That directory is empty, as is one for "wcwidth". Removing both folders resulted in a makefile with all actual packages. Running make again now. The supposed packages "prompt_toolkit" and "wcwidth" aren't part of either the

[sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

You tried the ipython 5.0 ticket, I presume. This left an empty directory lying around. Git doesn't know about empty directories, but our build system assumes that it is a package. And then fails and writes an incomplete makefile. You need to delete build/pkgs/prompt_toolkit, either by hand or

Re: [sage-devel] Re: symbolic computation with Chevalley generators for algebraic groups

On Tuesday, July 26, 2016 at 3:07:04 PM UTC-5, Joseph Hundley wrote: > > I recently looked at Computing in Groups of Lie Type > by > > Cohen, Murray and

[sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

As I recall I did checkout that ticket (21006) by accident when I wanted one (21008) a couple digits away. That's the source of the problem. Why can't the build system recognize an empty folder and pass over it? On Tuesday, July 26, 2016 at 1:20:38 PM UTC-7, Volker Braun wrote: > > You tried th

[sage-devel] Re: Sage on Bash on Ubuntu on Windows

William Stein wrote: > On Tue, Jul 26, 2016 at 11:39 AM, leif wrote: >> William Stein wrote: >>> Regarding the above discussion about speed, what combination of >>> OS/Virtualization/Emulations/Native/etc. is actually fastest is not >>> something that can be determined by "pure thought", since the

[sage-devel] Re: Sage on Bash on Ubuntu on Windows

On Tuesday, 26 July 2016 23:12:03 UTC+2, leif wrote: > The only difference at the C level I know of is different #includes > (maybe some OS types and functions), and the size of long on 64-bit, > which is only 32 bits on 64-bit Windows (only long long is 64 bits > there), with some impact

[sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

Paul Masson wrote: > As I recall I did checkout that ticket (21006) by accident when I wanted > one (21008) a couple digits away. That's the source of the problem. > > Why can't the build system recognize an empty folder and pass over it? That's a genuine bug in Sage's 'configure'. Not only that

[sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

Success! Many thanks to all who contributed. On Tuesday, July 26, 2016 at 1:19:55 PM UTC-7, Paul Masson wrote: > > The error message here led me to look at the "prompt_toolkit" package. > That directory is empty, as is one for "wcwidth". Removing both folders > resulted in a makefile with all ac

[sage-devel] Installing optional packages

I just installed an optional package but it took me a while to remember how to do it. Of course, it is completely straightforward but I just forgot The first place that I looked was in the "Installation guide". There is a section there on "standard packages" but nothing on "optional packages

[sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

Paul Masson wrote: > Success! Many thanks to all who contributed. Fine. Just for the record: While 'git status' doesn't show untracked empty folders as Volker mentioned, git ls-files -o --directory --exclude-standard would have shown you (also) the left-over folders which led to this. ("Lis

Re: [sage-devel] Re: Trac attachment limit

On Tue, Jul 26, 2016 at 1:04 PM, Paul Masson wrote: > What about a "packages" repository on GitHub just to store files? I was also going to suggest that. A drawback is we would have to add all trac users to the Github repo, so hundreds and hundreds of people, many probably not even on github rig

Re: [sage-devel] Re: survey ==> Python3

On Tue, Jul 26, 2016 at 12:46 PM, Francesco Biscani wrote: >> That would be difficult to substantiate I think. > > > If you look at languages with "true" multithreading, what they provide are > not only the basic building blocks which Python also has (threads, locks, > mutexes, condition variables

[sage-devel] Re: Installing optional packages

This is now https://trac.sagemath.org/ticket/21101 On Wednesday, 27 July 2016 10:18:59 UTC+10, Andrew wrote: > > I just installed an optional package but it took me a while to remember > how to do it. Of course, it is completely straightforward but I just > forgot > > The first place that I

Re: [sage-devel] Incorrect links to external references in doc build

On 2016-07-26 18:52, Erik Bray wrote: Is this a known issue? Has anyone encountered this before? Given that it's caught by a doctest, probably not. I added that doctest specifically while working on Sphinx-related tickets to ensure that links would work. -- You received this message because

Re: [sage-devel] Re: Sage on Bash on Ubuntu on Windows

On Tue, Jul 26, 2016 at 06:29:22PM +0200, Erik Bray wrote: > >> OS bashing will not be tolerated. > > > > But company bashing will... ;-) > > That's not really okay either--constructive criticisms are fine +1 > but you never know where your next funding source will come from... This argument is

Re: [sage-devel] Incorrect links to external references in doc build

On Tue, Jul 26, 2016 at 9:20 PM, Paul Masson wrote: > This Trac ticket looks related: https://trac.sagemath.org/ticket/21044 Thanks--I agree, that looks possibly related. I'm working on investigating... -- You received this message because you are subscribed to the Google Groups "sage-devel"

Re: [sage-devel] Incorrect links to external references in doc build

On Wed, Jul 27, 2016 at 8:06 AM, Jeroen Demeyer wrote: > On 2016-07-26 18:52, Erik Bray wrote: >> >> Is this a known issue? Has anyone encountered this before? > > Given that it's caught by a doctest, probably not. I added that doctest > specifically while working on Sphinx-related tickets to ens

[sage-devel] Re: No longer able to build 7.2 or 7.3 betas on Mac OS X El Capitan

leif wrote: > Paul Masson wrote: >> As I recall I did checkout that ticket (21006) by accident when I wanted >> one (21008) a couple digits away. That's the source of the problem. >> >> Why can't the build system recognize an empty folder and pass over it? > > That's a genuine bug in Sage's 'confi