Re: [sage-devel] Heartbleed

[William Stein]

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 sagenb, cloud, sage cell use?
>>
>
> Sagemathcloud is patched.
> Sagenb doesn't use SSL.
>
>
>> (Also, sagemath.org seems to currently be down?)
>>
>
> No it's up.

However, it may have been down when you sent that, since we got this
message from our sysadmins:

"

Kevin Loranger

9:34 PM (16 minutes ago)
to business
at 2128 www.math.washington.edu was NOT reachable.
Five minutes later www.math.washington.edu come up very slow.
UWTech is working this network issue.

-- 
Kevin Loranger
https://sites.google.com/a/uw.edu/kevinloranger/

___





Math business mailing list
busin...@math.washington.edu"

-- 
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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[Travis Scrimshaw]

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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Problem installing sagecell

[cch]

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/build/widgets.js] Error 1
Error minifying javascript and CSS.

What does it mean?

Thanks in advance.

cch

-- 
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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Heartbleed

[William Stein]

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 doesn't use SSL.


> (Also, sagemath.org seems to currently be down?)
>

No it's up.
> - kcrisman
>
> --
> 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 sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Heartbleed

[kcrisman]

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 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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[Jean-Pierre Flori]

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 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 I will try the 
> proposed 
> > msysgit fix and let you know if that works for me. 
> can't you just use git from Cygwin instead? 
>
Sure you could, that's what I do (within a VM running on Linux)...

-- 
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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[Dima Pasechnik]

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 have the same documentation issue it seems so I will try the proposed 
> msysgit fix and let you know if that works for me.
can't you just use git from Cygwin instead?

>
> Thank you all so much for your help!!!
>
> On Tuesday, April 8, 2014 2:05:34 PM UTC-5, Sebastien Gouezel wrote:
>>
>> 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 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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[Evan Oman]

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 I will try the proposed 
msysgit fix and let you know if that works for me.

Thank you all so much for your help!!!

On Tuesday, April 8, 2014 2:05:34 PM UTC-5, Sebastien Gouezel wrote:
>
> 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 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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[Sebastien Gouezel]

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 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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[P Purkayastha]

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, Apr 8, 2014 at 11:35 PM, R. Andrew Ohana wrote:

> 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) because I didn't know what (and didn't want to deal with) other
> things might be affected if I actually moved that directory. However, it
> should probably be physically moved, and not just linked.
>
>
> On Tue, Apr 8, 2014 at 8:30 AM, P Purkayastha  wrote:
>
>> 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 to inside the sagenb/sagenb, instead of having it as
>> a symbolic link.
>>
>> - basu.
>>
>>
>>
>> On Tue, Apr 8, 2014 at 11:21 PM, Jonathan  wrote:
>>
>>> 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 8, 2014 10:07:30 AM UTC-5, kcrisman wrote:

 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 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 sage is in ~/sage and sagenb is in ~/sagenb:
>
> $ cd ~/sagenb/sagenb
> $ rm flask_version
> $ mv ../flask_version .
> $ cd ~/sage/local/lib/python/site-packages/sagenb-0.10.8.2-py2.7.egg
> $ mv sagenb{,-0.10.8.2}
> $ ln -s ~/sagenb/sagenb .
>
>
> And now, you can continue to work on sagenb dev in ~/sagenb.
>
> - basu.
>
> On Tuesday, April 8, 2014 10:33:03 AM UTC+8, kcrisman wrote:
>>
>> With the new directory layout, http://www.sagemath.org/doc/
>> developer/sagenb/index.html no longer makes any sense, and I don't
>> see any easy way to do any sagenb development without making new (s)pkgs.
>>  Is that correct?  Any ideas for making this simpler?
>>
>> Thanks,
>> - kcrisman
>>
>  --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "sage-devel" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/sage-devel/B7PpXa2VFQs/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> sage-devel+unsubscr...@googlegroups.com.
>>>
>>> To post to this group, send email to sage-devel@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/sage-devel.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
>> 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 sage-devel@googlegroups.com.
>> Visit this group at http://groups.google.com/group/sage-devel.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Andrew
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sage-devel/B7PpXa2VFQs/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 sage

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

[R. Andrew Ohana]

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) because I didn't know what (and didn't want to deal with) other
things might be affected if I actually moved that directory. However, it
should probably be physically moved, and not just linked.


