Re: [sage-devel] Heartbleed

On Tue, Apr 8, 2014 at 8:20 PM, William Stein wrote: > > On Apr 8, 2014 8:06 PM, "kcrisman" wrote: >> >> >> http://www.zdnet.com/heartbleed-serious-openssl-zero-day-vulnerability-revealed-728166/ >> >> Apparently this is a real vulnerability in OpenSSL. So... just fyi. What >> version does

[sage-devel] Re: Cannot start Sage after upgrading to 6.2.beta7

PS - I'm running Ubuntu 12.04 LTS. -- 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 sa

[sage-devel] Re: Problem installing sagecell

After installing ipython-2.0.0.tar.gz, got this error message: Tracing dependencies for: widgets Error: Error: ENOENT, no such file or directory '/usr/local/sage/sagecell-main/static/require/build/notebook/js/widgetmanager.js' at Object.fs.openSync (fs.js:427:18) make: *** [static/require/bu

Re: [sage-devel] Heartbleed

On Apr 8, 2014 8:06 PM, "kcrisman" wrote: > > http://www.zdnet.com/heartbleed-serious-openssl-zero-day-vulnerability-revealed-728166/ > > Apparently this is a real vulnerability in OpenSSL. So... just fyi. What version does sagenb, cloud, sage cell use? > Sagemathcloud is patched. Sagenb do

[sage-devel] Heartbleed

http://www.zdnet.com/heartbleed-serious-openssl-zero-day-vulnerability-revealed-728166/ Apparently this is a real vulnerability in OpenSSL. So... just fyi. What version does sagenb, cloud, sage cell use? (Also, sagemath.org seems to currently be down?) - kcrisman -- You received this me

[sage-devel] Re: Building Sage with Cygwin 32 bit

On Wednesday, April 9, 2014 12:06:14 AM UTC+2, Dima Pasechnik wrote: > > On 2014-04-08, Evan Oman > wrote: > > > > > >< > https://lh3.googleusercontent.com/-oJq3iWFDFmg/U0RoSaeJluI/DMQ/yQhAr6gT1Z8/s1600/Screenshot+%282%29.png> > > > > AHA! That did it! > > > > So along with comment

[sage-devel] Re: Building Sage with Cygwin 32 bit

On 2014-04-08, Evan Oman wrote: > > > > AHA! That did it! > > So along with commenting out the lines in _rinterface that Sebastien > mentioned I have a running Sage install! > > I do

[sage-devel] Re: Building Sage with Cygwin 32 bit

AHA! That did it! So along with commenting out the lines in _rinterface that Sebastien mentioned I have a running Sage install! I do have the same documentation issue it seems so

[sage-devel] Re: Building Sage with Cygwin 32 bit

Le 08/04/2014 20:52, Evan Oman a écrit : I tried adding | ||defined(_CYGWIN_) There should be two underscores on each side of CYGWIN, i.e., __CYGWIN__ instead of _CYGWIN_ -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from

Re: [sage-devel] Re: new layout breaks sagenb development?

I have set up a pull request to move the flask_version directory to inside sagenb. The documentation can be fixed later, but this should enable anyone to start working on sagenb dev immediately. I also checked that the newly generated sagenb tarball installs and works correctly. - basu. On Tue

Re: [sage-devel] Re: new layout breaks sagenb development?

The symbolic link exists for the sole reason that previously you could not install sagenb as a standard python package (it cared deeply about its location in the SAGE_ROOT); this was necessary for getting sagenb to initially work on the git version of Sage. The symbolic link was made (as a hack) be

Re: [sage-devel] Re: new layout breaks sagenb development?

Hello Jonathan, In my experience, making a symbolic link to the root of the sagenb directory does not work. Making a symbolic link to the sagenb directory *inside the sagenb root* also does not work. My suggestion would be to change the layout of the sagenb root directory and move flask_version

[sage-devel] Re: new layout breaks sagenb development?

Another solution that works is to work with a separate sagenb git repository and then rename the directory sagenb inside the egg to something like sagenb_old. Then create a symlink to your development git repository named sagenb. This is almost the same solution as Basu's. On Tuesday, April

[sage-devel] Re: new layout breaks sagenb development?

Hey Basu, thanks! That sounds great. Can you open a ticket to fix the developer guide with this information (the last section on sagenb development)? (Suitably generic, of course.) - kcrisman On Tuesday, April 8, 2014 10:45:24 AM UTC-4, P Purkayastha wrote: > > There is an easy fix. The ma

[sage-devel] Re: new layout breaks sagenb development?

There is an easy fix. The main reason why it has broken sagenb development is because "sagenb/sagenb/flask_version" is a symbolic link to "sagenb/flask_version" - I do not know why it is set up like this. So, doing the following will allow you to work on sagenb dev - I will assume that your sag

[sage-devel] Re: "The name of this deprecated function can not be determined"

The deprecated function alias uses a hack to get the name it is assigned to, and it fails in that case. The problem is that "from foo import bar" generates a bar.__module__, but only import bar does not. I'll upload a patch to http://trac.sagemath.org/16093 when it finishes testing... -- You

[sage-devel] Re: "The name of this deprecated function can not be determined"

Am Montag, 7. April 2014 23:36:01 UTC+2 schrieb Andrey Novoseltsev: > Hello, > > I am trying to deprecate a function with an alias which seems to be very > straightforward: > http://git.sagemath.org/sage.git/commit/?id=2080f3cf0365f4b568ce1129f3d0dc448fe80f11 > but it results in the following err