On Apr 29, 5:40 pm, Robert Bradshaw <[EMAIL PROTECTED]>
wrote:
> On Apr 28, 2008, at 11:32 PM, mabshoff wrote:
<SNIP>
> > The file system underneath Sage is for now a Unix file system which
> > uses "space" as a separator. It is generally a bad idea to use
> > anything non [a-zA-Z0-9] in file names since it will likely break with
> > other encodings and/or file systems. Windows introduced the rather
> > stupid concept that allows file system path to contain spaces and it
> > has broken numerous tools like the autotools for example. Having
> > spaces or any other characters in file names is something you do not
> > do and I personally see no reason why we should work around that
> > limitation.
>
> I think spaces in filenames is something that should be supported,
> especially as we look to porting to Windows (where the users entire
> home folder sits inside "Documents and Settings." The preparser
> shouldn't be called on lines sent to the shell, though I'm not sure
> how to best detect that (other than explicitly prefacing with a "!").
> It is kind of odd that ipython will automatically treat some commands
> as shell commands.
>
Yes, but there are two bugs here:
a) an issue in ipython, i.e.
sage: cd?
Type: Magic function
Base Class: <type 'instancemethod'>
String Form: <bound method InteractiveShell.magic_cd of
<IPython.iplib.InteractiveShell object at 0x600000000036e950>>
Namespace: IPython internal
File: /home/mabshoff/sage-3.0.1.alpha0/local/lib/python2.5/
site-packages/IPython/Magic.py
Definition: cd(self, parameter_s='')
Docstring:
Change the current working directory.
cd either needs to learn how to escape certain characters or just put
quotes around the name. Quotes won't help if you have quotes in a file
name [which some people do - I have seen it].
On Windows we could always convert long file names [with spaces] to
short 8.3 file names, but I guess that would require hacking on
ipython itself. Either way, we are running some quite old version of
ipython and we maybe should consider upgrading.
b) The preparser, i.e. 3.0->RealNumber(3.0): This is a more general
issue, i.e. people get bitten by it when using numpy/scipy regularly.
I am not sure what can be done here on a technical level to avpoid
this whole mess. Any ideas?
<SNIP>
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