On Tue, Apr 8, 2014 at 8:30 AM, P Purkayastha  wrote:

> 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 to inside the sagenb/sagenb, instead of having it as
> a symbolic link.
>
> - basu.
>
>
>
> On Tue, Apr 8, 2014 at 11:21 PM, Jonathan  wrote:
>
>> 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 8, 2014 10:07:30 AM UTC-5, kcrisman wrote:
>>>
>>> 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 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 sage is in ~/sage and sagenb is in ~/sagenb:

 $ cd ~/sagenb/sagenb
 $ rm flask_version
 $ mv ../flask_version .
 $ cd ~/sage/local/lib/python/site-packages/sagenb-0.10.8.2-py2.7.egg
 $ mv sagenb{,-0.10.8.2}
 $ ln -s ~/sagenb/sagenb .


 And now, you can continue to work on sagenb dev in ~/sagenb.

 - basu.

 On Tuesday, April 8, 2014 10:33:03 AM UTC+8, kcrisman wrote:
>
> With the new directory layout, http://www.sagemath.org/doc/
> developer/sagenb/index.html no longer makes any sense, and I don't
> see any easy way to do any sagenb development without making new (s)pkgs.
>  Is that correct?  Any ideas for making this simpler?
>
> Thanks,
> - kcrisman
>
  --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "sage-devel" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/sage-devel/B7PpXa2VFQs/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> sage-devel+unsubscr...@googlegroups.com.
>>
>> To post to this group, send email to sage-devel@googlegroups.com.
>> Visit this group at http://groups.google.com/group/sage-devel.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> 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 sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Andrew

-- 
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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[P Purkayastha]

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 to inside the sagenb/sagenb, instead of having it as
a symbolic link.

- basu.



On Tue, Apr 8, 2014 at 11:21 PM, Jonathan  wrote:

> 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 8, 2014 10:07:30 AM UTC-5, kcrisman wrote:
>>
>> 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 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 sage is in ~/sage and sagenb is in ~/sagenb:
>>>
>>> $ cd ~/sagenb/sagenb
>>> $ rm flask_version
>>> $ mv ../flask_version .
>>> $ cd ~/sage/local/lib/python/site-packages/sagenb-0.10.8.2-py2.7.egg
>>> $ mv sagenb{,-0.10.8.2}
>>> $ ln -s ~/sagenb/sagenb .
>>>
>>>
>>> And now, you can continue to work on sagenb dev in ~/sagenb.
>>>
>>> - basu.
>>>
>>> On Tuesday, April 8, 2014 10:33:03 AM UTC+8, kcrisman wrote:

 With the new directory layout, http://www.sagemath.org/doc/
 developer/sagenb/index.html no longer makes any sense, and I don't see
 any easy way to do any sagenb development without making new (s)pkgs.  Is
 that correct?  Any ideas for making this simpler?

 Thanks,
 - kcrisman

>>>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sage-devel/B7PpXa2VFQs/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[Jonathan]

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 8, 2014 10:07:30 AM UTC-5, kcrisman wrote:
>
> 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 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 sage is in ~/sage and sagenb is in ~/sagenb:
>>
>> $ cd ~/sagenb/sagenb
>> $ rm flask_version
>> $ mv ../flask_version .
>> $ cd ~/sage/local/lib/python/site-packages/sagenb-0.10.8.2-py2.7.egg
>> $ mv sagenb{,-0.10.8.2}
>> $ ln -s ~/sagenb/sagenb .
>>
>>
>> And now, you can continue to work on sagenb dev in ~/sagenb.
>>
>> - basu.
>>
>> On Tuesday, April 8, 2014 10:33:03 AM UTC+8, kcrisman wrote:
>>>
>>> With the new directory layout, 
>>> http://www.sagemath.org/doc/developer/sagenb/index.html no longer makes 
>>> any sense, and I don't see any easy way to do any sagenb development 
>>> without making new (s)pkgs.  Is that correct?  Any ideas for making this 
>>> simpler?
>>>
>>> Thanks,
>>> - kcrisman
>>>
>>

