#19105: Allow sage -i python to actually install the right version of Python
-------------------------------------+-------------------------------------
Reporter: jdemeyer | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.9
Component: scripts | Resolution:
Keywords: | Merged in:
Authors: Jeroen Demeyer | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/jdemeyer/ticket/19105 | 74c78c179010befaf59224628a64efdf0ca88048
Dependencies: #19119 | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by jhpalmieri):
Another possible solution: don't search on-line standard packages.
{{{
#!diff
diff --git a/build/bin/sage-spkg b/build/bin/sage-spkg
index f4b085b..356efb9 100755
--- a/build/bin/sage-spkg
+++ b/build/bin/sage-spkg
@@ -331,7 +331,7 @@ if [ ! -f "$PKG_SRC" ]; then
if [ $? -ne 0 ]; then
exit 1
fi
- for repo in optional experimental standard huge archive; do
+ for repo in optional experimental huge archive; do
# Download the list of packages.
echo ">>> Checking online list of $repo packages."
# File inside DOT_SAGE should be writable
}}}
That's where the problematic Python package is, right? And with recent
versions of Sage, is there any reason to search "standard" packages? I
think that all of those are either outdated or have more recent new-style
replacements.
--
Ticket URL: <http://trac.sagemath.org/ticket/19105#comment:10>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" 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-trac.
For more options, visit https://groups.google.com/d/optout.
