Re: [sage-devel] The future of the Mac Application on Mojave

[Ivan Andrus]

I think as long as the sage tree is not inside the app bundle then we are okay. 
 I just tried it by pulling out the sage directory from the Resources directory 
and then pointing the preferences to that and it worked (there was a weird 
warning about read only at first, but we can get that worked out).

-Ivan

> On Mar 23, 2019, at 4:32 PM, Volker Braun  wrote:
> 
> For 3), where should the downloaded Sage installation be stored? If its in 
> the same folder as the Sage mac app then presumably OSX will again iterate 
> through all 1 files at glacial pace?
> 
> 
> 
> 
> -- 
> 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/nlXP6cv4LAY/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 https://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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] The future of the Mac Application on Mojave

[Ivan Andrus]

On Mar 19, 2019, at 4:01 AM, dimp...@gmail.com wrote:


Hi Ivan,
thanks for looking into this.
On Mon, Mar 18, 2019 at 06:25:53PM -0700, Ivan Andrus wrote:

I haven't worked on Sage for quite a while, but it was brought to my
attention (thanks Karl-Dieter), that the Mac application no longer works on
Mojave.  I believe this has to do with the fact that the application isn't
signed by a registered developer.  I say this because starting it from the
command line (e.g. $ /Applications/SageMath-8.5.app/Contents/MacOS/Sage)
 starts
up instantly and, as near as I can tell, perfectly.  However, when I double
click in the Finder, it gets stuck (for a very long time--maybe 10 minutes)
in _LSResolveAllQuarantineItems(...) in [NSWorkspace
openFile:withApplication:andDeactivate:].  Ten minutes may not be forever,
but it's certainly longer than we should require people to wait, especially
given that it's every time they launch the app.

This explains that weird delays people mentioned which using the app,
another "clever" OSX joke...

I can think of a few options that might be able to solve the problem:

 1. We could start signing the code.  However, I don't think signing it
 will be possible since one of the first things that happens when running
 sage is that it changes the paths embedded in certain executables (at
least
 that's what I remember).  Changing anything in the application (code or
 resources [1]) would invalidate the signing, so I think that's out.


