Volker Braun wrote:
I guess that #16187 broke it (the beautification of "sage -optional").

Yes, I feared that, so I did run doctests with the changes, and "All tests passed!"... B)


By the way, optional_packages() parses the output of "sage -optional"
(!).

I knew that was the case long time ago, but thought that meanwhile changed, since we turned a lot of such functionality from (just calling) shell scripts into "real" Python functions.


And it isn't doctested.

Obviously...


The only surprise should be that it took
this long to break.

Well, the old output (before #16187) didn't work w.r.t. "new style" spkgs anyway; one reason for opening #16187.


Finally, it is fundamentally unsound to modify shared libraries while
your program is executing. install_package() should at most tell you how
to exit sage and install stuff using sage -i.

I don't care much, and btw. changing shared libraries that have already been loaded shouldn't cause (immediate) trouble.

I'd simply give a kind advice, like 'sage -upgrade' used to do:

   WARNING: Installing new packages from within Sage could take hours,
            fail, and render your Sage install useless!!


We don't recommend, but we also don't prevent people from running os.system("sage -b") or os.system("make") from the Sage prompt.


-leif

On Sunday, April 27, 2014 10:42:36 PM UTC+1, William wrote:

    Hi,

    I installed the sage-6.2.rc0 [1] that Volker posted a few days ago.
    However, the in-Sage commands install_package, optional_packages,
    etc., are now broken.  Any ideas what is going on?

    More precisely:

        sage: v = optional_packages()
        ...

        Type 'sage -i package_name' to download and install a package.
        Optional package list (shown above) appears to be currently not
    available or corrupted (network error?).
        sage: v
        ([], [])

    PROBLEMS:

    1. Note that v is wrong -- it should have the installed/uninstalled
    packages.  This is probably because of the "network error?" error.

    2. Why does a command *inside of Sage, run from the Sage prompt* tell
    the user to "Type 'sage -i package_name' to download and install a
    package."?   Instead, it should suggest using the install_package(...)
    command in Sage.

    3. As mentioned above, the install_package command is also broken now.


    NOTE: Using "sage -i" from the command line does still work, so that's
    what I'll do.

    [1]
    
http://boxen.math.washington.edu/home/release/sage-6.2.rc0/sage-6.2.rc0.tar.gz

--
() The ASCII Ribbon Campaign
/\   Help Cure HTML E-Mail

--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to