-- 
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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[kcrisman]

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 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 sage is in ~/sage and sagenb is in ~/sagenb:
>
> $ cd ~/sagenb/sagenb
> $ rm flask_version
> $ mv ../flask_version .
> $ cd ~/sage/local/lib/python/site-packages/sagenb-0.10.8.2-py2.7.egg
> $ mv sagenb{,-0.10.8.2}
> $ ln -s ~/sagenb/sagenb .
>
>
> And now, you can continue to work on sagenb dev in ~/sagenb.
>
> - basu.
>
> On Tuesday, April 8, 2014 10:33:03 AM UTC+8, kcrisman wrote:
>>
>> With the new directory layout, 
>> http://www.sagemath.org/doc/developer/sagenb/index.html no longer makes 
>> any sense, and I don't see any easy way to do any sagenb development 
>> without making new (s)pkgs.  Is that correct?  Any ideas for making this 
>> simpler?
>>
>> Thanks,
>> - kcrisman
>>
>

-- 
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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[P Purkayastha]

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 sage is in ~/sage and sagenb is in ~/sagenb:

$ cd ~/sagenb/sagenb
$ rm flask_version
$ mv ../flask_version .
$ cd ~/sage/local/lib/python/site-packages/sagenb-0.10.8.2-py2.7.egg
$ mv sagenb{,-0.10.8.2}
$ ln -s ~/sagenb/sagenb .


And now, you can continue to work on sagenb dev in ~/sagenb.

- basu.

On Tuesday, April 8, 2014 10:33:03 AM UTC+8, kcrisman wrote:
>
> With the new directory layout, 
> http://www.sagemath.org/doc/developer/sagenb/index.html no longer makes 
> any sense, and I don't see any easy way to do any sagenb development 
> without making new (s)pkgs.  Is that correct?  Any ideas for making this 
> simpler?
>
> Thanks,
> - kcrisman
>

-- 
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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[Volker Braun]

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 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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

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

[Jan Keitel]

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 error - what am I doing wrong?
> 
> Thank you!
> Andrey
> 
> 
> sage: lattice_polytope.cross_polytope(3)
> 3-d reflexive polytope in 3-d lattice M
> sage: lattice_polytope.octahedron(3)
> ---
> AttributeError    Traceback (most recent call last)
>  in ()
> > 1 lattice_polytope.octahedron(Integer(3))
> 
> /home/novoselt/sage.git/local/lib/python2.7/site-packages/sage/misc/superseded.pyc
>  in __call__(self, *args, **kwds)
>     203 
>     204 deprecation(self.trac_number,
> --> 205 "%s is deprecated. Please use %s 
> instead."%(self.__name__, other))
>     206 if self.instance is None:
>     207 return self.func(*args, **kwds)
> 
> /home/novoselt/sage.git/local/lib/python2.7/site-packages/sage/misc/lazy_attribute.so
>  in sage.misc.lazy_attribute._lazy_attribute.__get__ 
> (sage/misc/lazy_attribute.c:1357)()
> 
> /home/novoselt/sage.git/local/lib/python2.7/site-packages/sage/misc/superseded.pyc
>  in __name__(self)
>     183 if val is self:
>     184 return key
> --> 185 raise AttributeError, "The name of this deprecated function 
> can not be determined"
>     186 
>     187 def __call__(self, *args, **kwds):
> 
> AttributeError: The name of this deprecated function can not be determined

Hi Andrey,

I know too little about python internals to know how to fix this, but the 
problem appears to be that __name__ cannot find the variable name of 
lattice_polytope.octahedron because it has not been imported into the global 
namespace.

If you try something like

sage: from sage.geometry.lattice_polytope import octahedron
sage: octahedron(3)

then it does work. So it seems that __name__ is not looking in all the 
necessary places. Because it cannot find lattice_polytope.octahedron, there are 
some other things that don't work the way one might want them to. For example

sage: o = lattice_polytope.octahedron
sage: lattice_polytope.octahedron(3)
/home/pcl337b/jkeitel/sage/sage/src/bin/sage-ipython:1: DeprecationWarning: o 
is deprecated. Please use sage.geometry.lattice_polytope.cross_polytope instead.
See http://trac.sagemath.org/15240 for details.
  #!/usr/bin/env python
A lattice polytope: 3-dimensional, 6 vertices.

So is there a way to know which variables from other source files have been 
used?

Best,
Jan

-- 
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 sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.