it's a technological problem here: as LD_LIBRARY_PATH using was no
longer possible on OSX (and it's a hassle anyway), Volker's
https://github.com/sagemath/binary-pkg
builds a distribution with paths being templates, that are replaced
with actual paths once the installation is known.

What would be the correct way to achieve this on OSX?
Simply assume that Sage must be installed in /Applications/SageMath
and build the distibution with the whole absolute paths known in
advance -- surely this could be signed then, no?
Or there is something more clever?


That's an option I hadn't thought of.  It seems pretty restrictive to me,
but probably most people install it there anyway.

 2. We may be able to replace our use of [NSWorkspace
 openFile:withApplication:andDeactivate:] with something else, perhaps
using
 system().  I haven't tried this, so I have no idea if it will work.
 3. We could move to a two-item approach in which we provide the app
 *without* sage embedded inside it (so it's very small and could be
 signed, or not), and then we provide the sage distribution separately
 (could be in the same dmg file, just not embedded).  For a long time, the
 application has had the ability to use to any sage installation.  However,
 it might be difficult to automatically point people to the latest
 installation (i.e. they would have to go into the app preferences and
 change it themselves).  We could offer some sort of installer that would
 copy the sage distribution and make that change for the current user.
  Perhaps sysadmins could just create a symlink to the latest or something.
  I'm not sure what problems we've seen people have in this area.  Also,
you
 would probably lose the ability to run multiple versions of the app to
 quickly switch back and forth.
 4. Create an AppleScript (or Terminal) launcher that just runs a
 variation of the script below [2] rather than starting the app directly.
  This seems to work fine, but is somewhat annoying to need a different
 launcher.  This can hopefully work as a stop-gap for those who have this
 problem right now.

In my opinion #3 is the most promising.  How bad is #3 from a user
experience perspective?  I used to always run it that way, so it's not a
problem for me, but I've been out of the loop for a while, and my
experience might not be typical.  What problems do people foresee with
integrating any of these with the build system?  Right now I'm not able to
build sage.  I haven't dug into why, but I can if need be.  Unfortunately,
I don't know how much time I'll be able to devote to working on this so any
help would be appreciated.


Another still not completely resolved, issue is openssl. The current
Python.org' Python OSX installer papers over it in a laughable (IMHO)
way: https://bugs.python.org/issue36344
(TLDR: they package fully functional pip, with all certs etc. as
well as openssl, broken by not having cert.pem in the right place, and
"fix" this by calling a special script that calls pip to install
cert.pem into the right place, even though this cert is already there in
the installer, in pip, to be precise!)
Perhaps it's meant to satisfy a (not very smart) lawyer, I don't know...

If you have ideas about the latter, it would be good, too.


Gaa.  Openssl is indeed a mess.  I'm not sure what to do about that.

-Ivan

-- 
You received this message because you a

[sage-devel] The future of the Mac Application on Mojave

[Ivan Andrus]

I haven't worked on Sage for quite a while, but it was brought to my 
attention (thanks Karl-Dieter), that the Mac application no longer works on 
Mojave.  I believe this has to do with the fact that the application isn't 
signed by a registered developer.  I say this because starting it from the 
command line (e.g. $ /Applications/SageMath-8.5.app/Contents/MacOS/Sage)  
starts 
up instantly and, as near as I can tell, perfectly.  However, when I double 
click in the Finder, it gets stuck (for a very long time--maybe 10 minutes) 
in _LSResolveAllQuarantineItems(...) in [NSWorkspace 
openFile:withApplication:andDeactivate:].  Ten minutes may not be forever, 
but it's certainly longer than we should require people to wait, especially 
given that it's every time they launch the app.  

I can think of a few options that might be able to solve the problem:

   1. We could start signing the code.  However, I don't think signing it 
   will be possible since one of the first things that happens when running 
   sage is that it changes the paths embedded in certain executables (at least 
   that's what I remember).  Changing anything in the application (code or 
   resources [1]) would invalidate the signing, so I think that's out.
   2. We may be able to replace our use of [NSWorkspace 
   openFile:withApplication:andDeactivate:] with something else, perhaps using 
   system().  I haven't tried this, so I have no idea if it will work.
   3. We could move to a two-item approach in which we provide the app 
   *without* sage embedded inside it (so it's very small and could be 
   signed, or not), and then we provide the sage distribution separately 
   (could be in the same dmg file, just not embedded).  For a long time, the 
   application has had the ability to use to any sage installation.  However, 
   it might be difficult to automatically point people to the latest 
   installation (i.e. they would have to go into the app preferences and 
   change it themselves).  We could offer some sort of installer that would 
   copy the sage distribution and make that change for the current user. 
Perhaps sysadmins could just create a symlink to the latest or something. 
I'm not sure what problems we've seen people have in this area.  Also, you 
   would probably lose the ability to run multiple versions of the app to 
   quickly switch back and forth.
   4. Create an AppleScript (or Terminal) launcher that just runs a 
   variation of the script below [2] rather than starting the app directly. 
This seems to work fine, but is somewhat annoying to need a different 
   launcher.  This can hopefully work as a stop-gap for those who have this 
   problem right now.

In my opinion #3 is the most promising.  How bad is #3 from a user 
experience perspective?  I used to always run it that way, so it's not a 
problem for me, but I've been out of the loop for a while, and my 
experience might not be typical.  What problems do people foresee with 
integrating any of these with the build system?  Right now I'm not able to 
build sage.  I haven't dug into why, but I can if need be.  Unfortunately, 
I don't know how much time I'll be able to devote to working on this so any 
help would be appreciated.

Please keep me in CC, since I'm no longer subscribed to sage-devel.

-Ivan

[1] 
https://developer.apple.com/library/archive/documentation/Security/Conceptual/CodeSigningGuide/Procedures/Procedures.html#//apple_ref/doc/uid/TP40005929-CH4-SW5

[2]* do shell script* "/Applications/SageMath-8.5.app/Contents/MacOS/Sage 
>/dev/null 2>/dev/null&"


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

Re: [sage-devel] http://macappstore.org/sage/ ?

[Ivan Andrus]

What did you want to know about it?  I hadn’t heard of it before, but it’s just 
a brew cask which means that it downloads the disk image from sagemath and 
installs it.  So it’s just a convenient way to install app version.

-Ivan

> On Nov 7, 2016, at 6:20 AM, Dima Pasechnik  wrote:
> 
> Does anyone have an idea on http://macappstore.org/sage/ ?
> This appears to be a homebrew-based installer of Sage on OSX...
> 
> Dima
> 
> -- 
> 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 https://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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

[Ivan Andrus]

> On Aug 14, 2016, at 11:28 AM, Johan S. H. Rosenkilde  
> wrote:
> 
> Hi,
> 
> On my machine, Ivan's workaround also does not help: I get exactly the
> same behaviour as Martin R. I run Emacs 24.5.1 on Arch Linux 4.6.3-1,
> x86_64.
> 
> See also this depressing post on Emacs Stack Exchange:
> http://emacs.stackexchange.com/questions/24453/weird-shell-output-when-using-ipython-5
> 
> I don't know how serious this can turn out to be for sage-mode. But it
> seems dire...

Yes, it appears the best option is to pass this flag when invoked from inside 
Emacs (and other dumb-ish terminals).  Does anyone know how to do this?  In the 
best case we could just run

sage --simple-prompt

but that doesn’t work.

-Ivan

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

Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

[Ivan Andrus]

I tried

%config SageTerminalInteractiveShell.simple_prompt=True

in a running session inside Emacs, but it didn’t help.  Perhaps it has to be 
done at the command line?

-Ivan

> On Aug 14, 2016, at 1:54 AM, Volker Braun  wrote:
> 
> Ipython 5 has now a comman-line switch "ipython --simple-prompt" that 
> disables all escape sequences, but also disables prompt customizations. So 
> instead of sage: its then always In[] / Out[].  I didn't find a way to turn 
> of all ansi sequences while still changing the prompt to "sage:".
> 
> 
> 
> On Sunday, August 14, 2016 at 7:45:12 AM UTC+2, Ivan Andrus wrote:
> It looks like ipython is printing invalid (or at least unknown to Emacs) 
> 
> I got it to ignore them by setting
> 
> (setq ansi-color-drop-regexp
>   " 
> \\[\\([ABCDsuK]\\|[12][JK]\\|=[0-9]+[hI]\\|[0-9;]*[HfDnC]\\|\\?[0-9]+[hl]\\|J\\
>  <>)")
> 
> There is also a bug in my version of Emacs which causes these eliminated 
> escape sequences to mess with the use of the start variable in 
> 'ansi-color-filter-apply'.  To make a long story short I changed the 
> implementation to 
> 
> (defun ansi-color-filter-apply (string)
>   "Filter out all ANSI control sequences from STRING.
> 
> Every call to this function will set and use the buffer-local variable
> `ansi-color-context' to save partial escape sequences.  This information
> will be used for the next call to `ansi-color-apply'.  Set
> `ansi-color-context' to nil if you don't want this.
> 
> This function can be added to `comint-preoutput-filter-functions'."
>   (let ((start 0) end result)
> ;; if context was saved and is a string, prepend it
> (if (cadr ansi-color-context)
> (setq string (concat (cadr ansi-color-context) string)
>   ansi-color-context nil))
> ;; eliminate unrecognized escape sequences
> (while (string-match ansi-color-drop-regexp string)
>   (setq string
> (replace-match "" nil nil string)))
> ;; find the next escape sequence
> (while (setq end (string-match ansi-color-regexp string start))
>   (setq result (concat result (substring string start end))
> start (match-end 0)))
> ;; save context, add the remainder of the string to the result
> (let (fragment)
>   (if (string-match "\033" string start)
> (let ((pos (match-beginning 0)))
>   (setq fragment (substring string pos)
> result (concat result (substring string start pos
>   (setq result (concat result (substring string start
>   (setq ansi-color-context (if fragment (list nil fragment
> result))
> 
> and it fixed it for me (I swapped the order of the "eliminate unrecognized 
> escape sequences" and "find the next escape sequence".  I have filed a bug on 
> it.  
> 
> Let me know if that solves the issue.  If so, then maybe we can add a 
> workaround to sage-mode or figure out how to get ipython to stop sending the 
> control sequences.  If not it would be helpful to know what version of Emacs 
> you’re running.
> 
> -Ivan
> 
>> On Aug 11, 2016, at 3:49 PM, 'Martin R' via sage-devel > <>googlegroups.com <http://googlegroups.com/>> wrote:
>> 
>> This is now https://trac.sagemath.org/ticket/21227 
>> <https://trac.sagemath.org/ticket/21227>
>>  
>> 
>> -- 
>> 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+...@ <>googlegroups.com <http://googlegroups.com/>.
>> To post to this group, send email to sage-...@ <>googlegroups.com 
>> <http://googlegroups.com/>.
>> Visit this group at https://groups.google.com/group/sage-devel 
>> <https://groups.google.com/group/sage-devel>.
>> For more options, visit https://groups.google.com/d/optout 
>> <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 
> <mailto:sage-devel+unsubscr...@googlegroups.com>.
> To post to this group, send email to sage-devel@googlegroups.com 
> <mailto:sage-devel@googlegroups.com>.
> Visit this group at https://groups.google.com/group/sage-devel 
> <https://groups.google.com/group/sage-devel>.
> For more options, visit https://groups.google.com/d/optout 
> <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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

[Ivan Andrus]

It looks like ipython is printing invalid (or at least unknown to Emacs) 

I got it to ignore them by setting

(setq ansi-color-drop-regexp
  " 
\\[\\([ABCDsuK]\\|[12][JK]\\|=[0-9]+[hI]\\|[0-9;]*[HfDnC]\\|\\?[0-9]+[hl]\\|J\\)")

There is also a bug in my version of Emacs which causes these eliminated escape 
sequences to mess with the use of the start variable in 
'ansi-color-filter-apply'.  To make a long story short I changed the 
implementation to 

(defun ansi-color-filter-apply (string)
  "Filter out all ANSI control sequences from STRING.

Every call to this function will set and use the buffer-local variable
`ansi-color-context' to save partial escape sequences.  This information
will be used for the next call to `ansi-color-apply'.  Set
`ansi-color-context' to nil if you don't want this.

This function can be added to `comint-preoutput-filter-functions'."
  (let ((start 0) end result)
;; if context was saved and is a string, prepend it
(if (cadr ansi-color-context)
(setq string (concat (cadr ansi-color-context) string)
  ansi-color-context nil))
;; eliminate unrecognized escape sequences
(while (string-match ansi-color-drop-regexp string)
  (setq string
(replace-match "" nil nil string)))
;; find the next escape sequence
(while (setq end (string-match ansi-color-regexp string start))
  (setq result (concat result (substring string start end))
start (match-end 0)))
;; save context, add the remainder of the string to the result
(let (fragment)
  (if (string-match "\033" string start)
  (let ((pos (match-beginning 0)))
(setq fragment (substring string pos)
  result (concat result (substring string start pos
(setq result (concat result (substring string start
  (setq ansi-color-context (if fragment (list nil fragment
result))

and it fixed it for me (I swapped the order of the "eliminate unrecognized 
escape sequences" and "find the next escape sequence".  I have filed a bug on 
it.  

Let me know if that solves the issue.  If so, then maybe we can add a 
workaround to sage-mode or figure out how to get ipython to stop sending the 
control sequences.  If not it would be helpful to know what version of Emacs 
you’re running.

-Ivan

> On Aug 11, 2016, at 3:49 PM, 'Martin R' via sage-devel 
>  wrote:
> 
> This is now https://trac.sagemath.org/ticket/21227
>  
> 
> -- 
> 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 https://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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage apps for iOS and Android

[Ivan Andrus]

Ah, you’re right.  Somehow I missed the fact that I was calling html.table().

-Ivan

> On May 27, 2016, at 8:21 AM, Andrey Novoseltsev  wrote:
> 
> On Friday, 27 May 2016 00:32:55 UTC-6, Ivan Andrus wrote:
> Also, I see a deprecation warning at http://aleph.sagemath.org/?q=deuoxi 
> <http://aleph.sagemath.org/?q=deuoxi> namely:
> 
> sagemathcell.py:29: DeprecationWarning:  html(...) will change soon to return 
> HTML instead of printing it. Instead use pretty_print(html(...)) for strings 
> or just pretty_print(...) for math. 
> See http://trac.sagemath.org/18292 <http://trac.sagemath.org/18292> for 
> details.
> 
> -Ivan
> 
> That's for your code! If you have a better idea for the file name, let me 
> know. Perhaps "user_input.py"? Or even "your_input.py"?
> 
> This particular deprecation was there for half a year, but it is recent 
> change that the correct line of code is shown, I've posted about it here 
> https://groups.google.com/d/topic/sage-devel/-KiMrG--5x8/discussion 
> <https://groups.google.com/d/topic/sage-devel/-KiMrG--5x8/discussion> but 
> people don't seem to care. The correct fix is probably something in IPython, 
> while I am doing this: 
> https://github.com/sagemath/sagecell/commit/bf5b926bd382768029a0fc9d3c7895855ddeb366
>  
> <https://github.com/sagemath/sagecell/commit/bf5b926bd382768029a0fc9d3c7895855ddeb366>
> 
>> On May 27, 2016, at 12:28 AM, Ivan Andrus gmail.com 
>> <http://gmail.com/>> wrote:
>> 
>> I’m not sure I trust the debugging facilities, but can’t it seem to load 
>> jquery.   However, the url it’s querying works just fine in a desktop 
>> browser or with curl.  In fact, it doesn’t seem to have $ defined.
>> 
>> I finally figured out that it wasn’t loading because of a security policy 
>> that it can only load scripts over https.  I don’t know if something has 
>> changed on the server side, or if that’s a side effect of compiling with a 
>> newer Xcode.
>> 
>> Anyway, I have to go to bed now.
>> 
>> -Ivan
>> 
>>> On May 26, 2016, at 10:23 PM, Andrey Novoseltsev gmail.com 
>>> <http://gmail.com/>> wrote:
>>> 
>>> Well, maybe history for the js folder would be better:
>>> https://github.com/sagemath/sagecell/commits/master/js 
>>> <https://github.com/sagemath/sagecell/commits/master/js>
>>> 
>>> Is there some console for iOS that shows what's wrong or at least where 
>>> things get stuck? Current version is very verbose in terms of logging, you 
>>> should be able to see all messages to/from IPython components.
>>> 
>>> The most visible js change should be the switch from iopub/shell to 
>>> channels prefix for everything and necessity to add a key to the message 
>>> with either iopub or shell value.
>>> 
>>> On Thursday, 26 May 2016 22:04:54 UTC-6, Ivan Andrus wrote:
>>> On May 26, 2016, at 9:46 AM, Andrey Novoseltsev > 
>>> wrote: 
>>> > 
>>> > I got a report that iOS app using SageMathCell is broken and I imagine 
>>> > the same is true for Android. Can someone look into updating them? This 
>>> > commit may be helpful in figuring out what to do: 
>>> > https://github.com/sagemath/sagecell/commit/9878eadc0b6f9959388549e21d8f7945e94f00b2
>>> >  
>>> > <https://github.com/sagemath/sagecell/commit/9878eadc0b6f9959388549e21d8f7945e94f00b2>
>>> >  
>>> > 
>>> > Thank you! 
>>> > Andrey 
>>> 
>>> The Android is completely different, so it very well might not be broken.   
>>> 
>>> I’m afraid I didn’t find that commit very enlightening.  I don’t actually 
>>> know the sage cell code, but since that’s a py file, I’m not sure how it 
>>> relates to the javascript in an embedded cell. 
>>> 
>>> -Ivan
>>> 
>>> -- 
>>> 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+...@ <>googlegroups.com <http://googlegroups.com/>.
>>> To post to this group, send email to sage-...@ <>googlegroups.com 
>>> <http://googlegroups.com/>.
>>> Visit this group at https://groups.google.com/group/sage-devel 
>>> <https://groups.google.com/group/sage-devel>.
>>> For more options, visit https://groups.google.com/d/optout 
>>> <https://groups.google.com/d/optout>.
>&

Re: [sage-devel] Sage apps for iOS and Android

[Ivan Andrus]

Also, I see a deprecation warning at http://aleph.sagemath.org/?q=deuoxi 
<http://aleph.sagemath.org/?q=deuoxi> namely:

sagemathcell.py:29: DeprecationWarning:  html(...) will change soon to return 
HTML instead of printing it. Instead use pretty_print(html(...)) for strings or 
just pretty_print(...) for math. 
See http://trac.sagemath.org/18292 for details.

-Ivan

> On May 27, 2016, at 12:28 AM, Ivan Andrus  wrote:
> 
> I’m not sure I trust the debugging facilities, but can’t it seem to load 
> jquery.   However, the url it’s querying works just fine in a desktop browser 
> or with curl.  In fact, it doesn’t seem to have $ defined.
> 
> I finally figured out that it wasn’t loading because of a security policy 
> that it can only load scripts over https.  I don’t know if something has 
> changed on the server side, or if that’s a side effect of compiling with a 
> newer Xcode.
> 
> Anyway, I have to go to bed now.
> 
> -Ivan
> 
>> On May 26, 2016, at 10:23 PM, Andrey Novoseltsev > <mailto:novos...@gmail.com>> wrote:
>> 
>> Well, maybe history for the js folder would be better:
>> https://github.com/sagemath/sagecell/commits/master/js 
>> <https://github.com/sagemath/sagecell/commits/master/js>
>> 
>> Is there some console for iOS that shows what's wrong or at least where 
>> things get stuck? Current version is very verbose in terms of logging, you 
>> should be able to see all messages to/from IPython components.
>> 
>> The most visible js change should be the switch from iopub/shell to channels 
>> prefix for everything and necessity to add a key to the message with either 
>> iopub or shell value.
>> 
>> On Thursday, 26 May 2016 22:04:54 UTC-6, Ivan Andrus wrote:
>> On May 26, 2016, at 9:46 AM, Andrey Novoseltsev > 
>> wrote: 
>> > 
>> > I got a report that iOS app using SageMathCell is broken and I imagine the 
>> > same is true for Android. Can someone look into updating them? This commit 
>> > may be helpful in figuring out what to do: 
>> > https://github.com/sagemath/sagecell/commit/9878eadc0b6f9959388549e21d8f7945e94f00b2
>> >  
>> > <https://github.com/sagemath/sagecell/commit/9878eadc0b6f9959388549e21d8f7945e94f00b2>
>> >  
>> > 
>> > Thank you! 
>> > Andrey 
>> 
>> The Android is completely different, so it very well might not be broken.   
>> 
>> I’m afraid I didn’t find that commit very enlightening.  I don’t actually 
>> know the sage cell code, but since that’s a py file, I’m not sure how it 
>> relates to the javascript in an embedded cell. 
>> 
>> -Ivan
>> 
>> -- 
>> 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 
>> <mailto:sage-devel+unsubscr...@googlegroups.com>.
>> To post to this group, send email to sage-devel@googlegroups.com 
>> <mailto:sage-devel@googlegroups.com>.
>> Visit this group at https://groups.google.com/group/sage-devel 
>> <https://groups.google.com/group/sage-devel>.
>> For more options, visit https://groups.google.com/d/optout 
>> <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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage apps for iOS and Android

[Ivan Andrus]

I’m not sure I trust the debugging facilities, but can’t it seem to load 
jquery.   However, the url it’s querying works just fine in a desktop browser 
or with curl.  In fact, it doesn’t seem to have $ defined.

I finally figured out that it wasn’t loading because of a security policy that 
it can only load scripts over https.  I don’t know if something has changed on 
the server side, or if that’s a side effect of compiling with a newer Xcode.

Anyway, I have to go to bed now.

-Ivan

> On May 26, 2016, at 10:23 PM, Andrey Novoseltsev  wrote:
> 
> Well, maybe history for the js folder would be better:
> https://github.com/sagemath/sagecell/commits/master/js 
> <https://github.com/sagemath/sagecell/commits/master/js>
> 
> Is there some console for iOS that shows what's wrong or at least where 
> things get stuck? Current version is very verbose in terms of logging, you 
> should be able to see all messages to/from IPython components.
> 
> The most visible js change should be the switch from iopub/shell to channels 
> prefix for everything and necessity to add a key to the message with either 
> iopub or shell value.
> 
> On Thursday, 26 May 2016 22:04:54 UTC-6, Ivan Andrus wrote:
> On May 26, 2016, at 9:46 AM, Andrey Novoseltsev > wrote: 
> > 
> > I got a report that iOS app using SageMathCell is broken and I imagine the 
> > same is true for Android. Can someone look into updating them? This commit 
> > may be helpful in figuring out what to do: 
> > https://github.com/sagemath/sagecell/commit/9878eadc0b6f9959388549e21d8f7945e94f00b2
> >  
> > <https://github.com/sagemath/sagecell/commit/9878eadc0b6f9959388549e21d8f7945e94f00b2>
> >  
> > 
> > Thank you! 
> > Andrey 
> 
> The Android is completely different, so it very well might not be broken.   
> 
> I’m afraid I didn’t find that commit very enlightening.  I don’t actually 
> know the sage cell code, but since that’s a py file, I’m not sure how it 
> relates to the javascript in an embedded cell. 
> 
> -Ivan
> 
> -- 
> 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 
> <mailto:sage-devel+unsubscr...@googlegroups.com>.
> To post to this group, send email to sage-devel@googlegroups.com 
> <mailto:sage-devel@googlegroups.com>.
> Visit this group at https://groups.google.com/group/sage-devel 
> <https://groups.google.com/group/sage-devel>.
> For more options, visit https://groups.google.com/d/optout 
> <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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Sage apps for iOS and Android

[Ivan Andrus]

On May 26, 2016, at 9:46 AM, Andrey Novoseltsev  wrote:
> 
> I got a report that iOS app using SageMathCell is broken and I imagine the 
> same is true for Android. Can someone look into updating them? This commit 
> may be helpful in figuring out what to do:
> https://github.com/sagemath/sagecell/commit/9878eadc0b6f9959388549e21d8f7945e94f00b2
> 
> Thank you!
> Andrey

The Android is completely different, so it very well might not be broken.  

I’m afraid I didn’t find that commit very enlightening.  I don’t actually know 
the sage cell code, but since that’s a py file, I’m not sure how it relates to 
the javascript in an embedded cell.

-Ivan

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

[sage-devel] Re: [sage-notebook] Coming SageMathCell upgrade - please test!

[Ivan Andrus]

On May 26, 2016, at 4:30 PM, Andrey Novoseltsev  wrote:
> 
> On Thursday, 26 May 2016 10:34:07 UTC-6, kcrisman wrote:
> http://ask.sagemath.org/question/33555/problem-with-encoding-german-characters/
>  
> 
>  could be related, or so the poster seems to imply - though probably not bad 
> enough to go back before 7.2. 
> 
> Thanks a lot for pointing it out - this is the worst problem I am currently 
> aware of and it is definitely new. Would be solved by a switch to Python3, I 
> guess ;-)
> 
> Overall things seem to be good enough that I don't plan a reversal anymore. 

Over the past few days I’ve gotten several complaints about the iOS sage app 
being broken.  Unfortunately, I missed the message that you were upgrading the 
cell server, so I didn’t know where to look immediately.

The method that the app uses is to load a webpage with an embedded sage cell in 
it, with some options other stuff to communicate back to the app.  The template 
webpage is 

https://bitbucket.org/gvol/sage-ios-app/src/c688df944ae283e1bb080ebabaec18dec584b2fa/template.html?fileviewer=file-view-default
 


Perhaps you will be able to look at it and notice that I’m doing something bad. 
 

-Ivan

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

Re: [sage-devel] latest OSX 7.1 beta builds available for testing - reverse support request

[Ivan Andrus]

I put up a branch on trac.  I haven’t tested the upgrading capability (which 
requires #19877), but the rest should work.  Let me know if you have any 
problems.

-Ivan

> On Feb 20, 2016, at 12:02 PM, Juan Luis Varona  
> wrote:
> 
> 
> Thanks, Ivan!
> 
> I will check the progress of the .app and the ticket from time to time.
> 
>  Yours,
> 
> Juan Luis
> 
> -- 
> 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 https://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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Mac App PSA

[Ivan Andrus]

On Feb 27, 2016, at 2:45 AM, Volker Braun  wrote:
> 
> Since that question came up elsewhere:
> 
> The Mac app is built with the Makefile at #19673.
> 
> This has been the case for a while now, its just that nobody found the time 
> to review the ticket that puts it back into the Sage repo.

Thanks, I hadn’t realized this had been done.

I created a new branch with some fixes, apart from which I give it a positive 
review.

-Ivan


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

Re: [sage-devel] Re: latest OSX 7.1 beta builds available for testing - reverse support request

[Ivan Andrus]

I’ve been working on it, albeit slowly.  It’s good to know people actually care 
though.  The trac ticket for this is http://trac.sagemath.org/ticket/19881 
, so you can add yourself to the CC list 
to be notified as I make progress.  If you have any thoughts on the interface 
etc. feel free to add them to the ticket or let me know via email.

You can run Jupyter from the app using "Terminal Session > Sage (advanced)" and 
then typing in --notebook=jupyter.  Though admittedly that’s not much easier 
than typing it into a terminal.

-Ivan

> On Feb 18, 2016, at 5:58 PM, Juan Luis Varona  
> wrote:
> 
> I have installed
> sage-7.1.beta3-OSX_10.11.3-x86_64.app.dmg
> in my macbook air (late 2010) with os x 10.11.2 (El Capitan) and it seems to 
> work without problems.
> Great!!!
> 
> From the app, I can see only the traditional notebook, so I can not to check 
> jupyter (as long as I know, it is not possible to use sage -n jupyter from 
> the app).
> 
> But, if, inside SageMath-7.1.beta3.app, I execute 
> /Contents/Resources/sage/ sage -n jupyter
> the jupyter aspect appears and seems to work also without problems.
> 
> It is not possible to add a preference to the app to choose if you want to 
> use the traditional notebooks or jupyter?
> I do not know if this is difficult or very easy.
> 
> Yours,
> 
> Juan Luis
> 
> 
> 
> -- 
> 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 https://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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] How can I know if Jupyter is running?

[Ivan Andrus]

On Jan 17, 2016, at 1:12 AM, Volker Braun  wrote:
> 
> IMHO the app should just start and manage its own jupyter server; Launch it 
> on startup and shut it down when the app is closed. The notebook server 
> doesn't fork into the background so its trivial to just keep a single 
> process, no need for a pidfile.

Well, I disagree, but it sounds like it’s the only option.

> If the user wants to launch a separate server (maybe with different options) 
> by hand then he/she should be allowed to.
> 
> PS:
> * Always use subprocess over os.system

I was planning to use NSTask.  :-)

> * Jupyter will autoincrement the port if it is in use, don't rely on it using 
> the given —port

Right.

> * Race conditions with ports, pids, and filenames are unlikely but often 
> exploitable security issues.

I’ll keep that in mind.

-Ivan

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

[sage-devel] How can I know if Jupyter is running?

[Ivan Andrus]

To adapt to the soon-to-be-default Jupyter notebook in Sage, I’m updating the 
Mac app to launch either SageNB or Jupyter depending on a preference.  
Unfortunately, I can’t figure out how to determine if Jupyter is already 
running at all, let alone in a given directory or on what port.  I can scrape 
the log if I’m the one who started the server, but I would like to check if 
they have started it some other way.  Does anyone know how to do that?

Also, I’m thinking of making ~/Documents/Sage the default directory to run 
Jupyter in.  Does that seem reasonable to everyone?

-Ivan

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

Re: [sage-devel] Sage on OS X: El Capitan

[Ivan Andrus]

> On Oct 21, 2015, at 8:42 PM, Michael Welsh  wrote:
> 
>> On 22/10/2015, at 0819, Christian Nassau  wrote:
>> 
>> On 21.10.2015 21:11, John H Palmieri wrote:
>>> The latest beta version of Sage should build on OS X 10.11. It has a 
>>> serious limitation: you can't move the installation once it has been built. 
>>> I don't know if anyone is working on fixing this, or on a proposed stopgap 
>>> (http://trac.sagemath.org/ticket/19410) which basically forces the Mac 
>>> installation (when you do "sage --bdist") to be in a particular directory.
>> 
>> I might be inclined to put some work into the #19410 (which I proposed), if 
>> there were some sort of consensus that this is the way to go (i.e.: forbid 
>> relocation, use a fixed install diectory). I'm more or less a complete Mac 
>> newbie and got started on this issue purely out of idle curiosity - I'm not 
>> at all sure whether experienced Mac users agree that this solution a) will 
>> work and b) is the right one.
>> 
>> Cheers,
>> Christian
> 
> IMO, this solution will work, but is not the best one. An installer that 
> allows the user to select the installation directory (which is then fixed) is 
> a better idea.

> I don't move apps around very much, and I can't think of any time I've moved 
> one after having the installer ask me where to install it (the ones I can 
> remember moving are TeXLive, which installs its apps in some subsubfolder, 
> and old iWork, when the same thing happened).

The issue, IIUC, is that it has to be installed in the same path as it was 
built in.  So just having an installer won’t change anything.  Rather, the user 
should _not_ be allowed to change the installation directory.

> I'm not a fan of /Applications/sagemath-$version, as then upgrading causes a 
> new folder to be made, which will break any aliases/dock shortcuts.

If it’s not in a versioned folder, then you can never have more than one 
version of sage at a time.  I don’t know how important that is to people.

The app itself is capable of pointing to any installation, so maybe we _should_ 
change how the app is installed.  Namely, the app itself could be put anywhere 
but would _not_ contain the sage install itself.  This would be moved to a 
specific location (namely the same place it was built) by an "installer", and 
Sage.app would be updated to point to it.  OTOH, I’m not sure this is actually 
any better since if the user doesn’t have root privileges they would be able to 
install the app, but not Sage itself—which seems suboptimal. :-)

I’ve been pretty busy at work, but I can probably scrounge some time to work on 
this portion once we know what we want to do.

-Ivan

-- 
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: sage_mode 0.14 not out there?

[Ivan Andrus]

I’m afraid I can’t help you with it’s (lack of) presence on the mirror servers. 
 I’ve CC’d sage-devel for that.  In the mean time, you should be able to 
install it from the bitbucket spkg. 

sage -i https://bitbucket.org/gvol/sage-mode/downloads/sage_mode-0.14.spkg

-Ivan

> On May 28, 2015, at 4:59 AM, David Rysdam  wrote:
> 
> I was running sage 6.5 and sage_mode 0.12(?) on Debian 7. But I recently
> upgraded to Debian 8, had some problems with 6.5 and decided to try the
> latest.
> 
> 6.7 compiles all right, but when I run 'sage -f sage_mode', I get a
> bunch of messages like:
> 
>Attempting to download package sage_mode-0.14
>http://mirrors.mit.edu/sage/spkg/upstream/sage_mode/sage_mode-0.14.tar.bz2
>[]
>[Errno 404] Not Found:
>'//mirrors.mit.edu/sage/spkg/upstream/sage_mode/sage_mode-0.14.tar.bz2'
>
> http://mirrors-usa.go-parts.com/sage/sagemath/spkg/upstream/sage_mode/sage_mode-0.14.tar.bz2
>[]
>[Errno 404] Not Found:
>
> '//mirrors-usa.go-parts.com/sage/sagemath/spkg/upstream/sage_mode/sage_mode-0.14.tar.bz2'
>
> http://mirrors-uk.go-parts.com/sage/sagemath/spkg/upstream/sage_mode/sage_mode-0.14.tar.bz2
> 
> This goes on for a while until the end, when it just fails.
> 
> Going to a few of these URLs, I find that it's no lie--sage_mode 0.14
> isn't there. What's up?

-- 
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] Sage Emacs lovers

[Ivan Andrus]

With new changes to the %display system in Sage, typeset output in
Emacs will break unless one (or more) of you review the following trac
tickets:

http://trac.sagemath.org/ticket/18115 — Add sage support for an Emacs
display backend
http://trac.sagemath.org/ticket/17580 — Update sage-mode to handle the
new backend

Also, sage-mode is woefully out of date in Sage, so even if you don’t
care about typeset output, reviewing #17580 would be a great boon to
all Emacs users.

The new backend is actually quite a bit cooler than the old one.  It
outputs both plain text and LaTeX-ified output (with plain text
hidden).  This means that you can copy either, which is cool since
often the plain text output is also valid Sage input whereas the LaTeX
version is not.  It also displays the text version while typesetting
the LaTeX version which is better than the "typesetting please wait"
message from before.

So I’m very excited about these changes.  Please help me get them in.

Thanks,
Ivan

P.S. If you’re feeling very generous, you could also review
http://trac.sagemath.org/ticket/10504 which will help typing functions
into the Sage shell inside Emacs (or other dumb terminals).

-- 
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] Sage logo -- Proposal

[Ivan Andrus]

> On Mar 29, 2015, at 9:39 AM, William Stein  wrote:
> 
> On Sun, Mar 29, 2015 at 8:23 AM, jplab  wrote:
>> Hi all,
>> 
>> Lately, I was suggested to create a post concerning the Sage logo. It would
>> be nice to have an open discussion about some possibilities. Perhaps this is
>> a good place to do so.
>> 
>> I hope the discussion will be constructive.
>> 
>> Indeed, one may ask the reason "why bother?", "why change the logo?". This
>> is indeed a relevant question to ask. Perhaps this thread could gather ideas
>> about the sage logo and opinions about it?
>> 
>> I believe it seems to some users and developers that the logo is something
>> that looks like an icosahedron. Is that the case in the origin?
>> 
>> If so, I used sage and tikz to produce a similar picture which is an actual
>> faithful drawing of an icosahedron. (I join the picture and the code to this
>> post). I kind of like the picture and it was produced using Sage (and tikz)!
>> A self-made logo is cool also I would say?
>> 
>> Could this be used to produce a logo for sage?
>> 
>> Plusses:
>> -vector graphics
>> -custumizable
>> 
>> One could also easily add the "sage" letter logo to it.
> 
> I wonder if there is a way to have the text "SageMath", now that we
> changed the name officially.
> 
> It is a great idea to "refresh" the logos periodically.   I think the
> history of the logos for Sage:
> 
>  - In 2006, Alex Clemesha's little brother drew something, which Alex
> then turned into the first logo with a sort of 'infinity' symbol in
> the middle.  Alex is a so-cal skater/surfer, and was probably inspired
> by that in design...?
> 
>  - A year or two later I think maybe Harald Schilly designed the
> icosahedron logo.  I'm sure he has vector graphics for it.  I might be
> wrong about who did the design.

Vector graphics can be found from here:
http://wiki.sagemath.org/CorporateIdentity

I don’t think it’s an icosahedron though.  IIRC it’s some combinatorial graph 
or other.

-Ivan

-- 
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] Running Sage.app installed by another user

[Ivan Andrus]

On Dec 5, 2014, at 9:07 AM, Jérôme Tremblay  wrote:

> Under OSX Yosemite, I try to install Sage 6.4.1 app in the system 
> applications. 
> 
> When I run sage as admin, everything works fine. However, when my users try 
> to run Sage, they get a warning that they are trying to execute Sage from a 
> read-only filesystem.
> 
> My question is :
> 
> It it safe to execute Sage.app if it's installed by the admin? If so, how do 
> I suppress the warning? If not, what can I do? I can't really start 
> installing a the whole Sage in each of my users personal space….

As a very cheap suppression of the warning, you could 
chmod go+w /path/to/Sage.app/Contents/Resources/sage/sage

-Ivan

-- 
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] Sage.app binary problems

[Ivan Andrus]

The 6.4.1 download _does_ give the app.

-Ivan

On Dec 1, 2014, at 12:03 PM, Volker Braun  wrote:

> Can somebody tell me for sure that the current osx binary is wrong? The app 
> and dmg have different sizes.
> 
> 
> 
> On Monday, December 1, 2014 6:54:29 PM UTC, kcrisman wrote:
> 
> I, just downloaded the Sage.app (OSX 10.9) from 2 different server and the 
> resulting downloads didn't give the Sage.app, but simply the src
> Maybe theres a problems?
> 
> It's conceivable that the mirrors were still updating, though in that case I 
> thought there would be no link at all.  Is this still a problem?
> 
> Hi kcrisman,
> 
> I think the original poster means "binary" instead of "src".
> 
> What may have happened at some point is that the script to
> produce sage-osx.dmg and sage-osx-app.dmg was producing
> sage-osx.dmg properly, but then producing the same again
> and calling it sage-osx-app.dmg, because of some missing
> setting of an environment variable. We should check if this
> is fixed now, ie, does the sage-osx-app.dmg available for
> download really contain the -app version?
> 
> 
> Ah, this is probably it -  Volker reported something similar happening with 
> the 10.10 binary last time, I believe.  Maybe the same thing happened here?
> 
> -- 
> 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.

Re: [sage-devel] Trac and sort by lastmod

[Ivan Andrus]

On Sep 26, 2014, at 6:33 AM, kcrisman  wrote:

> 
> > After clicking Lastmod-header it got tickets sorted like 
> > 
> > 1 mins < 23 hours < 32 mins <  8 days 
> 
> It's not a direct answer to your question, but you might be interested 
> in http://trac.sagemath.org/report/92 
> 
> 
> This is nearly useless, though, except for tickets modified since the last 
> Sage (official) release.  Is there any way to get back to the "old" system 
> where the milestone would change *without* changing the ticket - and hence 
> the ticket last-mod time?  It is very misleading to see ticket #xyz modified 
> three weeks ago and it turns out that it was last substantively modified in 
> 2008.

Do we really need to change the milestone every time?  Why can't we just set 
them all to future, and then when they get merged, we can change the milestone 
to the actual version?  As it is now, it seems milestone serves no real 
purpose.  It's not the version it was originally reported against.  It's not 
the version it's going to be fixed in.  It's just the next release that will be 
made.

-Ivan

-- 
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] Sage package bash?

[Ivan Andrus]

On Sep 26, 2014, at 7:59 AM, Dima Pasechnik  wrote:

> From the noises I hear, in particular on our departamental email, sysadmins 
> might be tempted to "rm -f /bin/bash"
> from any place they can get their hands on.
> 
> It might mean that for building/working with Sage one will need a separate 
> install of bash.
> (or we should switch to another shell...)

I don't think that would help security at all since bash is available simply as

os.system('sage-native-execute /bin/bash')

-Ivan

-- 
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: Remove webassets from sagenb?

[Ivan Andrus]

On Aug 5, 2014, at 9:46 PM, François Bissey  
wrote:

> On Tue, 05 Aug 2014 07:06:36 kcrisman wrote:
>> That took more time to track down than I would have liked.   So I guess we 
>> can indeed scrap it, though if we can keep samuela's branch compatibility 
>> (this is called the "newui" branch on github) that would be good for 
>> honoring that contribution, as someone may have time to do this in the long 
>> run (sagenb may not be cutting-edge but it is still the best choice for a
>> lot of local work; I assume it is lighter-weight than whatever local SMC
>> comes up but assumptions are dangerous).  Anyway, hope this detective work
>> was useful.
> Actually if you are using KDE there is an interesting alternative to sagenb:
> "cantor" http://www.kde.org/applications/education/cantor
> Pity it doesn't work on OS X.

Has anyone tried?  You can install KDE libraries with homebrew (or fink, or mac 
ports).  It's not inconceivable that cantor could work.

-Ivan

-- 
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] emacs, SageTeX, multiple major modes

[Ivan Andrus]

On Jul 9, 2014, at 2:11 PM, Dan Drake  wrote:

> On Wed, 09 Jul 2014 at 01:03PM -0600, Ivan Andrus wrote:
>> Sweet!  Would you mind if I added it to sage-mode?  There is already a
>> sage-latex.el which does some AUCTeX specific setup.  I would be
>> willing to do it, or you can create a pull request (thereby getting
>> credit).
> 
> I'll make a pull request, although be warned that I really don't know
> elisp well; I can fiddle around with my .emacs but haven't done anything
> "bigger". You may end up just doing it yourself. :)

No problem!  I munch elisp for breakfast. :-)

Thanks,
Ivan

-- 
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] emacs, SageTeX, multiple major modes

[Ivan Andrus]

On Jul 9, 2014, at 12:24 PM, Dan Drake  wrote:

> Hi,
> 
> Those of you who use SageTeX with emacs and, say, AUCTeX, may be annoyed
> when you are editing sageblock environments because of the TeX-like
> behavior. Here's a snippet you can use to make emacs use MMM (multiple
> major modes) and treat your TeX like TeX, and your Sage code like Sage
> code.

Sweet!  Would you mind if I added it to sage-mode?  There is already a 
sage-latex.el which does some AUCTeX specific setup.  I would be willing to do 
it, or you can create a pull request (thereby getting credit).

> https://gist.github.com/dandrake/6d7e46f36cecab6d89bc
> 
> You'll need MMM (https://github.com/purcell/mmm-mode) and perhaps also
> our own sage-mode.
> 
> Comments welcome -- I've only tested this with one versions of emacs,
> and there are some problems with font lock. But it does work!

Yes, AUCTeX uses non-standard font locking IIRC.

-Ivan

-- 
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] Logs for aleph.sagemath.org

[Ivan Andrus]

On Jun 6, 2014, at 7:11 AM, Jason Grout  wrote:

> On 6/5/14, 2:33, Ivan Andrus wrote:
>> Are there logs (and if so where are they?) for aleph.sagemath.org?  I'm 
>> trying to figure out what sorts of things the iOS app is used for.
> 
> Yes, there are logs.   Right now, we log remote ip, referer, execution type, 
> kernel id, and the code text: 
> https://github.com/sagemath/sagecell/blob/master/log.py
> 
> That's a good idea to log the user agent too, but we don't have historical 
> data on that (at least from the ios app)

I looked on boxen but can't find the log files (maybe I need access to 
/home/sagenb?).  Then (I thought) I remembered it was moved off of boxen, but I 
couldn't find where to in the archives.

Anyway, it would still be interesting to know what people are doing in general, 
but if I can't separate out the app, it's less useful I suppose.

Thanks,
Ivan

-- 
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: Logs for aleph.sagemath.org

[Ivan Andrus]

On Thu, Jun 5, 2014 at 6:33 AM, kcrisman  wrote:

> Are there logs (and if so where are they?) for aleph.sagemath.org?  I’m
>> trying to figure out what sorts of things the iOS app is used for.
>>
>
> Just FYI, there are a lot of other things Sage cell is used for, and
> presumably some places still point to aleph not sagecell.sagemath...
>

Yes, but if it keeps track of the user agent I should be able to get a
pretty good picture of what the app is used for.

-Ivan

-- 
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] Logs for aleph.sagemath.org

[Ivan Andrus]

Are there logs (and if so where are they?) for aleph.sagemath.org?  I'm trying 
to figure out what sorts of things the iOS app is used for.

Thanks,
Ivan

-- 
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] Default arguments for notebook in Mac app

[Ivan Andrus]

In the past some have wanted to use the Mac app for starting the notebook 
server on a different interface etc.  This will be possible (after 
http://trac.sagemath.org/ticket/16437 is reviewed) by using default arguments 
(in Preferences using "notebook" as the session).

Any help reviewing it would be appreciated.

-Ivan

-- 
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] Sage and Emacs

[Ivan Andrus]

On Jun 2, 2014, at 2:53 PM, Nicolas M. Thiery  wrote:

>   Dear Sage and emacs users,
> 
> Following Nathann recent discovery of the which-function-mode life
> saver, we pondered that it was time to have a centralized point to
> gather tips and tricks about Sage for emacs users. Since I haven't
> found one, I recycled the former sage-mode wiki page for this:
> 
>   http://wiki.sagemath.org/Emacs
> 
> Please edit and share your favorite tips!

Or if you have any suggestions/feature requests.  You can also create issues on 
bitbucket.

> Cheers,
>   Nicolas
> 
> PS: and now the big question: which page will become most useful?
> 
>   http://wiki.sagemath.org/Vi
>   http://wiki.sagemath.org/Eclipse
>   ...
> 
> :-)

They should just point back to http://wiki.sagemath.org/Emacs :-P

-Ivan


-- 
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] tab-completion in sage_mode / emacs broken

[Ivan Andrus]

On May 28, 2014, at 5:46 AM, 'Martin R' via sage-devel 
 wrote:

> Hi Ivan!
> 
> thanks for your rapid reply!  I only got to the problematic computer today.  
> So:
> 
> %colors NoColor
> 
> works (which is wonderful!),  but
> 
> https://bitbucket.org/gvol/sage-mode/downloads/sage_mode-0.11.spkg
> 
> doesn't :-(

Ack!  Sorry I didn't reply to you earlier.  Needless to say it's working for 
me.  I wonder if you have an old version hanging around.  I presume you 
restarted Emacs?  What are the values of `sage-mode-version' and 
`sage-startup-before-prompt-command'?  If you customized the latter, you will 
have to change it to "%colors NoColor" (or at least include that).  

If you're still having problems, please send me relevant portions of your 
.emacs and any error messages you see.

Thanks,
Ivan

-- 
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: tab-completion in sage_mode / emacs broken

[Ivan Andrus]

FWIW, I just updated http://trac.sagemath.org/ticket/16294 to use the new 
version as well, so checking that over might be useful as well.  

Thanks for the bug report by the way.

-Ivan

On May 24, 2014, at 1:22 PM, Ivan Andrus  wrote:

> I tried it on Emacs 23.3.1 and I see the same problem.  It's getting confused 
> by the ansi color escape sequences.  I pulled out some code to deal with it 
> because I thought it could handle it, but apparently I didn't test with old 
> Emacsen.  Anyway, the thing to do for now is run 
> 
> %colors NoColor
> 
> before you do any tab completion.  Or, I decided to release 0.11 (which 
> should fix this problem), so you can get the newest spkg: 
> https://bitbucket.org/gvol/sage-mode/downloads/sage_mode-0.11.spkg
> 
> -Ivan
> 
> On May 24, 2014, at 2:46 AM, 'Martin R' via sage-devel 
>  wrote:
> 
>> I'm sorry, I should have mentioned that I tried both sage_mode 0.10 and 
>> https://bitbucket.org/gol/sage-mode/downloads/sage_mode-20140407.spkg 
>> without success.
>> 
>> In case it is of any help: I tried the %psearch within sage, which works.  
>> From edebug it seems to me that it is a problem of communication between 
>> sage-mode and python.  How should it work? Does sage-mode send the %psearch 
>> command to a separate python process?
>> 
>> Martin
>> 
>> Am Samstag, 24. Mai 2014 07:42:28 UTC+2 schrieb Ivan Andrus:
>> It works for me with Sage 6.3.beta1, Emacs 24.3.91.3 (from git), and 
>> sage_mode (from hg).  Can you try installing the latest sage_mode from 
>> https://bitbucket.org/gvol/sage-mode/downloads, namely 
>> https://bitbucket.org/gvol/sage-mode/downloads/sage_mode-20140407.spkg  You 
>> can of course install from source if you wish as well.  If the latest 
>> version works for you I'll hurry and release version 0.11 so that others 
>> won't have the same problem. 
>> 
>> On a side note, I'm in the process of updating sage_mode to use the new spkg 
>> system.  You could also try installing it that way.  See 
>> http://trac.sagemath.org/ticket/16294 if you're interested. 
>> 
>> -Ivan 
>> 
>> On May 22, 2014, at 2:51 AM, Martin Rubey  wrote: 
>> 
>> > Hi there, 
>> > 
>> > I just installed sage 6.3.beta1 (from git) and sage_mode. 
>> > 
>> > Unfortunately, tab completion is broken in emacs. 
>> > 
>> > I'm using GNU Emacs 23.3.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.10). 
>> > 
>> > When I press tab, the mouse pointer changes into the "please wait" 
>> > thingy, and nothing happens.  top doesn't show any activity.  I tried 
>> > edebug on 
>> > 
>> > (defun sage-pcomplete-or-help () 
>> >  "If point is after ?, describe preceding symbol; otherwise, pcomplete." 
>> >  (interactive) 
>> >  (if (not (looking-back "[^\\?]\\?")) 
>> >  (pcomplete) 
>> >(save-excursion 
>> >  (backward-char) 
>> >  (when (python-current-word) 
>> > (ipython-describe-symbol (python-current-word)) 
>> > 
>> > But I don't know where to go from here. (Of course, pcomplete is not 
>> > returning...) 
>> > 
>> > Thanks for any help, 
>> > 
>> > Martin 
>> 
>> 
>> -- 
>> 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.

Re: [sage-devel] Re: tab-completion in sage_mode / emacs broken

[Ivan Andrus]

I tried it on Emacs 23.3.1 and I see the same problem.  It's getting confused 
by the ansi color escape sequences.  I pulled out some code to deal with it 
because I thought it could handle it, but apparently I didn't test with old 
Emacsen.  Anyway, the thing to do for now is run 

%colors NoColor

before you do any tab completion.  Or, I decided to release 0.11 (which should 
fix this problem), so you can get the newest spkg: 
https://bitbucket.org/gvol/sage-mode/downloads/sage_mode-0.11.spkg

-Ivan

On May 24, 2014, at 2:46 AM, 'Martin R' via sage-devel 
 wrote:

> I'm sorry, I should have mentioned that I tried both sage_mode 0.10 and 
> https://bitbucket.org/gol/sage-mode/downloads/sage_mode-20140407.spkg without 
> success.
> 
> In case it is of any help: I tried the %psearch within sage, which works.  
> From edebug it seems to me that it is a problem of communication between 
> sage-mode and python.  How should it work? Does sage-mode send the %psearch 
> command to a separate python process?
> 
> Martin
> 
> Am Samstag, 24. Mai 2014 07:42:28 UTC+2 schrieb Ivan Andrus:
> It works for me with Sage 6.3.beta1, Emacs 24.3.91.3 (from git), and 
> sage_mode (from hg).  Can you try installing the latest sage_mode from 
> https://bitbucket.org/gvol/sage-mode/downloads, namely 
> https://bitbucket.org/gvol/sage-mode/downloads/sage_mode-20140407.spkg  You 
> can of course install from source if you wish as well.  If the latest version 
> works for you I'll hurry and release version 0.11 so that others won't have 
> the same problem. 
> 
> On a side note, I'm in the process of updating sage_mode to use the new spkg 
> system.  You could also try installing it that way.  See 
> http://trac.sagemath.org/ticket/16294 if you're interested. 
> 
> -Ivan 
> 
> On May 22, 2014, at 2:51 AM, Martin Rubey  wrote: 
> 
> > Hi there, 
> > 
> > I just installed sage 6.3.beta1 (from git) and sage_mode. 
> > 
> > Unfortunately, tab completion is broken in emacs. 
> > 
> > I'm using GNU Emacs 23.3.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.10). 
> > 
> > When I press tab, the mouse pointer changes into the "please wait" 
> > thingy, and nothing happens.  top doesn't show any activity.  I tried 
> > edebug on 
> > 
> > (defun sage-pcomplete-or-help () 
> >  "If point is after ?, describe preceding symbol; otherwise, pcomplete." 
> >  (interactive) 
> >  (if (not (looking-back "[^\\?]\\?")) 
> >  (pcomplete) 
> >(save-excursion 
> >  (backward-char) 
> >  (when (python-current-word) 
> > (ipython-describe-symbol (python-current-word)) 
> > 
> > But I don't know where to go from here. (Of course, pcomplete is not 
> > returning...) 
> > 
> > Thanks for any help, 
> > 
> > Martin 
> 
> 
> -- 
> 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.

Re: [sage-devel] What to use instead of `%display typeset`

[Ivan Andrus]

Thanks.  It works for great.  I gave it a positive review.  If only I had known 
it would be so easy. :-)

Thanks again,
Ivan

On May 22, 2014, at 3:37 AM, Volker Braun  wrote:

> This was broken in the IPython update, I think. I've hooked up our existing 
> "typeset" displayhook to also work in IPython.
> 
> http://trac.sagemath.org/16389
> 
> With the ticket, the output is:
> 
> sage: %display typeset
> sage: 1/2
>  type="math/tex">\newcommand{\Bold}[1]{\mathbf{#1}}\frac{1}{2}
> 
> 
> 
> On Thursday, May 22, 2014 5:31:49 AM UTC+1, Ivan Andrus wrote:
> There is a thread on sage-support [0] in which it is lamented that 
> typesetting results in Emacs is broken.  This is because `%display typeset` 
> doesn't work in 6.2.  Since I know not everyone reads sage-support, I thought 
> I would ask here what I should use instead of `%display typeset`.  See also 
> the related ticket [1] where it was suggested to use `%display typeset`. 
> 
> Thanks, 
> Ivan 
> 
> [0] https://groups.google.com/forum/#!topic/sage-support/HD_g24L7ta8 
> [1] http://trac.sagemath.org/ticket/15271
> 
> -- 
> 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] Re: tab-completion in sage_mode / emacs broken

[Ivan Andrus]

It works for me with Sage 6.3.beta1, Emacs 24.3.91.3 (from git), and sage_mode 
(from hg).  Can you try installing the latest sage_mode from 
https://bitbucket.org/gvol/sage-mode/downloads, namely 
https://bitbucket.org/gvol/sage-mode/downloads/sage_mode-20140407.spkg  You can 
of course install from source if you wish as well.  If the latest version works 
for you I'll hurry and release version 0.11 so that others won't have the same 
problem.

On a side note, I'm in the process of updating sage_mode to use the new spkg 
system.  You could also try installing it that way.  See 
http://trac.sagemath.org/ticket/16294 if you're interested.

-Ivan

On May 22, 2014, at 2:51 AM, Martin Rubey  wrote:

> Hi there,
> 
> I just installed sage 6.3.beta1 (from git) and sage_mode.
> 
> Unfortunately, tab completion is broken in emacs.
> 
> I'm using GNU Emacs 23.3.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.10).
> 
> When I press tab, the mouse pointer changes into the "please wait"
> thingy, and nothing happens.  top doesn't show any activity.  I tried
> edebug on
> 
> (defun sage-pcomplete-or-help ()
>  "If point is after ?, describe preceding symbol; otherwise, pcomplete."
>  (interactive)
>  (if (not (looking-back "[^\\?]\\?"))
>  (pcomplete)
>(save-excursion
>  (backward-char)
>  (when (python-current-word)
>   (ipython-describe-symbol (python-current-word))
> 
> But I don't know where to go from here. (Of course, pcomplete is not
> returning...)
> 
> Thanks for any help,
> 
> Martin

-- 
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] What to use instead of `%display typeset`

[Ivan Andrus]

There is a thread on sage-support [0] in which it is lamented that typesetting 
results in Emacs is broken.  This is because `%display typeset` doesn't work in 
6.2.  Since I know not everyone reads sage-support, I thought I would ask here 
what I should use instead of `%display typeset`.  See also the related ticket 
[1] where it was suggested to use `%display typeset`.

Thanks,
Ivan

[0] https://groups.google.com/forum/#!topic/sage-support/HD_g24L7ta8
[1] http://trac.sagemath.org/ticket/15271

-- 
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: interact.sagemath.org

[Ivan Andrus]

On May 6, 2014, at 11:47 AM, Jason Grout  wrote:

> On 5/5/14, 14:20, Daniel Bell wrote:
>> Hi
>> 
>> I am one of the students who was selected for working with Sage for
>> Google Summer of Code.  I will be working on the iOS app.  One of the
>> features I want to implement is the ability to interact with
>> interact.sagemath.org 
>> 
>> Is there an API I can use, or a database I can interact with?
> 
> interact.sagemath.org is using Drupal, so I imagine it would be a pretty 
> standard thing to enable a REST API or something of that sort.  Would you 
> like to take over the website and do that?

I take it from this that you were the maintainer, and it will therefore be 
abandoned soon?

-Ivan

-- 
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] GSOC 2014 iOS App

[Ivan Andrus]

On Feb 25, 2014, at 2:42 AM, Aditya Makkar  wrote:

> Hi,
> I am Aditya and I am interested in getting involved in Google Summer of Code 
> with Sage. I am just finishing my second year at Indian Institute of 
> Technology, Delhi doing B.Tech in Mechanical Engineering. I have good 
> knowledge of C++, Python and Objective-C. I have some experience in iOS app 
> development, mainly through the course "CS 193P iPhone Application 
> Development", which I am currently doing. I have the Sage app on iPad and I 
> have downloaded the code from here(Bitbucket).

> So I would really love if I could be a contributor to Sage and work on this 
> project in my summers.

Cool!  My suggestion at this stage is to use the iOS app (which I assume you 
are) and come up with ideas for improvements.  I think it looks really good on 
your GSOC application if you've already submitted a pull request or otherwise 
had a patch accepted (even a fairly trivial one) since that shows that shows 
that you've been in communication and such.

I know there is lots of room for improvement on the iPad version.  I have some 
ideas, but you'll probably come up with better ones.

> Thank You
> Aditya Makkar
> 
> PS: I am sorry if this not the right place to post this, since I could not 
> post it in sage-gsoc google group.

Feel free to contact me directly (or via bitbucket) if you have questions 
specific to the iOS app.

-Ivan

-- 
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/groups/opt_out.

Re: [sage-devel] Re: Please elaborate on the difference between the two OS X binaries for Sage 6.0.

[Ivan Andrus]

There are supposed to be two versions–one with the app and the other
without.  The reason for the non-app version is so that those users who
don’t want to use the app can more easily access the sage folder.

In an ideal world there would be one version that contains the app, and
also the sage directory at the top level.  But this would double the size
of the download unless the sage directory was a hard link to the one
embedded in the app.  Hard linking is technically possible but would be
tricky to implement and brittle since there are no public apis for it.
 Using a soft link/alias won’t work nicely since copying it will copy the
link instead of the directory linked to.  So that’s the background.

As for how to build them, it should be a matter of setting the environment
variable SAGE_APP_BUNDLE=yes vs. setting it to anything else (or leaving it
unset).

-Ivan

On Jan 20, 2014, at 7:12 AM, Volker Braun  wrote:

I'd also like to know what the expectations for the OSX binaries are. Why
are there two separate ones to start with? Should I change something in how
they are built?


On Sunday, January 19, 2014 10:25:45 AM UTC, Geoff Oxberry wrote:
>
> According to the download website (http://boxen.math.washington.
> edu/home/sagemath/sage-mirror/osx/intel/index.html), the main difference
> between the two binaries is that one is geared towards Unix-style CLI use
> on OS X, and the other is meant to be a clickable Mac-style binary. The
> README in both disk images reflects this distinction.
>
> However, having downloaded both disk images, I don't see a "sage" folder
> in the Unix-style CLI disk image. I only see the README, and "Sage.app"
> (technically a folder, but not named "sage"), so the first-level directory
> layout looks the same, and double-clicking on Sage.app from the Unix-style
> CLI disk image starts Sage without having to resort to any of the
> additional steps for launching Sage from the README.
>
> Obviously, the two disk images are different; they have different
> checksums, and different file sizes. Could someone explain the differences
> in a little more detail?
>

-- 
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/groups/opt_out.

Re: [sage-devel] Sherlock

[Ivan Andrus]

On Jan 6, 2014, at 2:02 AM, John Cremona  wrote:
> On 5 January 2014 23:25, Tom Boothby  wrote:
>> On Sun, Jan 5, 2014 at 2:47 PM, Martin Albrecht
>>  wrote:
>> 
 I remember that dinner... where I had license discussions with an
 intoxicated Germans...
>>> 
>>> Makes sense: as far as I know the Sage rule is you're *only* allowed to 
>>> discuss licenses if you are intoxicated.
>> 
>> I'm going to have to disagree with that... we'd be discriminating
>> against several developers based on religious grounds.  Unless, like
>> me, they can intoxicate themselves on the very concept of software
>> licensing.
> 
> It certainly sends me to sleep...
> 
> John


And gives me a hangover.  :-)

-Ivan

-- 
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/groups/opt_out.

Re: [sage-devel] emacs configuration for git-sage

[Ivan Andrus]

Anne, 

I'm really sorry.  I meant to get back to you sooner, but your email got lost 
in my inbox.  Anyway, when you install the sage_mode spkg it should tell you 
what to put in your .emacs.  You can always install it again if you need to 
remember.  Anyhow, in this case the directory should be

/Applications/sage/share/emacs/site-lisp/sage-mode

You will have to use the latest spkg though:
https://bitbucket.org/gvol/sage-mode/downloads/sage_mode-0.10.spkg

But it was recently positively reviewed, so I think `sage -i sage_mode` should 
work fine.

-Ivan

On Nov 6, 2013, at 10:21 PM, Anne Schilling  wrote:

> Hi!
> 
> With mercurial git I had the following line in my .emacs file
> 
> (add-to-list 'load-path (expand-file-name "/Applications/sage/data/emacs"))
> 
> but now sage/data does not exist any longer. What should I put there?
> 
> Thanks,
> 
> Anne
> 
> -- 
> 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/groups/opt_out.

-- 
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/groups/opt_out.

Re: [sage-devel] Need help with optional spkgs

[Ivan Andrus]

Valgrind complains about glibc being too recent.  It should be updated from 
3.7.0 to 3.8.1 anyway.  This is http://trac.sagemath.org/ticket/13060 which 
unfortunately has issues on OS X.  I suggest that we move forward with the spkg 
at that ticket and worry about OS X later since otherwise it may never get 
upgraded.  Unfortunately, that means I won't be able to help review it (though 
I think it already had positive review except on OS X).

-Ivan

On Oct 7, 2013, at 4:52 AM, Volker Braun  wrote:

> We need to make sure that the optional spkg still work with the new git 
> directory layout. I've tried to build all optional spkgs and the following 
> ran into problems installing. Some failures may be trivial, but some spkgs 
> will need updating. If you care about one of these, please check the build 
> log and help transition it to the new directory layout. If it turns out that 
> nobody cares then we will move the spkg to experimental.
> 
> brian
> cunningham_tables
> database_cremona_ellcurve
> database_jones_numfield
> database_kohel
> database_odlyzko_zeta
> database_sloane_oeis
> database_stein_watkins_mini.p0
> database_symbolic_data
> fricas
> fricasaldor
> jsmath_image_fonts
> libcocoa
> libtheora
> mpi4py
> openssl
> p_group_cohomology
> PyQt_x11
> TOPCOM
> valgrind
> 
> Logfiles are here: 
> http://boxen.math.washington.edu/home/vbraun/Sage/Testing/optional/
> 
> The corresponding trac ticket is http://trac.sagemath.org/ticket/14962
> 
> -- 
> 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/groups/opt_out.

-- 
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/groups/opt_out.

Re: [sage-devel] We need a new color?

[Ivan Andrus]

When in doubt about rgb colors, consult xkcd: http://xkcd.com/color/rgb/

There he identifies sage (87ae73), light sage (bcecac), dark sage (598556), and 
sage green (88b378).

-Ivan

On Sep 26, 2013, at 8:57 PM, kcrisman  wrote:

> From a user.  I'm not sure how the matplotlib devels would feel about adding 
> this.  And which RGB value would it be, anyway? ;-)
> +++
> One of my students pointed out a weird flaw in Sage today.  Namely, in the 
> plotting color options, 'sage' is not a known color name.  So, e.g., 
> plot((e^(sin(x))),(x,-5,5),color='sage')
> generates an error.
> 
> My entire class felt that this was a problematic oversight on the part of the 
> Sage developers.  In fact, they proposed that sage be the default plotting 
> color in Sage.  
> 
> Any insights here?  Are the developers humorless?  Have they just not noticed 
> this gaping color hole?
> 
> -- 
> 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/groups/opt_out.

-- 
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/groups/opt_out.

Re: [sage-devel] broken prompts in Emacs shell-mode

[Ivan Andrus]

Not that this bug shouldn't be fixed, and not that there aren't valid reasons 
for running sage in an emacs shell, but just in case you didn't know: you can 
install the sage_mode spkg and run sage directly using the `sage' command.

-Ivan

On Sep 20, 2013, at 11:54 AM, Bill Janssen  wrote:

> In an Emacs shell, Sage seems to be ignoring the TERM setting (dumb) and 
> sending ANSI escape sequences to the terminal around the "sage:" prompt.
> 
> [pippin:~] wjanssen% printenv TERM
> dumb
> [pippin:~] wjanssen% /local/sage-5.11/sage
> ++
> | Sage Version 5.11, Release Date: 2013-08-13|
> | Type "notebook()" for the browser-based notebook interface.|
> | Type "help()" for help.|
> ++
> [0;34msage: [0m
> 
> Is there a way to defeat this?  Should I file a bug on this?
> 
> Bill
> 
> -- 
> 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/groups/opt_out.

-- 
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/groups/opt_out.

Re: [sage-devel] funding sage through catincan ?

[Ivan Andrus]

There's also http://www.freedomsponsors.org and I'm sure several others.  
Freedom Sponsors is more about fixing bugs as near as I can tell, which I think 
is actually more immediately useful.  I like the model of Freedom Sponsors 
since it's more user driven than developer driven.  That said, I have no 
experience with the site itself, and there's no reason we couldn't use both.

I think this could be a good way to get people working on "unimportant", i.e. 
non-mathematical, bugs or small features.  Things for which most Sage 
developers would have little motivation to do otherwise.  In my opinion, the 
money should be split (somehow) between the person who wrote the patch(es) and 
the person who reviewed those patches.  

-Ivan

On Aug 9, 2013, at 11:51 AM, Harald Schilly  wrote:

> Hello.
> I just found out about the website https://www.catincan.com/
> 
> It's idea is to fund specific tasks or new features of existing
> open-source projects through crowdfunded pledges.
> Does anybody have any experience with that page, or does find this an
> interesting model to fund some work on Sage?
> The benefit is certainly, that funded features might get done earlier
> and more thoroughly, because money is in the end quite some motivator
> to get things done.
> On the other hand, this kind of partial funding could be discouraging
> for other "pro-bono" developers.
> 
> One core issue is also, who would get the money and how it is actually
> distributed. It must be an US account, so in my eyes William would be
> my first choice.
> 
> Harald
> 
> -- 
> 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/groups/opt_out.
> 
> 

-- 
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/groups/opt_out.

Re: [sage-devel] Re: cloud.sagemath.org, Sage Notebook, command line, etc

[Ivan Andrus]

On Jul 17, 2013, at 11:17 PM, Jason Grout  wrote:
> On 7/15/13 6:58 AM, Pedro Cruz wrote:
>> Hello,
>> 
>> what sequence of instructions could tell what Sage 5.10 "user-interface"
>> is currently being used ?
>> 
>> Possible answers are:
>> 
>>  - cloud.sagemath.org
>>  - Sage Notebook
>>  - "linux" command line
>>  - "windows" command line (?)
>>  - "cygwin" command line (?)
>>  - new others...
>> 
>> Long ago I used to check if variable
>>sage.plot.plot.EMBEDDED_MODE
>> is defined to see if notebook is being used.
>> 
> 
> I have a patch that changes EMBEDDED_MODE to a dictionary that tells you what 
> frontend (notebook or cell server) is being used.  I've been waiting for the 
> switch to git to submit it, though.  I hope to submit it in the next month or 
> so.

FWIW, sage-mode sets EMBEDDED_MODE to true when displaying inline plots so that 
it knows where to grab the files from and such.  It can be changed to use a new 
way, but please cc me on the ticket/pull request so I can be ready.

-Ivan

-- 
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/groups/opt_out.

Re: [sage-devel] UTF-8 and old terminals (new startup banner)

[Ivan Andrus]

+1 to a UTF-8 banner.  

FWIW, Terminal.app and iTerm2.app (on OS X) also work.

-Ivan

On Jul 7, 2013, at 8:05 PM, Volker Braun  wrote:

> Frédéric Chapoton has written a patch at http://trac.sagemath.org/14733 that 
> will beautify the Sage startup banner using some UTF-8 characters to draw the 
> box. This will display incorrectly in terminals that do not support UTF-8. In 
> that case, Sage still works but the box around the banner is garbled (most 
> likely rendered by placeholder signs for non-ASCII characters).
> 
> Of course, various Sage source files are already UTF-8 encoded, usually 
> because of non-ASCII characters in docstrings. These will never render 
> correctly in ancient terminals, nor will editing such source files lead to 
> much happiness. The questions is essentially, do we want to make it clear to 
> the user right at the beginning that his terminal is not up to the task or 
> would we rather only have more subtle errors later?
> 
> Working terminals:
>   * xterm
>   * urxvt (the rxvt-unicode fork)
>   * gnome-terminal
>   * kterm
> 
> Not working:
>   * Eterm (unless your distro integrates inofficial patches that are floating 
> around)
>   * aterm
>   * rxvt and various clones that predate rxvt-unicode
> 
> 
> -- 
> 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/groups/opt_out.
>  
>  

-- 
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/groups/opt_out.

Re: [sage-devel] spkg statistics

[Ivan Andrus]

On Jul 5, 2013, at 3:48 AM, Harald Schilly  wrote:

> A week ago i started to log what's happening on the sagemath.org
> website and analyzed the resulting logfiles. The following page shows
> cumulative numbers for the downloads of SPKGes, which might come in
> handy!
> 
> http://sagemath.org/spkg_stats.html

Cool!

> * having sage-mode and sage_mode seems odd. I assume that's an error
> and we should get rid of the 0.7 version?

Indeed sage-mode-0.7 should no longer be there.  I changed the name to 
sage_mode (underscore) so that version parsing works correctly.  Anyhow, it 
should go away.

-Ivan

-- 
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/groups/opt_out.

[sage-devel] Re: Mac App broken on OS X 10.4

[Ivan Andrus]

Oops, forgot to send to the list.

On May 2, 2013, at 8:05 AM, kcrisman  wrote:

> Because you have the buildbot, I haven't been checking lately... I may have 
> time to try this out next week.
> 
> On Thursday, May 2, 2013 8:57:49 AM UTC-4, Jeroen Demeyer wrote:
> I just noticed this when creating the Sage 5.9 binaries: the Mac App 
> doesn't build anymore on OS X 10.4 (PPC). I personally don't care very 
> much, but maybe other people do. This problem probably dates back to 
> Sage 5.8 (for unrelated reasons, no binaries of Sage 5.8 were made for 
> OS X 10.4) 
> 
> Here is the relevant line
> 
> - (void)alertDidEnd:(NSAlert *)alert returnCode:(NSInteger)returnCode 
> contextInfo:(void *)contextInfo { 
> 
> which perhaps does indeed use something newer.  Note that I point out in my 
> part of the review
> 
> I haven't tested this on anything but Snow Leopard.
> 
> So perhaps I should have barked a little when nkirchner set positive review 
> (you didn't even add him to the reviewer, Jeroen :) but it had been a long 
> time since I had even looked at it, and then it was sage-pending for months 
> and months... aargh.

I'm pretty sure it doesn't use anything not available on 10.4.  Also "parse 
error" sounds weird.  Is there a 10.4 box I could play around with?  I have an 
account on boxen.

If not, someone could try adding 

- (void)alertDidEnd:(NSAlert *)alert returnCode:(NSInteger)returnCode 
contextInfo:(void *)contextInfo;

to the header.  It's just a shot in the dark though.

> I didn't open a ticket yet - Ivan, do you want to do that?


I opened http://trac.sagemath.org/sage_trac/ticket/14521

-Ivan

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [sage-devel] Mac App broken on OS X 10.4

[Ivan Andrus]

On May 2, 2013, at 8:10 AM, Jeroen Demeyer  wrote:
> On 05/02/2013 04:05 PM, kcrisman wrote:
>> Because you have the buildbot, I haven't been checking lately...
> 
> I also wasn't really aware of the fact that the Mac App is only built when 
> running sage --bdist, so a normal "make ptestlong" doesn't catch this.

Should we add a test to build it?  With the move to git it might actually be a 
good time to turn it into an spkg (or not).  Then, if I am not mistaken, it 
_would_ be tested.  It doesn't actually take to long to build, and doesn't 
depend on anything else.  The part that takes forever is copying the whole 
distribution inside and that shouldn't be done until running bdist.

-Ivan

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [sage-devel] About the extcode spkg

[Ivan Andrus]

On Mar 21, 2013, at 2:15 PM, Julien Puydt  wrote:

> Hi,
> 
> the extcode spkg lacks a SPKG.txt, and has no description in 
> http://www.sagemath.org/packages/standard/.
> 
> Looking at its content shows:
> - jsmath (why isn't it in a proper spkg?)
> - things for the notebook (why isn't it in the sagenb spkg?)
> - something about a mac app (shouldn't it rather go in a sagemac spkg which 
> would be only installed on that platform?)

I have no problem making the Mac app into a separate spkg.

> - very random stuff.

Are you sure it's not pseudo-random?  :-) 

-Ivan

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [sage-devel] New sage-mode release fixing breakage on Sage 5.7

[Ivan Andrus]

No problem.  I know how hard writing a bug report can be.  I'm just glad it is 
useful for people.  Now if I could only get someone to review it…  :-)

-Ivan

On Mar 13, 2013, at 2:28 AM, martin  wrote:

> Hi Ivan!
> 
> I'd just like to send you a big THANK YOU for fixing the emacs mode with 5.7. 
>  In fact, I didn't upgrade sage just because of this...  (I was too busy to 
> drop you a line, sorry.)
> 
> Thanks again,
> 
> Martin

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [sage-devel] Google groups suck

[Ivan Andrus]

FWIW, I saw all of them.  Sadly I can't help you.

-Ivan

On Mar 9, 2013, at 1:36 PM, Stephen Montgomery-Smith  
wrote:

> This is the 4th time I tried sending this message.  I think it gets
> flagged as spam by google.
> 
> I have a problems building docs on sage-5.8.beta4.  On FreeBSD, the doc
> creation process freezes.  I cannot tell you where, because the text
> must be flagged as spam.  If this when gets through, I'll try sending it
> as a follow up.

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[sage-devel] New sage-mode release fixing breakage on Sage 5.7

[Ivan Andrus]

Dear Sage Emacs Users,

I finally made a new official release of sage-mode v0.9.  This includes fixes 
for working with the new ipython.  Without these changes tab completion is 
broken in Sage 5.7 and later.  Because of this breakage I have changed the 
ticket from enhancement to defect. *gasp*  

People have been reluctant to review the upgrade ticket #13182 in the past, but 
please consider reviewing it so that poor emacs users don't have to switch to a 
terminal to use Sage.  Such inconveniences have been known to greatly anger the 
Flying Spaghetti Monster!


Thanks in advance,
Ivan

P.S. #3007 should be an easy review as the bug was already fixed independently. 
 

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [sage-devel] Re: GSOC 2013

[Ivan Andrus]

On Mar 8, 2013, at 3:27 AM, P Purkayastha  wrote:

> On 03/08/2013 05:43 PM, mmarco wrote:
>> IIRC, the call for projects of Google summer of code was last year
>> around march or april. Should we start to get prepared for this?
>> 
>> As a suggestion for possible projects, i would propose the writing of
>> a windows GUI program that handles the virtual machines (set them up
>> properly, handles upgradings, checks the availability of ports and
>> decides if the VM should be launched in headless mode...)
>> 
>> It sounds like a project that can be done in a summer, and can be
>> really useful to spread sage among windows users.
>> 
> 
> This is too little I think. The following can be added to it

I don't know anything about Windows programming, but I don't think this is a 
trivial project.  As evidenced partly by the fact that no one has done it yet 
(I tried to convince my brother to do it once).  I think a basic solution might 
be pretty easy, but if you really make it robust with respect to firewall 
settings, getting data in and out, upgrading the vm, etc., I think it could be 
quite a lot of work.  But perhaps not enough for a whole summer, I don't know.

Even though I never use Windows, I think this would be a good project for Sage.

> 1. Fix the Mac application. See
> http://ask.sagemath.org/question/2322/trouble-logging-into-notebook
> for what currently happens on a Mac

I'm fairly certain this is fixed in sage-5.8.beta0.  Sorry, I haven't been 
keeping up with ask.sagemath.org as well as I should.  Though to be honest I 
might have missed it anyway since it's not tagged with Mac App or similar.  

> 2. Open sage to the worksheet when double clicking on sws files. This is 
> already mostly done for Mac, and should be done for Linux too :)

The problem with this is that someone with the expertise to make a good Windows 
GUI might not be able to work on Linux (or Mac).  But perhaps they could help 
with the cygwin port?

-Ivan

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [sage-devel] print when defining a symbolic function with "f(x) = ..."?

[Ivan Andrus]

On Mar 6, 2013, at 10:32 AM, Dan Drake  wrote:

> Recently in a different thread here [1], someone accidentally clobbered
> a Python builtin with a symbolic function:
> 
> sage: t = (1,2,3)
> sage: len(t) = 4
> 
> ...which overwrites t and the Python builtin len. 
> 
> I have a patch at #14231 that, at Nils Bruin's suggestion, *always*
> prints when defining a symbolic function via the preparser:
> 
> sage: f(u,v)=u+v
> Defining symbolic function f and symbolic variables u,v
> 
> This makes it easier to catch typos such as "sin(t) = 0" when you want
> "sin(t) == 0". This seems reasonable to me; I taught the MAA PREP
> workshop on Sage last summer, and symbolic functions and variables were
> a tricky concept. The new behavior would at least tell the user what the
> preparser is doing behind the scenes.
> 
> This is a change in behavior, though, and will require fixing a lot of
> doctests. Comments welcome.

Would it be possible to print the warning only if the session is interactive.  
Then you wouldn't have to change doctests and wouldn't have to see the warning 
when running scripts.

-Ivan

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [sage-devel] Which Development Enviroment

[Ivan Andrus]

On Feb 25, 2013, at 6:27 AM, Jesus Torrado  wrote:

> Hey,
> 
> On Monday, February 25, 2013 12:40:40 PM UTC+1, jason wrote:
> I typically use emacs or the online notebook.  I've used Eclipse before 
> as well. 
> 
> Me too. I normally prototype in the notebook and move to a file and work in 
> emacs when the size of the code gets big enough.
> 
> In case it is useful, in order for emacs to use the "python mode" (syntax 
> highlighting, tabs, etc.) with a ".sage" file, it is enough to add this line 
> to your "~/.emacs":
> 
> (setq auto-mode-alist (cons '("\\.sage\\'" . python-mode) auto-mode-alist))
> 
> Cheers,
> Jesús Torrado

You should also know that there is sage-mode (which I maintain) which adds some 
niceties specific to Sage.  It's available via 

sage -i sage_mode

It will give instructions for how to install it in your .emacs.  Unfortunately, 
the latest version needs to be reviewed [1] before it can installed in that way 
(hint, hint).  At the moment I suggest you install sage-mode with

sage -i http://boxen.math.washington.edu/home/iandrus/sage_mode-0.8.spkg


If you don't want to use Emacs either, you might check out Cantor [2] which I 
have not used, but looks interesting.

-Ivan

[1] http://trac.sagemath.org/sage_trac/ticket/13182
[2] http://edu.kde.org/cantor/

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [sage-devel] Please test this if you have OS X 10.8

[Ivan Andrus]

On Feb 12, 2013, at 3:15 PM, Michael Welsh  wrote:
> On 13/02/2013, at 11:09 AM, Ivan Andrus  wrote:
>> On Feb 12, 2013, at 2:17 PM, Michael Welsh  wrote:
>> 
>>> On 13/02/2013, at 9:53 AM, kcrisman  wrote:
>>>> Hi!  Thanks to very hard work by Ivan Andrus, we have Sage double-clicking 
>>>> sws files on Mac.  We just need one more test to make it complete.
>>>> 
>>>> If you DO have OS X 10.8 Mountain Lion but have NOT ever made something 
>>>> that makes sws files open with Sage.app on a double-click, please 
>>>> download 
>>>> http://sage.math.washington.edu/home/palmieri/misc/sage-Sage-testing-doubleclick-x86_64-Darwin.dmg
>>>>  
>>>> and try it out.  We particularly would like people who don't even have 
>>>> Sage.app to try this, since with multiple versions of Sage.app there can 
>>>> be 
>>>> natural confusion as to which one is supposed to open the file, though in 
>>>> principle this should work there as well.  Thanks to John Palmieri for 
>>>> helping with this.
>>>> 
>>>> - kcrisman
>>> 
>>> It worked fine, though I had Sage open already and that caused some issues. 
>>> I've never use a .app on this machine or even sws files. The app that I 
>>> just copied on is the only thing that can open it (according to the 
>>> right-click menu)
>> 
>> What issues did it cause?
> When I quit the app, it killed the notebook server I had running. As the sws 
> file I double-clicked was saved a few seconds beforehand from the running 
> worksheet, that confused me.

Ah, I see how that could be confusing.  FWIW, if you hold option while 
quitting, it won't kill the server.  Maybe I could make it more obvious what 
will happen…  Or maybe it should warn you, perhaps only if it didn't start the 
server itself.

> As did the "your server is starting up" tab, which IMO should go away when 
> the server actually starts.

I agree.  Unfortunately, I'm not sure how to get rid of it without writing some 
applescript for every different browser out there.  But maybe that wouldn't be 
so bad.  Any suggestions on how to improve the wording etc. in meantime would 
be appreciated.

>> And what do you mean by Sage was already open?  It should handle a notebook 
>> server running without any problems.
> I had a notebook server running. It handled it fine by taking it over, which 
> was not entirely what I expected.

I see.

Thanks,
Ivan

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [sage-devel] Please test this if you have OS X 10.8

[Ivan Andrus]

On Feb 12, 2013, at 2:25 PM, Benjamin Jones  wrote:
> On Tue, Feb 12, 2013 at 12:53 PM, kcrisman  wrote:
>> Hi!  Thanks to very hard work by Ivan Andrus, we have Sage double-clicking
>> sws files on Mac.  We just need one more test to make it complete.
>> 
>> If you DO have OS X 10.8 Mountain Lion but have NOT ever made something that
>> makes sws files open with Sage.app on a double-click, please download
>> http://sage.math.washington.edu/home/palmieri/misc/sage-Sage-testing-doubleclick-x86_64-Darwin.dmg
>> and try it out.  We particularly would like people who don't even have
>> Sage.app to try this, since with multiple versions of Sage.app there can be
>> natural confusion as to which one is supposed to open the file, though in
>> principle this should work there as well.  Thanks to John Palmieri for
>> helping with this.
>> 
>> - kcrisman
> 
> Works for me (OS X 10.8.2). I've never installed any .app Sage distro
> on this particular machine before. I downloaded this one, dragged to
> /Applications, waiting quite a while, and then tried double clicking a
> sws I had laying around. Worked perfectly. Nice work!
> 
> The helpful messages that pop up along the way have really improved
> too! I think this will go a long way to getting new folks started with
> Sage on OS X.

Thanks for testing.  Hopefully not just new users will like it.  :-)

-Ivan

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [sage-devel] Please test this if you have OS X 10.8

[Ivan Andrus]

On Feb 12, 2013, at 1:59 PM, Michael Welsh  wrote:
> On 13/02/2013, at 9:53 AM, kcrisman  wrote:
>> 
>> We particularly would like people who don't even have 
>> Sage.app to try this, since with multiple versions of Sage.app there can be 
>> natural confusion as to which one is supposed to open the file, though in 
>> principle this should work there as well.
> 
> Just to confirm: sage.app is different from self-compiled versions?

You can build the app yourself.  It's a GUI shell that you can use to manage 
Sage.  e.g. There is a menu item to start and stop the server, to start new 
shell sessions etc.

-Ivan

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [sage-devel] Please test this if you have OS X 10.8

[Ivan Andrus]

On Feb 12, 2013, at 2:17 PM, Michael Welsh  wrote:

> On 13/02/2013, at 9:53 AM, kcrisman  wrote:
>> Hi!  Thanks to very hard work by Ivan Andrus, we have Sage double-clicking 
>> sws files on Mac.  We just need one more test to make it complete.
>> 
>> If you DO have OS X 10.8 Mountain Lion but have NOT ever made something 
>> that makes sws files open with Sage.app on a double-click, please 
>> download 
>> http://sage.math.washington.edu/home/palmieri/misc/sage-Sage-testing-doubleclick-x86_64-Darwin.dmg
>>  
>> and try it out.  We particularly would like people who don't even have 
>> Sage.app to try this, since with multiple versions of Sage.app there can be 
>> natural confusion as to which one is supposed to open the file, though in 
>> principle this should work there as well.  Thanks to John Palmieri for 
>> helping with this.
>> 
>> - kcrisman
> 
> 
> It worked fine, though I had Sage open already and that caused some issues. 
> I've never use a .app on this machine or even sws files. The app that I just 
> copied on is the only thing that can open it (according to the right-click 
> menu)

What issues did it cause?  And what do you mean by Sage was already open?  It 
should handle a notebook server running without any problems.

-Ivan

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [sage-devel] New iOS app is up

[Ivan Andrus]

On Nov 12, 2012, at 3:57 PM, Jason Grout  wrote:

> On 11/11/12 5:09 PM, Ivan Andrus wrote:
> 
> Ivan: is there an easy way to reevaluate a computation?  That is particularly 
> useful for interacts.  If I click on a computation in the list, it opens up 
> the window for editing and evaluating, but the evaluate button doesn't seem 
> to appear until I actually edit the computation, so I find myself adding all 
> sorts of empty lines and things to be able to evaluate a computation again.

I finally got around to fixing this.  The app was just approved so it should be 
available for update shortly.  I also added the ability to choose a different 
computation engine (e.g. GAP, maxima, etc.)

-Ivan

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.

Re: [sage-devel] Android/iOS apps

[Ivan Andrus]

I haven't looked at it.  The free version doesn't have a keyboard and I just 
have a hard time spending $3 for the app, just to try out the keyboard.  
Looking at the screen shots is definitely interesting.  Has anyone seen other 
keyboards that they like?

I've been meaning to improve the keyboard for some, but haven't got around to 
it yet.  Partly because I'm interesting in what William is going to release 
with Salv.us, and partly because it's not simply a matter of coding.  I think 
it will take a lot of playing around to find a really nice keyboard (if such a 
thing is actually possible on the iPhone).  And arguably an iPad-optimized 
version is more important.

-Ivan

On Jan 12, 2013, at 2:49 AM, kcrisman  wrote:

> So at the Joint Meetings, someone was saying how much they like the Wolfram 
> Alpha app.  Apparently a little keyboard comes down to enter stuff in and 
> this person really liked that.  (I have no idea if this is actually a good 
> idea.)  Has anyone (such as Volker or Ivan) experimented with comparing that 
> app and ours?  Not because we should do what they do, but because it's useful 
> to think about such things.
> 
> Happy brainstorming!
> - kcrisman
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "sage-devel" group.
> To post to this group, send email to sage-devel@googlegroups.com.
> To unsubscribe from this group, send email to 
> sage-devel+unsubscr...@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel?hl=en.
>  
>  

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.

Re: [sage-devel] Preferred way to patch the Mac app?

[Ivan Andrus]

On Jan 5, 2013, at 8:59 PM, Nicholas Kirchner  wrote:

> I've taken a look at trac ticket 11026, and I'll comment there as soon as my 
> account is approved.  For now:
> 
> I'm on OS X Lion, using the Browser bundled with Sage.app.
> 
> 1. It does start and stop the server.  Starting the server initializes three 
> python2.7 processes.  Two of them are ~100MB and one is ~5MB.  Stopping the 
> server or exiting Sage.app terminates the two larger of these, while leaving 
> the ~5MB python2.7 process running.  This last running process is a problem 
> for deleting/renaming Sage.app.

Can you tell what the process is?  There is a sage-cleaner, that might hang 
around for a while.  On my machine that's the python2.7 process that takes 
about 5MB.  I think it should go away after a while.  But I hadn't run into 
problems with deleting or renaming Sage.app before, probably because I use an 
alternate sage executable.

> 2. Right-clicking a .txt file and selecting Sage.app to open it results in 
> the text of the file being placed above the first input cell without 
> linebreaks.  That is, a text file consisting of
> 
> """Hello.  I'm a 
> sample text file in Sage.app"""
> 
> ends up being opened with the text "Hello.  I'm a sample text file in 
> Sage.app", with the first input cell following the text.  I'm not quite sure 
> whether this is the intent or not, and I don't imaging using this 
> functionality, personally.

Yes.  IIRC the format of the text file should be the same as you see when 
pressing the Edit button, namely all cells should be in triple braces like:

{{{
f=x^2-2x+1
}}}

{{{
f.factor()
}}}

> 3. Double-clicking a .sws file saved via Sage.app's File->Save As menu does 
> activate Sage.app.  It pulls up an error page:
> 
> "There was an error uploading the worksheet. It could be an old unsupported 
> format or worse. If you desperately need its contents contact the 
> sage-support group and post a link to your worksheet. Alternatively, an sws 
> file is just a bzip2 tarball; take a look inside!"

You are using the Sage.app browser and File->Save As from the applications 
menu?  I think that just saves the html.  In fact, I deleted that item from the 
menu in a more recent version since it was confusing.

> Instead using the in-browser's File->Save worksheet to file... does not 
> appear to save anything.

I see that you are right.  I'll put that on my list of things to fix.  However, 
it might be best to use a real browser since I haven't gotten the browser 
portion of Sage.app very polished yet (as you have witnessed).  It doesn't seem 
like there is much use for it anyway, since most people are going to use the 
system browser since it will have way more features.  

Personally, I like the idea of having a dedicated browser for Sage, but it 
hasn't worked out in practice (yet).  If you would like to see it get better 
(i.e. usable), then I can devote some time to it.  Feel free to open tickets if 
you would like.  Just make sure to set me (iandrus) as the owner or at least cc 
me.

Thanks for taking the time to look at all this.

-Ivan

> On Saturday, January 5, 2013 3:25:01 AM UTC-6, Ivan Andrus wrote:
> I know I've fixed this before.  It took a while to find because it made it 
> into the patch at #11026 (which would be a great ticket to have finished).  
> It's there because the issue came up during testing.  So if you have some 
> time it would be great to get it reviewed.  IIRC it only needed to be tested 
> on (Mountain) Lion.
> 
> http://trac.sagemath.org/sage_trac/ticket/11026
> 
> There are a few other Mac app tickets that need review.  If you have some 
> energy to review them, I have some time to fix whatever issues you find.  I 
> also have some other patches locally that I need to put on trac.
> 
> http://trac.sagemath.org/sage_trac/ticket/10555
> http://trac.sagemath.org/sage_trac/ticket/10556
> 
> Thanks,
> Ivan
> 
> On Jan 5, 2013, at 7:19 AM, Nicholas Kirchner  wrote:
> 
>> I've been having the problem that the Mac app won't stop the sage server 
>> when I ask it to.  I know the problem: the Mac app source code references 
>> .sage/sage_notebook.sagenb/twistd.pid, whereas it should reference 
>> sagenb.pid.
>> 
>> The instructions at "Walking Through the Development Process" do not seem 
>> quite suitable for patching the app, which resides in 
>> SAGE_ROOT/devel/ext-main/sage/ext/mac-app.  What's the preferred way to 
>> create a patch for a Trac ticket on the Mac application?
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "

Re: [sage-devel] Preferred way to patch the Mac app?

[Ivan Andrus]

I know I've fixed this before.  It took a while to find because it made it into 
the patch at #11026 (which would be a great ticket to have finished).  It's 
there because the issue came up during testing.  So if you have some time it 
would be great to get it reviewed.  IIRC it only needed to be tested on 
(Mountain) Lion.

http://trac.sagemath.org/sage_trac/ticket/11026

There are a few other Mac app tickets that need review.  If you have some 
energy to review them, I have some time to fix whatever issues you find.  I 
also have some other patches locally that I need to put on trac.

http://trac.sagemath.org/sage_trac/ticket/10555
http://trac.sagemath.org/sage_trac/ticket/10556

Thanks,
Ivan

On Jan 5, 2013, at 7:19 AM, Nicholas Kirchner  wrote:

> I've been having the problem that the Mac app won't stop the sage server when 
> I ask it to.  I know the problem: the Mac app source code references 
> .sage/sage_notebook.sagenb/twistd.pid, whereas it should reference sagenb.pid.
> 
> The instructions at "Walking Through the Development Process" do not seem 
> quite suitable for patching the app, which resides in 
> SAGE_ROOT/devel/ext-main/sage/ext/mac-app.  What's the preferred way to 
> create a patch for a Trac ticket on the Mac application?
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "sage-devel" group.
> To post to this group, send email to sage-devel@googlegroups.com.
> To unsubscribe from this group, send email to 
> sage-devel+unsubscr...@googlegroups.com.
> Visit this group at http://groups.google.com/group/sage-devel?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.

Re: [sage-devel] Re: Disable the "trailing whitespace" patchbot plugin

[Ivan Andrus]

On Nov 25, 2012, at 1:01 AM, Keshav Kini  wrote:

> Travis Scrimshaw  writes:
>> Hey,
>>   I'd be happy with A), but perhaps we could have an option D) where
>> when we upload (or merge) patches into sage, we automatically strip
>> all whitespace in the patch file?
> 
> This will get nasty once we stop using patch files and switch to git.
> Commits should not be invisibly edited after they've been made and
> "approved" for some value of "approved".


But we can have a commit hook, right?  It could just refuse to commit with 
trailing whitespace.  Or maybe it could even offer to fix it for you.

-Ivan

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.

Re: [sage-devel] Disable the "trailing whitespace" patchbot plugin

[Ivan Andrus]

On Nov 24, 2012, at 3:38 PM, Volker Braun  wrote:

> On Saturday, November 24, 2012 2:11:54 PM UTC, Ivan Andrus wrote:
> I disagree.  Perhaps I am alone in this, but I often (used to) move to the 
> end of the line, go back a few characters (to get inside parenthesis or 
> something), and start typing.  
> 
> http://www.emacswiki.org/emacs/NavigatingParentheses
> 
> Or press C-e M-\ to got to end and remove whitespace. Or roll your own macro. 
> Making the editor do what you prefer seems much more straight-forward than 
> removing whitespace and then put it back in when you are finished editing.

Sure I can do that, but I'm happy with my setup now (I think this part is 
nearly a decade old).  And I don't know what you mean by "putting it back".  My 
point is simply that it can be annoying until you "fix" your editor.  And I 
don't think it's reasonable to assume that all Sage users have "fixed" their 
editors.  But definitely the policy (whatever it is in the end) should be 
enforced programmatically.

-Ivan

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.

Re: [sage-devel] Re: Disable the "trailing whitespace" patchbot plugin

[Ivan Andrus]

I disagree.  Perhaps I am alone in this, but I often (used to) move to the end 
of the line, go back a few characters (to get inside parenthesis or something), 
and start typing.  If there is trailing whitespace that I didn't know about I 
would be extremely annoyed because all my typing was in the wrong place.  
That's why I now show all trailing whitespace in my editor and have a draconian 
kill-all-trailing-whitespace-on-save policy.  It has caused very few problems 
for me.  I just have to remember to kill any hunks with whitespace only changes.

For those reasons I would love if we just got rid of trailing whitespace 
everywhere.  Unfortunately, as you have mentioned, changing trailing whitespace 
causes hg/git to think that the line has changed thereby messing up blame etc.  
If there was a way to remove all whitespace from every revision ever when we 
change over to git, I think that would be awesome.  I have no idea how much 
work it would be though, and there's always the slight chance you might break 
something that way.

That said, I think the blame issue is more important than not having trailing 
whitespace, so I think C is a pretty good option.

-Ivan

On Nov 24, 2012, at 1:05 PM, Volker Braun  wrote:

> You talk about trailing whitespace as if getting rid of it were a worthy goal 
> in itself. It is not. Humans don't care about trailing whitespace, we don't 
> see it unless you misconfigure your editor. Its purely for the benefit of 
> automated merge tools. If we disallow patch hunks that change trailing 
> whitespace only then the needs of merge tools are satisfied and there is no 
> further need for any policy beyond that.
> 
> 
> On Saturday, November 24, 2012 11:55:24 AM UTC, P Purkayastha wrote:
> C) We care about trailing whitespace. No new patches should introduce 
> trailing whitespace in modified lines. But patch hunks that ONLY change 
> trailing whitespace are disallowed. It is of course encouraged to get 
> rid of trailing whitespace in the code surrounding the lines your patch 
> touches. 
> 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.

Re: [sage-devel] Re: How to proceed to reduce Sage's memory leaking?

[Ivan Andrus]

On Nov 17, 2012, at 9:56 PM, Nils Bruin  wrote:

> On Nov 17, 12:20 pm, Ivan Andrus  wrote:
> 
>> At one point I had the goal of creating a suppressions file so that the 
>> doctests passed "cleanly".  I'm sure some of the suppressions were actual 
>> problems, but it would at least allow you to find new problems.  I still 
>> have the scripts that I used to collect and remove duplicate suppressions.  
>> I would be happy to run them again if people thought it would be useful.  
>> Sadly my machine isn't the fastest, so it takes quite a while (running all 
>> the doctests under valgrind is _slow_).  I never did make it all the way 
>> through the test suite.  But especially if I knew the likely areas it 
>> wouldn't be too hard to run some overnight and see what turns up.
> 
> Anything that has to do with libsingular. The problem is that OTHER
> tests may well exercise this code much better than libsingular's own
> doctests.
> 
> However, with an unmodified libsingular it's unlikely you'll find
> anything. omalloc allocates pages of system memory and then manages
> pieces of it by itself. So as far as valgrind is concerned, there is
> relatively little allocation/deallocation activity. I think you can go
> further and tell valgrind about the functioning of alternative memory
> managers. That would improve diagnostics a little. But if the compact
> memory layout of omalloc (the compactness is its purpose) isn't
> changed, you still have a good chance that an access-after-free refers
> to perfectly valid memory (a block that now has been reallocated for a
> different purpose)
> 
> This is the issue I'm trying to address with malloc-version of
> singular. Combined with a malloc implementation that puts blocks on
> separate pages, on the edge of the page, unmaps any page upon
> deallocation, and tries to avoid reusing or using adjacent logical
> pages means that any illegal access is almost sure to segfault. BSD's
> gmalloc does that. It seems glibc's malloc with MALLOC_CHECK_=2 or 3
> does at least a bit of that.
> 
> The real problem here is that we (Simon, Volker or I) don't know for
> sure what the refcount and deletion protocols are for Singular
> objects. It seems to be the kind of thing that is folklore inside the
> Singular group but was never properly documented. Singular was not
> designed to be a clean library, but it does seem to be a direction
> Singular is heading, so perhaps this might sometime get documented
> properly. I just think Sage can't wait for the decade or so that this
> is probably going to take.

Thanks for the explanation.  That makes sense.  It sounds like there's not much 
valgrind will help with, but I'll give it a go anyway.

-Ivan

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.

Re: [sage-devel] Re: How to proceed to reduce Sage's memory leaking?

[Ivan Andrus]

On Nov 17, 2012, at 8:01 PM, Nils Bruin  wrote:

> On Nov 17, 1:01 am, Jeroen Demeyer  wrote:
>> On 2012-11-16 19:35, Nils Bruin wrote:> On Nov 15, 11:59 pm, Jeroen Demeyer 
>>  wrote:
>> After adding every single ticket, there is reason to expect differently.
>> This stuff is *so sensitive* to changes, even changes which look
>> completely unrelated.
> That's why the effort to do strict checking on memory management
> should help (and it was in that light that I interpreted your
> request). I think the sensitivity comes from the fact that you have to
> wait for the coincidence that a freed-too-early location gets reused
> and *then* written in its own role (i.e., actual corruption).
> 
> gc.collect() all the time should make deletions a little more
> predictable and a very strict malloc/free should detect the problem
> sooner. I'm afraid that MALLOC_CHECK_ isn't as good as BSD's gmalloc,
> where even an access-after-free is a segfault (and many out-of-bound
> accesses too).
> 
> Once one gets a little better in writing valgrind suppressions it's
> easy to let valgrind produce less irrelevant output, so perhaps
> there's a future for that. Or perhaps a tool to query and sort
> valgrind reports after the fact (basically filter after the fact).
> Perhaps it's time for William to hire someone again who is really good
> at this stuff, because mathematically it's utterly uninteresting work
> (and it really is finding and cleaning other people's mess)

At one point I had the goal of creating a suppressions file so that the 
doctests passed "cleanly".  I'm sure some of the suppressions were actual 
problems, but it would at least allow you to find new problems.  I still have 
the scripts that I used to collect and remove duplicate suppressions.  I would 
be happy to run them again if people thought it would be useful.  Sadly my 
machine isn't the fastest, so it takes quite a while (running all the doctests 
under valgrind is _slow_).  I never did make it all the way through the test 
suite.  But especially if I knew the likely areas it wouldn't be too hard to 
run some overnight and see what turns up.

-Ivan

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.

Re: [sage-devel] New iOS app is up

[Ivan Andrus]

On Nov 12, 2012, at 4:16 PM, Ivan Andrus  wrote:

> On Nov 12, 2012, at 3:57 PM, Jason Grout  wrote:
> 
>> On 11/11/12 5:09 PM, Ivan Andrus wrote:
>>> A substantial rewrite of the iOS app is in the iTunes store [1].  It
>>> uses the new server and supports interacts!  It handles output a
>>> little different (it uses a web page instead of plain text or image)
>>> so it can also handle more than one image as well as text plus image.
>>> The only problem that I know of is that it doesn't shrink the picture
>>> to be able to view it nicely on the iPhone—instead you have to scroll
>>> around.  I'm pretty sure this can be fixed, I just didn't want to
>>> delay the release any longer since I was having some weird issues
>>> getting it working.
>>> 
>>> Anyway, let me know if you experience any problems with it, and as
>>> always I'm interested in feature requests as well.  You can reply
>>> here, to me personally, or open a ticket on bitbucket [2], whichever
>>> you prefer.
>> 
>> This is awesome.  Thanks again Ivan!
>> 
>> As soon as the android app migrates to the new cell server, we'll retire 
>> aleph1.sagemath.org.
>> 
>> Ivan: is there an easy way to reevaluate a computation?  That is 
>> particularly useful for interacts.  If I click on a computation in the list, 
>> it opens up the window for editing and evaluating, but the evaluate button 
>> doesn't seem to appear until I actually edit the computation, so I find 
>> myself adding all sorts of empty lines and things to be able to evaluate a 
>> computation again.
> 
> 
> There isn't currently.  I did find myself editing in order to reevaluate, but 
> I figured that was because of the fact that I was testing things rather than 
> actually using it.  You are right though about interacts.  
> 
> One problem is that there isn't much room on the iPhone to add another 
> button.  I could make the Evaluate button always available on the iPad (which 
> is where you use it right?).  Perhaps if it contains the string "@interact" I 
> could make Evaluate the default when you open it up.  That probably makes 
> sense and should be an easy improvement.

Actually, maybe it makes sense all the time (not just for interacts) because 
you could have used the Share button from the main screen if that's what you 
wanted to do.

-Ivan

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.

Re: [sage-devel] New iOS app is up

[Ivan Andrus]

On Nov 12, 2012, at 3:57 PM, Jason Grout  wrote:

> On 11/11/12 5:09 PM, Ivan Andrus wrote:
>> A substantial rewrite of the iOS app is in the iTunes store [1].  It
>> uses the new server and supports interacts!  It handles output a
>> little different (it uses a web page instead of plain text or image)
>> so it can also handle more than one image as well as text plus image.
>> The only problem that I know of is that it doesn't shrink the picture
>> to be able to view it nicely on the iPhone—instead you have to scroll
>> around.  I'm pretty sure this can be fixed, I just didn't want to
>> delay the release any longer since I was having some weird issues
>> getting it working.
>> 
>> Anyway, let me know if you experience any problems with it, and as
>> always I'm interested in feature requests as well.  You can reply
>> here, to me personally, or open a ticket on bitbucket [2], whichever
>> you prefer.
> 
> This is awesome.  Thanks again Ivan!
> 
> As soon as the android app migrates to the new cell server, we'll retire 
> aleph1.sagemath.org.
> 
> Ivan: is there an easy way to reevaluate a computation?  That is particularly 
> useful for interacts.  If I click on a computation in the list, it opens up 
> the window for editing and evaluating, but the evaluate button doesn't seem 
> to appear until I actually edit the computation, so I find myself adding all 
> sorts of empty lines and things to be able to evaluate a computation again.


There isn't currently.  I did find myself editing in order to reevaluate, but I 
figured that was because of the fact that I was testing things rather than 
actually using it.  You are right though about interacts.  

One problem is that there isn't much room on the iPhone to add another button.  
I could make the Evaluate button always available on the iPad (which is where 
you use it right?).  Perhaps if it contains the string "@interact" I could make 
Evaluate the default when you open it up.  That probably makes sense and should 
be an easy improvement.

-Ivan

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.

[sage-devel] New iOS app is up

[Ivan Andrus]

A substantial rewrite of the iOS app is in the iTunes store [1].  It uses the 
new server and supports interacts!  It handles output a little different (it 
uses a web page instead of plain text or image) so it can also handle more than 
one image as well as text plus image.  The only problem that I know of is that 
it doesn't shrink the picture to be able to view it nicely on the 
iPhone—instead you have to scroll around.  I'm pretty sure this can be fixed, I 
just didn't want to delay the release any longer since I was having some weird 
issues getting it working.

Anyway, let me know if you experience any problems with it, and as always I'm 
interested in feature requests as well.  You can reply here, to me personally, 
or open a ticket on bitbucket [2], whichever you prefer.

-Ivan

[1] https://itunes.apple.com/us/app/sage-math/id496492945
[2] https://bitbucket.org/gvol/sage-iphone-app/issues?status=new&status=open

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.

Re: [sage-devel] Remove OSX 10.4 PPC from supported platforms

[Ivan Andrus]

On Sep 17, 2012, at 4:00 PM, William Stein wrote:

> On Monday, September 17, 2012, Volker Braun  wrote:
> > Two weeks ago I tried to get access to a OSX PPC machine, and we haven't 
> > made any progress yet. Thats just not maintainable. I've been playing 
> > trac/email tag with Karl-Dieter for two weeks but we still haven't been 
> > able to fix the blas linkage. Basically, the OSX PPC binaries that we build 
> > are not correctly linked and only work by accident. We can either freeze 
> > the current state and never touch the blas again (sucks if you have a 
> > modern processor) or we'll have to let go of the ancient stuff. We can 
> > still run Sage on OSX PPC as we manage to iron out the kinks, but this 
> > shouldn't be a blocker for ATLAS to move forward, say.
> >
> 
> +1. We shouldn't hold sage *back* to support 10.4 at this point.

But we should we still try to support 10.4 if it's not too difficult, right?  
For example, when building the Mac app, there are certain APIs that appear in 
10.5.  I have been able to get by without them, but a few things would be a 
little easier if I could use them.

-Ivan

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.

[sage-devel] Re: Sage-mode 0.8 now ready

[Ivan Andrus]

I finally tagged and released sage-mode 0.8 and marked the trac ticket #13182 
for review.  I thought I had done this earlier, so please review it if you use 
sage-mode.  I also added one tiny feature—support for sagetex in org-mode 
exporting to pdf, so please reinstall the spkg before reviewing.

I think this is a fairly important update since it allows using the latest 
Emacs for sage development.

As always, please send me any bug reports or feature requests.

Thanks,
Ivan

On Jul 12, 2012, at 11:05 PM, Ivan Andrus wrote:

> I have finally gotten sage-mode working (I think) with the new python.el 
> which will be included in Emacs 24.2.  For that reason I am ready to 
> "release" it to a wider audience, in preparation for sage-mode becoming 
> standard.  My plans are that 0.8 become an optional package after some 
> testing and then, depending on bug reports/feature requests, 0.8 or 0.9 would 
> become a standard package.
> 
> I'm asking for any one who uses sage-mode regularly to please try the new 
> spkg with
> 
> sage -f http://boxen.math.washington.edu/home/iandrus/sage_mode-0.8.spkg
> 
> If you have any problems or suggestions let me know either on sage-devel, on 
> bitbucket [1], or on trac ticket #13182 [2].  Since I use the very latest 
> Emacs I would especially appreciate people with older versions to test to 
> make sure I didn't break something that way.
> 
> Note that the name has changed from sage-mode-0.7 to sage_mode-0.8 (hyphen to 
> underscore) since sage uses the hyphen to separate the package from the 
> version.  That's why currently `sage -i sage-mode` doesn't work, but `sage -i 
> sage` does!
> 
> Mostly 0.8 consists of bug fixes and new python.el support, but there are a 
> few new features as well:
> 
> 1. Support for SageTeX when using AUCTeX—automatically detects when Sage 
> needs to be run.
> 2. sage-fix-doctest-at-point which is just fun (thanks to Martin Albrecht for 
> the idea).
> 
> Thanks,
> Ivan
> 
> [1] https://bitbucket.org/gvol/sage-mode/issues?status=new&status=open
> [2] http://trac.sagemath.org/sage_trac/ticket/13182

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.

Re: [sage-devel] Re: Need developer account on OSX 10.4 PPC (or remove from supported platforms)

[Ivan Andrus]

On Sep 4, 2012, at 11:39 AM, Dima Pasechnik wrote:
> On 2012-09-02, Volker Braun  wrote:
>> --=_Part_2609_10642519.1346583022793
>> Content-Type: text/plain; charset=ISO-8859-1
>> 
>> Something in our OSX 10.4 build uses the reference blas instead of the 
>> accelerate framework. See http://trac.sagemath.org/10508 for some heroic 
>> efforts by Karl-Dieter to debug this by word of mouth, but thats just not 
>> sustainable. We either need shell access for Sage developers to a OSX 10.4 
>> machine or remove it from the first-tier supported platforms.
> 
> I have a PPC G4 laptop running OSX 10.5 (I don't think I can get it to
> run 10.4). I can let you guys use it remotely, although it's not going
> to be very fast (as it's in Singapore).
> 
> I don't think 10.5 is too different from 10.4...

It's quite different, at least in terms of the Mac app.

-Ivan

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to 
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.

Re: [sage-devel] Re: sage startup time hasn't improved...

[Ivan Andrus]

I get around 2 seconds on my MacBook Pro (non-SSD) that's a couple years old.  
FWIW, sage -c is consistently 10% faster than `echo "" | sage`.

$ time sage -c 'print 3+2'
5

real0m1.809s
user0m1.158s
sys 0m0.705s
$ time echo "" | sage
--
| Sage Version 5.2, Release Date: 2012-07-25 |
| Type "notebook()" for the browser-based notebook interface.|
| Type "help()" for help.|
--
sage: sage: 
Exiting Sage (CPU time 0m0.05s, Wall time 0m0.05s).

real0m2.001s
user0m1.312s
sys 0m0.750s


I think we either need to make startup time a hard and fast rule for 
reviewing—which means we need an easy and consistent way to test—or we just 
forget about it and use something like sage-forker (except probably based on 
the new ipython).  I think the latter is going to give better performance, but 
startup time might still be important for other reasons that I'm not thinking 
of.  

-Ivan

On Aug 11, 2012, at 8:43 PM, Volker Braun wrote:

> I still don't understand why its so slow for you, on a recent machine Sage 
> startup with warm cache should be around 1s.  
> 
> Playing around with the startup a bit, I noticed that the notebook stuff 
> imports a lot during startup. Why do we need to import anything from the 
> notebook except the notebook() function? This seems wasteful. Cutting out the 
> notebook imports saves me about 1/4 of the startup time (from ~1s to 0.75s).
> 
> We also have a lot of stuff in the sys.path that causes many failed open() 
> calls upon startup as Python has to check every directory for modules. About 
> half of all are notebook-related python packages that have no use in 
> mathematics. These are also subdirectories of site-packages so they are 
> searched twice since site-packages is also is sys.path. Just getting rid of 
> packages that are only used in the notebook saves about a third of all open() 
> calls during startup. But on my laptop that only saves something on the order 
> of 0.01s, basically nothing. But if you have a slow file system then it might 
> make a difference.
> 
> 
> On Friday, August 10, 2012 8:51:17 PM UTC-4, William wrote:
> Hi, 
> 
> I'm sad that on a fast SSD repeatedly doing the following: 
> 
> wstein@geom:/usr/local/sage/sage-5.2$ time echo "" | ./sage 
> -- 
> | Sage Version 5.2, Release Date: 2012-07-25 | 
> | Type "notebook()" for the browser-based notebook interface.| 
> | Type "help()" for help.| 
> -- 
> sage: sage: 
> Exiting Sage (CPU time 0m0.03s, Wall time 0m0.03s). 
> 
> real0m1.902s 
> user0m1.428s 
> sys0m0.424s 
> 
> always outputs 1.9 seconds!   That test was < 1 second on sage.math 
> when I put in a doctest to make sure it didn't exceed that 1 second, 
> when we were trying to improve the sage startup time.  In the 
> intervening year (?), the test is ignored or gone, and the startup 
> time seems to have got a bit worse.  Dang. 
> 
> On another faster machine, I'm getting: 
> 
> wstein@combinat:/usr/local/sage/sage-5.2$ time echo "" | ./sage 
> -- 
> | Sage Version 5.2, Release Date: 2012-07-25 | 
> | Type "notebook()" for the browser-based notebook interface.| 
> | Type "help()" for help.| 
> -- 
> sage: sage: 
> Exiting Sage (CPU time 0m0.04s, Wall time 0m0.05s). 
> 
> real0m1.580s 
> user0m1.224s 
> sys0m0.356s 
> 
> 
> Any ideas? 
> 
> 
> 
> 
> William 
> 
> 
> 
> 
> -- 
> William Stein 
> Professor of Mathematics 
> University of Washington 
> http://wstein.org 
> 
> -- 
> -- 
> To post to this group, send an email to sage-devel@googlegroups.com
> To unsubscribe from this group, send an email to 
> sage-devel+unsubscr...@googlegroups.com
> For more options, visit this group at 
> http://groups.google.com/group/sage-devel
> URL: http://www.sagemath.org
>  
>  
>  


-- 
-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Re: Wanted: a reviewer for ticket #12503

[Ivan Andrus]

On Jul 16, 2012, at 8:13 PM, Dima Pasechnik wrote:
> On Tuesday, 17 July 2012 01:42:54 UTC+8, Ivan Andrus wrote:
> On Jul 16, 2012, at 3:16 PM, Dima Pasechnik wrote:
> 
>> On Monday, 16 July 2012 12:06:10 UTC+8, Kwankyu Lee wrote:
>> Hi,
>> 
>> This ticket is long abandoned at Trac without a reviewer.
>> 
>> http://trac.sagemath.org/sage_trac/ticket/12503
>> 
>> The feature that the patch provides is indispensable to me when I use 
>> command line interface of Sage. I think it is also very useful to you. Would 
>> you be a reviewer of the ticket?
>> 
>> comments there seem to indicate it's a duplicate of already closed #10289. 
>> Only by going to the latter one sees that it was a duplicate... :–)
>> 
>> By the way, is there a sorely missed by me feature of getting the next 
>> command in the history?
>> I.e. I often do something like this:
>> 
>> sage: A...
>> sage: B...
>> sage: C...
>> oops, wrong answer; editing code...
>> sage: A...
>> sage: B...
>> sage: C...
>> oops, wrong answer; editing code...
>> sage: A...
>> sage: B...
>> sage: C...
>> Good!
>> 
>> So I can navigate history to A, but once I am there and executed it, I want 
>> a quick way to go to B.
>> But it's not available...
> 
> That's the whole point of this patch, unless I'm misunderstanding what you 
> want.  Here's the workflow (after having bound keys appropriately).  
> 
> 1. Navigate your history to A
> 2. Type C-o (or whatever) and it will 
>   a. execute A 
>   b. take you to B automatically.  
> 
> Is this what you wanted?
> 
> More or less.
> Specifically, I want the same behaviour as in GAP. In GAP one can go to A 
> using (say) arrows keys. Then, after executing A, you get GAP prompt, just as 
> if you execute the "normal" command. But if you then hit arrow-down (i.e. 
> "next command" in history) you'll get to B.
> 
> In Sage executing A brings you to the bottom of the history (which I weird, 
> IMHO).

So execute normally but remember where you were in the history if you press 
down.  I've always found that a bit weird since if you press up you _lose_ your 
place.  But I grew up in a bash shell before a GAP shell. :-)  I'm sure such a 
thing would be easy by adding another function on top of this patch.  

FWIW, I think this should go in soon and have another patch to get the GAP 
behavior, since this has been languishing for quite a while. There should also 
be a section that basically says, do XYZ to get GAP behavior and WXY to get 
Magma behavior, etc.

-Ivan

-- 
-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Re: Wanted: a reviewer for ticket #12503

[Ivan Andrus]

On Jul 16, 2012, at 3:16 PM, Dima Pasechnik wrote:

> On Monday, 16 July 2012 12:06:10 UTC+8, Kwankyu Lee wrote:
> Hi,
> 
> This ticket is long abandoned at Trac without a reviewer.
> 
> http://trac.sagemath.org/sage_trac/ticket/12503
> 
> The feature that the patch provides is indispensable to me when I use command 
> line interface of Sage. I think it is also very useful to you. Would you be a 
> reviewer of the ticket?
> 
> comments there seem to indicate it's a duplicate of already closed #10289. 
> Only by going to the latter one sees that it was a duplicate... :–)
> 
> By the way, is there a sorely missed by me feature of getting the next 
> command in the history?
> I.e. I often do something like this:
> 
> sage: A...
> sage: B...
> sage: C...
> oops, wrong answer; editing code...
> sage: A...
> sage: B...
> sage: C...
> oops, wrong answer; editing code...
> sage: A...
> sage: B...
> sage: C...
> Good!
> 
> So I can navigate history to A, but once I am there and executed it, I want a 
> quick way to go to B.
> But it's not available...

That's the whole point of this patch, unless I'm misunderstanding what you 
want.  Here's the workflow (after having bound keys appropriately).  

1. Navigate your history to A
2. Type C-o (or whatever) and it will 
  a. execute A 
  b. take you to B automatically.  

Is this what you wanted?

-Ivan

-- 
-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Sage-mode 0.8 now ready

[Ivan Andrus]

I have finally gotten sage-mode working (I think) with the new python.el which 
will be included in Emacs 24.2.  For that reason I am ready to "release" it to 
a wider audience, in preparation for sage-mode becoming standard.  My plans are 
that 0.8 become an optional package after some testing and then, depending on 
bug reports/feature requests, 0.8 or 0.9 would become a standard package.

I'm asking for any one who uses sage-mode regularly to please try the new spkg 
with

sage -f http://boxen.math.washington.edu/home/iandrus/sage_mode-0.8.spkg

If you have any problems or suggestions let me know either on sage-devel, on 
bitbucket [1], or on trac ticket #13182 [2].  Since I use the very latest Emacs 
I would especially appreciate people with older versions to test to make sure I 
didn't break something that way.

Note that the name has changed from sage-mode-0.7 to sage_mode-0.8 (hyphen to 
underscore) since sage uses the hyphen to separate the package from the 
version.  That's why currently `sage -i sage-mode` doesn't work, but `sage -i 
sage` does!

Mostly 0.8 consists of bug fixes and new python.el support, but there are a few 
new features as well:

1. Support for SageTeX when using AUCTeX—automatically detects when Sage needs 
to be run.
2. sage-fix-doctest-at-point which is just fun (thanks to Martin Albrecht for 
the idea).

Thanks,
Ivan

[1] https://bitbucket.org/gvol/sage-mode/issues?status=new&status=open
[2] http://trac.sagemath.org/sage_trac/ticket/13182

-- 
-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] old sws file does not open

[Ivan Andrus]

On Jul 4, 2012, at 3:46 PM, Goutam Paul wrote:

> Really need the contents.
> 
> Got an error message:
> "There was an error uploading the worksheet. It could be an old
> unsupported format or worse. If you desperately need its contents
> contact the sage-support group and post a link to your worksheet.
> Alternatively, an sws file is just a bzip2 tarball; take a look
> inside!"
> 
> bunzip2 didn't show readable output.

FWIW, I didn't have any problems running it through bunzip2 and tar.  I include 
below the contents of worksheet.txt.  You should be able to create a new 
worksheet, hit the "Edit" button, paste it in, "Save Changes", and then 
evaluate all of your cells.

HTH,
Ivan


eve
system:sage

{{{id=0|
d = var('d')
P0=plot(d,0,0.5,color='black',linestyle=":")
P1=plot(sqrt(d-d^2),0,0.5,color='blue',linestyle="-")
P2=plot(0.5*d+0.5*sqrt(2*d-3*(d^2)), 0, 0.5,color='red',linestyle="-")
P3=plot(8*(sqrt(d-d^2))^4,0,0.5,color='blue',linestyle="--")
P4=plot(0.5*(d+sqrt(2*d-3*(d^2)))^3,0,0.5,color='red',linestyle="--")
P5=plot(128*(sqrt(d-d^2))^8,0,0.5,color='blue',linestyle="-.")
P6=plot(0.5*(d+sqrt(2*d-3*(d^2)))^6,0,0.5,color='red',linestyle="-.")
P=P0+P1+P2+P3+P4+P5+P6
P.axes_labels(['$D$', 'Advantage($D$)'])
show(P)
///
}}}

{{{id=1|
import numpy as np
import matplotlib.pyplot as plt

fig = plt.figure(figsize=(12, 6), dpi=300)
ax = fig.add_subplot(1,1,1)

plt.clf()

def P0(x):
return x
 
def P1(x):
return np.sqrt(x-x^2)

def P2(x):
return 0.5*x+0.5*np.sqrt(2*x-3*(x^2))

def P3(x):
return 4*(np.sqrt(x-x^2))^3

def P4(x):
return 0.5*(x+np.sqrt(2*x-3*(x^2)))^2

def P5(x): 
return (2^5)*(np.sqrt(x-x^2))^6

def P6(x):
return 0.5*(x+np.sqrt(2*x-3*(x^2)))^4

def P7(x): 
return (2^299)*(np.sqrt(x-x^2))^300

def P8(x):
return 0.5*(x+np.sqrt(2*x-3*(x^2)))^200

d = np.arange(0.0,0.5,0.001)

plt.plot(d,P0(d),'g:',linewidth=2,label="$D$")
plt.plot(d,P1(d),'b-',label="$A^{4 state}_{opt}(D)$")
plt.plot(d,P2(d),'r-',label="$A^{6 state}_{opt}(D)$")
plt.plot(d,P3(d),'b--',linewidth=1.5,label="$A^{4 state}_{opt}(D, 3)$")
plt.plot(d,P4(d),'r--',linewidth=1.5,label="$A^{6 state}_{opt}(D, 2)$")
plt.plot(d,P5(d),'b-.',linewidth=1.5,label="$A^{4 state}_{opt}(D, 6)$")
plt.plot(d,P6(d),'r-.',linewidth=1.5,label="$A^{6 state}_{opt}(D, 4)$")
plt.plot(d,P7(d),color='cyan',linestyle="-",linewidth=1.5,label="$A^{4 
state}_{opt}(D, 300)$")
plt.plot(d,P8(d),color='magenta',linestyle="-",linewidth=1.5,label="$A^{6 
state}_{opt}(D, 200)$")
plt.axis([0,1,0,0.5])
plt.xticks([0,0.1,0.2,0.3,0.4,0.5])
plt.grid(True)
plt.legend(loc=7)
plt.xlabel('Disturbance $D$')
plt.ylabel('Optimal Advantage')
plt.savefig('adv.eps')
///
}}}

{{{id=2|
import numpy as np
import matplotlib.pyplot as plt

fig = plt.figure(figsize=(6, 6), dpi=300)
ax = fig.add_subplot(1,1,1)

plt.clf() 
 
def P1(x):
return 0.5+np.sqrt(x-x^2)

def P2(x):
return 0.5+0.5*x+0.5*np.sqrt(2*x-3*(x^2))

d = np.arange(0.0,0.5,0.001)

plt.plot(d,P1(d),'b--',linewidth=1.5)
plt.plot(d,P2(d),'r-.',linewidth=2)
plt.axis([0,0.5,0.5,1])
plt.grid(True)
plt.legend(['$P_{opt}^{4 state}(success)$','$P_{opt1}^{6 
state}(success)=P_{opt2}^{6 state}(success)$'],loc=4)
plt.xlabel('Disturbance $D$')
plt.ylabel('Optimal Success Probability')
plt.savefig('prob.eps')
///
}}}

{{{id=4|
import numpy as np
import matplotlib.pyplot as plt

fig = plt.figure(figsize=(6, 6), dpi=300)
ax = fig.add_subplot(1,1,1)

plt.clf() 

def Q0(x):
return 1+x*np.log(x)/np.log(2)+(1-x)*np.log(1-x)/np.log(2)

def Q1(x):
return 
1+(0.5+np.sqrt(x-x^2))*np.log(0.5+np.sqrt(x-x^2))/np.log(2)+(0.5-np.sqrt(x-x^2))*np.log(0.5-np.sqrt(x-x^2))/np.log(2)

def Q2(x):
return 
1+(0.5+0.5*x+0.5*np.sqrt(2*x-3*(x^2)))*np.log(0.5+0.5*x+0.5*np.sqrt(2*x-3*(x^2)))/np.log(2)+(0.5-0.5*x-0.5*np.sqrt(2*x-3*(x^2)))*np.log(0.5-0.5*x-0.5*np.sqrt(2*x-3*(x^2)))/np.log(2)

def Q3(x):
return 
1+(1-x)*((0.5+np.sqrt(2*x-3*(x^2))/(2-2*x))*np.log(0.5+np.sqrt(2*x-3*(x^2))/(2-2*x))/np.log(2)+(0.5-np.sqrt(2*x-3*(x^2))/(2-2*x))*np.log(0.5-np.sqrt(2*x-3*(x^2))/(2-2*x))/np.log(2))

d = np.arange(0.0,0.5,0.001)

plt.plot(d,Q0(d),'g-',linewidth=1.5)
plt.plot(d,Q1(d),'b--',linewidth=1.5)
plt.plot(d,Q2(d),'r-.',linewidth=2)
plt.plot(d,Q3(d),color='magenta',linestyle=':',linewidth=3)
plt.axis([0,0.5,0,1])
plt.grid(True)
plt.legend(['$I^{AB}$','$I^{AV}$','$I^{AV}_1$','$I^{AV}_2$'],loc=7)
plt.xlabel('Disturbance $D$')
plt.ylabel('Optimal Mutual Information')
plt.savefig('info.eps')
///
}}}

{{{id=5|
d = var('d')
P0=plot(sqrt(d-d^2),0,0.5,color='black',linestyle=":")
P1=plot((sqrt(0.5*d)/(0.5+d))*(1-d) + 
(sqrt(0.5*d))*d,0,0.5,color='blue',linestyle="-")
P2=plot(1-d,0,0.5,color='red',linestyle="--")
P=P0+P1+P2
P.axes_labels(['$D$', 'Advantage($D$)'])
show(P)
///
}}}

{{{id=8|

///
}}}

{{{id=6|
import numpy as np
import matplotlib.pyplot as plt

fig = plt.figure(figsize=(6, 6), dpi=300)
ax = fig.add_subplot(1,1,1)

plt.clf()

def P0(x):
return x
 
def P1(x):
return np.sqrt(x-x^2)

def P2(x):
return n

[sage-devel] Pyrex-mode vs Cython-mode

[Ivan Andrus]

I'm updating sage-mode to work with the latest python.el, so I'm going through 
it systematically for the time.  I've noticed something odd, namely that there 
exist both pyrex-mode and cython-mode.  cython-mode is very minimal, and a 
strict subset of pyrex-mode.  However, both register themselves for handling 
files pyx, pxi and pxd files.  pyrex-mode is the one that wins, but it seems 
there should only be one mode, cython-mode, and all functionality should be 
moved from pyrex-mode to cython-mode.  

Unless there are objections I'm going to rename pyrex-mode to cython-mode and 
remove the old cython-mode.

Actually Cython itself comes with cython-mode.el [1], so perhaps we ought to 
use that.  It doesn't seem to be installed in Sage though.  

-Ivan

[1] https://github.com/cython/cython/blob/master/Tools/cython-mode.el

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Re: Optional BeautifulSoup spkg

[Ivan Andrus]

On Jun 26, 2012, at 3:23 PM, kcrisman wrote:
> On Tuesday, June 26, 2012 5:58:12 AM UTC-4, Javier López Peña wrote: 
> So, summarizing, I have no strong feelings in the spke vs easy_install thing, 
> but if having it as an optional spkg makes someone's life easier, my vote is 
> just go for it.
> 
> This would be to make it easier for someone who has not used easy_install 
> before but has installed spkgs (a nontrivial subset of the population, I 
> think).  We have a number of Python spkgs that presumably wouldn't need to be 
> spkgs.   But again, simply for consistency/convenience; it's nice to have the 
> supply chain all be "Sageified".

I wonder if it might be nice (or perhaps just confusing) to have `sage -i 
beautifulsoup4` install beautiful soup via easy_install.  This would mean the 
same installation process could be used for lots of python packages, and one 
would not have to remember whether to use `sage -sh -c "easy_install package"` 
or `sage -i package`.  Then in the future if we have to patch beautiful soup 
(or any other package) we can create an spkg with the patched source and 
everything works the same.  

Of course I don't know how difficult this would be to integrate with the 
install process since I am completely unfamiliar with it.

-Ivan

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] humble sage-mode feature requests

[Ivan Andrus]

On Jun 8, 2012, at 11:30 AM, Martin Albrecht wrote:

> Hi,
> 
> I am not sure where to send these, but I figured the following would
> be rather nice:

Here is fine, or you could open tickets either on trac (cc me--iandrus) or open 
issues on https://bitbucket.org/gvol/sage-mode/

> - Sage mode (at least in my setup) is bound to one Sage instance. But
> if one plays with SPKGs one may have many. Hence, if sage-mode could
> figure out the copy of Sage to use automatically, or I could set it
> once per session, that'd be great.

I'm not sure how much work this would take.  It might be as simple as setting 
`sage-command` to a buffer local variable when you visit a file.  Certainly you 
could set it globally in `sage-mode-hook` and the last one would win.  I'm most 
worried about how this would interface with the sage shell since you wouldn't 
want to send Sage 5 code to a Sage 4 shell.  I think python-mode.el supports 
multiple versions of pythons runnings, but to my knowledge neither the current 
python.el, nor fgallina's, supports this.

> - sage-test is awesome. Can we perhaps add something like:
> fix-this-doctest-failure? It would replace the expected line with the
> line one got. It would help to fix the trivial stuff. Of course, it
> should be handled with care etc. but it would make things nicer.

That's a good idea.  We already have `sage --fixdoctests` so this would just be 
a more granular form of that.  

I created issue on bitbucket if you want to follow them.  I'll try to get to 
them (especially the second) soon, but I can't make any promises.  There is 
some cleanup that I need to do first.

https://bitbucket.org/gvol/sage-mode/issue/3/support-multiple-versions-of-sage
https://bitbucket.org/gvol/sage-mode/issue/2/add-sage-fix-doctest-at-point

-Ivan

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Has anybody gotten ropemacs working for sage?

[Ivan Andrus]

Greg, 

I got something that seems to work.  I don't take the time to set up a ropemacs 
project (since I don't know what I'm doing), but if you could test it to see if 
it works for you that would be great.  If it does work then we can put the 
instructions on the wiki, and/or make an spkg or something.

download pymacs


sage -sh

easy_install rope
easy_install ropemode
easy_install ropemacs

cd /path/to/pymacs/source
make check
make install # Not sure what this did if anything -- we install it next
cp Pymacs.py $SAGE_ROOT/local/lib/python/
cp Pymacs.el $SAGE_ROOT/data/emacs

exit

# test it when no longer in sage -sh
sage --python -c 'import sys; from Pymacs import main; main(*sys.argv[1:])' -f


Then, either create a sage-python shell script:

#!/bin/sh
sage --python "$@"

or patch Pymacs.el to add (hopefully where is obvious):


(defvar pymacs-python-options '()
  "Options to pass to Python interpreter")

(defun pymacs-start-services ()
...
  (append
   pymacs-python-options
   (list "-c"
 (concat "import sys;"
 " from Pymacs import main;"
 " main(*sys.argv[1:])"))
   (and (>= emacs-major-version 24) '("-f"))
   (mapcar 'expand-file-name pymacs-load-path))
...


;; Add the following to .emacs
;; pymacs.el should be in the load-path if sage-mode is...
(require 'pymacs)

(setq pymacs-python-command sage-command
  pymacs-python-options '("--python"))

(autoload 'pymacs-apply "pymacs")
(autoload 'pymacs-call "pymacs")
(autoload 'pymacs-eval "pymacs" nil t)
(autoload 'pymacs-exec "pymacs" nil t)
(autoload 'pymacs-load "pymacs" nil t)
(autoload 'pymacs-autoload "pymacs")

(pymacs-load "ropemacs" "rope-")
(setq ropemacs-enable-autoimport t)

(require 'auto-complete)
(global-auto-complete-mode t)




Then test:

M-x pymacs-eval 

and see the ropemacs menu etc.

-Ivan

On May 30, 2012, at 10:17 AM, Ivan Andrus wrote:

> Sorry, I meant to write back earlier.  I haven't gotten ropemacs to work, but 
> I haven't tried.  I don't have time to work on it right now, but if you open 
> a ticket on https://bitbucket.org/gvol/sage-mode/issues then I'll get around 
> to it eventually.
> 
> Unfortunately, the installation looks rather complicated.  What did you try 
> and how did it fail?  Did you install rope and friends in sage's python for 
> example?
> 
> sage -sh
> easy_install rope
> easy_install ropemode
> easy_install ropemacs
> 
> In fact perhaps everything would best be done in sage -sh.  
> 
> -Ivan
> 
> On May 16, 2012, at 4:26 AM, Greg Laun wrote:
> 
>> I'm writing some modules for sage, and I would like to get some auto-
>> completion and refactoring abilities.  I can get some things to work,
>> such as pyflakes for code checking, but I would really like ropemacs
>> to work.
>> 
>> I see there is a page on the wiki about setting up IDEs, but no
>> mention is made of the emacs IDE features.  I know many sage
>> developers use emacs, so I was wondering if anyone had gotten ropemacs
>> or pymacs or something similar to work.
>> 
>> If so, would anybody be willing to document the procedure?
>> 
>> Thanks!
>> 
>> Greg Laun

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Re: new computer - any special Lion instructions?

[Ivan Andrus]

On Jun 6, 2012, at 4:42 AM, Benjamin Jones wrote:
> On Tue, Jun 5, 2012 at 9:37 PM, kcrisman  wrote:
>> 
>>> I'm using Lion as well. I installed the command line tools package
>>> from Apple and have had no problems building sage-5+. No idea about
>> 
>> Is that different from the $5 Xcode or whatever?  I could ask my IT
>> people to preinstall certain optional things from the installation
>> materials.
>> 
> 
> Yes -- I didn't pay anything to install the command line tools. See
> [2] for more info. The full xcode includes all the Apple specific
> libraries that one needs to build Mac and iOS apps.

If you want to build the app portion, you'll need all of Xcode.  This isn't a 
big deal unless you want to test patches which I know you've done in the past 
(at least on PPC).

-Ivan

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Can't login to trac

[Ivan Andrus]

On Jun 3, 2012, at 7:31 PM, P Purkayastha wrote:

> Hi,
> 
>   For the past 1 day I am unable to login to trac. Clicking on the login for 
> the first time asks for user/passwd, and then it drops me back to the same 
> page as if I was unauthenticated. Clicking on the login again, doesn't ask 
> for user/passwd anymore but simply refreshes the page. Sometimes the page 
> alternates the color from the old color scheme to the new color scheme (or 
> vice versa) during this refresh. But I am not logged in nonetheless.
> 
>   Is anyone else facing the same problem? Or, is it an isolated problem with 
> my account?
> 
>  - ppurka (trac username)

It's working for me.  When I click login, I never have to type my password, 
though, so perhaps it a difference of settings.  I don't remember what setting 
that was.  

It's a wild guess but the changing of color schemes makes me think you might 
have an old copy cached somewhere that's interfering.

-Ivan

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Re: Poll: Making sage-mode a standard package

[Ivan Andrus]

On Jun 1, 2012, at 7:55 AM, syd.lavas...@gmail.com wrote:

> [X] Make it standard at some point in the "near" future
> 
> Mainly because I think everybody should use emacs as their operating system. 
> it will save their time and the money they spend on buying fancey computers. 
> Also Nicolas is very cool so I wanted to support his point ;)
> 
> That's said, I found couple of bugs in it when I use it with emacs 24,

Please open tickets on bitbucket [1] so they don't get lost.

> for example you can only run sage-build from a window with inferior-sage-mode 
> (subproblem of what we discussed before probably you need to add that hook 
> thing to the sage-build as well),

Yeah.  I need to figure out the right way to fix that once and for all.  I 
might file a bug with Emacs after I figure out exactly why we're doing it in 
the first place. :-)

> also autocomplete and keyword?? take ages to work. It also hijacks python 
> files no matter if there's a python interpretor open or not (I wrote a fix 
> for this one).

If you can fork on bitbucket and send a pull request that would be great.  Or 
just sending me a diff would be fine too.

> Though, it's unstable emacs 24. But if by the time it gets released, 
> sage-mode is not standard, it's less probable that somebody cares about these 
> bugs as Benjamin said.

Yeah.  Emacs 24 is in pretest right now, and I don't think it will be long 
before it's released (the release candidate was just released.  In 24.2 they're 
going to change python.el so I'm sure there will be plenty of work in the near 
future.

I really need to get some automated tests in place so that it's easy to check 
with different emacs version.  But writing tests is even more boring than 
writing my thesis. :-)

-Ivan

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Has anybody gotten ropemacs working for sage?

[Ivan Andrus]

Sorry, I meant to write back earlier.  I haven't gotten ropemacs to work, but I 
haven't tried.  I don't have time to work on it right now, but if you open a 
ticket on https://bitbucket.org/gvol/sage-mode/issues then I'll get around to 
it eventually.

Unfortunately, the installation looks rather complicated.  What did you try and 
how did it fail?  Did you install rope and friends in sage's python for example?

sage -sh
easy_install rope
easy_install ropemode
easy_install ropemacs

In fact perhaps everything would best be done in sage -sh.  

-Ivan

On May 16, 2012, at 4:26 AM, Greg Laun wrote:

> I'm writing some modules for sage, and I would like to get some auto-
> completion and refactoring abilities.  I can get some things to work,
> such as pyflakes for code checking, but I would really like ropemacs
> to work.
> 
> I see there is a page on the wiki about setting up IDEs, but no
> mention is made of the emacs IDE features.  I know many sage
> developers use emacs, so I was wondering if anyone had gotten ropemacs
> or pymacs or something similar to work.
> 
> If so, would anybody be willing to document the procedure?
> 
> Thanks!
> 
> Greg Laun

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Re: Poll: Making sage-mode a standard package

[Ivan Andrus]

On May 25, 2012, at 11:24 PM, Ivan Andrus wrote:

> Dear all sage and emacs (or not) users,
> 
> Since I've been working on sage-mode a bit recently I thought I would look at 
> trac and try to fix any sage-mode related bugs there.  I found #2666 which 
> wants to make sage-mode a standard package.
> 
> If people want this then I'd like to get it done.  But if not then I'd like 
> to close the ticket.  Personally, I'm not sure it should be standard since 
> people who wish to use it still have to add something to their .emacs, and 
> hence they still need to know about it and take some action.  However, I'm 
> open to being persuaded.  The spkg is 272K.
> 
> [ ] Make it standard at some point in the "near" future.
> [ ] Don't make it standard and close the ticket.
> [ ] Don't make it standard now, but don't close the ticket.


The results are fairly close (I guess everyone has responded who wants to).  We 
have 3.5 votes for making it standard, 3.5 for not, and 1 for thought it was 
standard, which I assume means make it standard.  So I guess I'll keep the 
ticket open and work towards making it standard unless anyone else would like 
to weigh in.

-Ivan

[X] Don't make it standard and close the ticket.
  Justin C. Walker
  David Roe
  Dima Pasechnik
  Benjamin Jones -- initially, see below

[X] Make it standard at some point in the "near" future.
  Nicolas M. Thiéry
  Keshav Kini
  Volker Braun
  Benjamin Jones -- if it would improve maintenance, see above

[X] I thought it was already standard, and am surprised to hear that it isn't.
  William Stein

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Re: Poll: Making sage-mode a standard package

[Ivan Andrus]

On May 26, 2012, at 7:31 PM, Benjamin Jones wrote:
> On Sat, May 26, 2012 at 10:23 AM, Ivan Andrus  wrote:
>> On May 26, 2012, at 7:09 PM, Benjamin Jones wrote:
>>> On Sat, May 26, 2012 at 6:55 AM, Ivan Andrus  wrote:
>>> 
>>>> No offense taken.  Who knows what's going to happen after I graduate for
>>>> example—maybe I'll get a full time job fixing bugs in Sage, or maybe I'll 
>>>> be
>>>> flipping burgers. :-)
>>>> 
>>>> It's important to remember that if it's standard someone _has_ to maintain
>>>> it.  Of course, it's also more likely that someone _will_ maintain it.
>>>> 
>>>> -Ivan
>>> 
>>> From the point of view that making sage-mode a standard package would
>>> increase the likelihood that it is maintained, I would support it
>>> being included as a standard package.
>> 
>> Do you say that because you feel it hasn't been maintained well, or that it 
>> might not be in the future since the original author has moved on?
>> 
>> -Ivan
> 
> I said that in the spirit that I think sage-mode is a useful package
> and any steps we can take to ensure that useful packages continue to
> be well maintained is a good thing. I haven't been using it for all
> that long, so I can't comment on if it has or hasn't been maintained
> well in the past. As for the future, who knows, but making it a
> standard package will increase its chances to thrive compared to
> making it an optional package.
> 
> What is your opinion as the current maintainer?


Unless I'm mistaken, if it becomes standard then someone (probably me) has to 
volunteer to maintain it for at least 2 years.  I'm okay with that since I'll 
be maintaining the Mac and iPhone apps for probably that long.  Of course I 
would prefer to not commit in case things change in the future.  :-)  But I 
would be willing to do it.

If I doesn't go standard and things don't work out for me after graduation in a 
way that I can spend a "lot" of time on sage, then I probably won't maintain it 
other than perhaps helping track down issues (i.e. no new features, code 
cleanup etc.).  Usually emacs lisp code is pretty easy to debug so I don't 
think it would take too much time.  Of course even if it does go standard there 
is no guarantee of new features, but it would be slightly more likely.  So in 
the end it may not making too much difference.

Also, do there need to be automated tests to become standard?  If so then 
someone would have to write them.  I would _love_ to have some tests for 
sage-mode, especially since we will have to support fgallina's rewrite of 
python.el pretty soon [1].  I certainly couldn't write them really soon (I'm 
already way behind on the iPhone app), but it would be a good reason to keep 
the ticket open.

-Ivan

[1] https://bitbucket.org/gvol/sage-mode/issue/1/support-pythonel-by-fgallina

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Re: Poll: Making sage-mode a standard package

[Ivan Andrus]

On May 26, 2012, at 7:09 PM, Benjamin Jones wrote:
> On Sat, May 26, 2012 at 6:55 AM, Ivan Andrus  wrote:
> 
>> 
>> No offense taken.  Who knows what's going to happen after I graduate for
>> example—maybe I'll get a full time job fixing bugs in Sage, or maybe I'll be
>> flipping burgers. :-)
>> 
>> It's important to remember that if it's standard someone _has_ to maintain
>> it.  Of course, it's also more likely that someone _will_ maintain it.
>> 
>> -Ivan
>> 
> 
> From the point of view that making sage-mode a standard package would
> increase the likelihood that it is maintained, I would support it
> being included as a standard package.

Do you say that because you feel it hasn't been maintained well, or that it 
might not be in the future since the original author has moved on?

-Ivan

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Re: Poll: Making sage-mode a standard package

[Ivan Andrus]

On May 26, 2012, at 2:46 PM, P Purkayastha wrote:
> On Saturday, May 26, 2012 8:31:11 PM UTC+8, P Purkayastha wrote:
> On Saturday, May 26, 2012 5:50:12 PM UTC+8, Dima Pasechnik wrote:
> On 2012-05-25, Ivan Andrus  wrote: 
> > Dear all sage and emacs (or not) users, 
> > 
> > [ ] Make it standard at some point in the "near" future. 
> > [ ] Don't make it standard and close the ticket. 
> > [ ] Don't make it standard now, but don't close the ticket. 
> 
> [X] Don't make it standard and close the ticket.  Include as optional 
> package. 
> 
> Also due to the painfully obvious next move: bundle in an emacs distro 
> compatible with the said sage-mode... 
> No, really, we'd hate to see a stream of complaints like "oh, it does 
> not work on my ZSuperDuperEmacs version 666.666.6..." 
> 
> Someone mentioned that GAP has such a mode in a standard distribution, 
> but in fact it's horribly broken and obsolete, 
> $ ls -l /usr/local/src/gap/gap4r4/etc/emacs/ 
> total 248 
> -rw-r--r--  1 dima  wheel  58933 Aug 15  2001 comint.el 
> -rw-r--r--  1 dima  wheel   4542 Aug 15  2001 gap-mode.doc 
> -rw-r--r--  1 dima  wheel  35909 Aug 15  2001 gap-mode.el 
> -rw-r--r--  1 dima  wheel  17587 May  8  2005 gap-process.el 
> 
> Dima
> 
> For that matter even the vim plugins are broken. See
> http://archives.gentoo.org/gentoo-science/msg_a74bfb4eb0abd88584885bab90d7e891.xml
>  
> 
> What I meant to say is that, in the long term there is a possibility that the 
> package might become unmaintained. No offense to Ivan, but this is a fact of 
> the way OSS works. :)

No offense taken.  Who knows what's going to happen after I graduate for 
example—maybe I'll get a full time job fixing bugs in Sage, or maybe I'll be 
flipping burgers. :-)  

It's important to remember that if it's standard someone _has_ to maintain it.  
Of course, it's also more likely that someone _will_ maintain it.

-Ivan

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Re: Poll: Making sage-mode a standard package

[Ivan Andrus]

On May 26, 2012, at 11:50 AM, Dima Pasechnik wrote:
> On 2012-05-25, Ivan Andrus  wrote:
>> Dear all sage and emacs (or not) users,
>> 
>> [ ] Make it standard at some point in the "near" future.
>> [ ] Don't make it standard and close the ticket.
>> [ ] Don't make it standard now, but don't close the ticket.
> 
> [X] Don't make it standard and close the ticket.  Include as optional
> package.
> 
> Also due to the painfully obvious next move: bundle in an emacs distro
> compatible with the said sage-mode...
> No, really, we'd hate to see a stream of complaints like "oh, it does
> not work on my ZSuperDuperEmacs version 666.666.6..."

I'll just have to use the time travel capabilities of emacs to ensure 
compatibility [1] :-)

> Someone mentioned that GAP has such a mode in a standard distribution,
> but in fact it's horribly broken and obsolete, 
> $ ls -l /usr/local/src/gap/gap4r4/etc/emacs/
> total 248
> -rw-r--r--  1 dima  wheel  58933 Aug 15  2001 comint.el
> -rw-r--r--  1 dima  wheel   4542 Aug 15  2001 gap-mode.doc
> -rw-r--r--  1 dima  wheel  35909 Aug 15  2001 gap-mode.el
> -rw-r--r--  1 dima  wheel  17587 May  8  2005 gap-process.el

I asked a while back if they would include my update to gap-mode [2], and got a 
non-commital response.  I guess it's about time to ask again.

-Ivan

[1] https://github.com/emacsmirror/emacs/blob/master/etc/future-bug
[2] https://bitbucket.org/gvol/gap-mode

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Re: Poll: Making sage-mode a standard package

[Ivan Andrus]

On May 26, 2012, at 1:11 AM, Keshav Kini wrote:
> Ivan Andrus  writes:
>> Dear all sage and emacs (or not) users,
>> 
>> Since I've been working on sage-mode a bit recently I thought I would look 
>> at trac and try to fix any sage-mode related bugs there.  I found #2666 
>> which wants to make sage-mode a standard package.
>> 
>> If people want this then I'd like to get it done.  But if not then I'd like 
>> to close the ticket.  Personally, I'm not sure it should be standard since 
>> people who wish to use it still have to add something to their .emacs, and 
>> hence they still need to know about it and take some action.  However, I'm 
>> open to being persuaded.  The spkg is 272K.
>> 
>> [ ] Make it standard at some point in the "near" future.
> 
> This. It is very standard for programs to include relevant emacs modes
> and vim syntax/indent/whatever files in their source distribution.
> Cython does this, for example, as does GAP.
> 
> -Keshav

That's true.  Often they have bash-completion and man pages as well.  Which now 
that I think about it is an interesting idea.  Maybe someone should improve 
http://wiki.sagemath.org/bash-completion and create an spkg.  Actually, when we 
switch to argparse we should just use optcomplete or genzshcomp or something 
similar.  Of course we might still have to write some custom stuff to properly 
complete certain subcommands (like sage --gap) which do there own parsing.

OTOH, most programs don't have an easy way to install optional pieces like Sage 
does with spkg's.

-Ivan

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

[sage-devel] Poll: Making sage-mode a standard package

[Ivan Andrus]

Dear all sage and emacs (or not) users,

Since I've been working on sage-mode a bit recently I thought I would look at 
trac and try to fix any sage-mode related bugs there.  I found #2666 which 
wants to make sage-mode a standard package.

If people want this then I'd like to get it done.  But if not then I'd like to 
close the ticket.  Personally, I'm not sure it should be standard since people 
who wish to use it still have to add something to their .emacs, and hence they 
still need to know about it and take some action.  However, I'm open to being 
persuaded.  The spkg is 272K.

[ ] Make it standard at some point in the "near" future.
[ ] Don't make it standard and close the ticket.
[ ] Don't make it standard now, but don't close the ticket.

-Ivan

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Re: [sage-devel] Re: How does the pynac spkg work?

[Ivan Andrus]

On May 14, 2012, at 7:47 AM, Julien Puydt wrote:
> Le lundi 14 mai, Keshav Kini a écrit:
>> A better solution, IMO, is to make scripts check the actual contents
>> of the SPKG for extraneous directories and files. There should be no
>> directories other than src/ and patches/ ; the line "src/" should be
>> in .hgignore (which should exist), spkg-install should exist, SPKG.txt
>> should exist, etc. Anything unknown in the root directory of the SPKG
>> should generate a warning.
> 
> Debian has an utility called 'lintian' which is a 'Static analysis tool
> for Debian packages', and which checks that the package satisfies a
> precise set of properties. No package goes in if it makes lintian
> unhappy.
> 
> Either sage would need such, or it should just put things right
> (upstream tarballs in a directory -- building scripts in another
> directory, under proper revision control).

When you build an spkg it already checks a few things.  It shouldn't be hard to 
add other checks.  Currently the checks are not "enforced" in the sense that 
they just print warnings, but don't change the return status or anything.  This 
is in SAGE_ROOT/local/bin/sage-pkg if anyone wants to look at it.  

For example we could exclude repository data in the src/ directory of all 
spkgs.  Deciding whether or not this is desirable is the hard part.  There 
could even be an environment variable (since we all love them) specifying in 
the spkg-install which other files to exclude.

-Ivan

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org