Remove twisted spkg

[dimpase]

The version of Twisted currently used in Sage is old and obsolete; moreover it is buggy, as our extensive tests involving running labs for 120 students show. The crashes of the notebook webapp go away after the upgrade to twisted 11.

The twisted package is now included in the flask sagenb (#11080), so this ticket just removes the twisted spkg.

See http://groups.google.com/group/sage-devel/browse_thread/thread/98c53d17166da1b9 for the sage-devel vote.

apply:

1. attachment: trac-11874-remove-twisted.patch to the sage root repository
2. attachment: sage-spkg-11874.patch to the Sage library.

And remove the twisted spkg from the standard spkgs.

Depends on #12329
Depends on #11080
Depends on #10492

CC: @rkirov @kini @ppurka @kcrisman @jasongrout @strogdon

Component: packages: standard

Keywords: twisted, notebook

Author: Radoslav Kirov, Jason Grout

Reviewer: Dmitrii Pasechnik, Jason Grout

Merged: sage-5.2.beta0

Issue created by migration from https://trac.sagemath.org/ticket/11874

[jasongrout]

comment:3

See also #11497, which has a possible fix that we may need to apply, maybe?

[jasongrout]

Description changed:

--- 
+++ 
@@ -1,7 +1,6 @@
 the currently used in Sage version of twisted is old and obsolete; moreover it is buggy, as our extensive tests involving running  labs for 120 students show. The crashed of the notebook webapp go away after the upgrade to twisted 11.
 
-A preliminary spkg is here http://boxen.math.washington.edu/home/dima/packages/twisted-11.0.0.spkg
-and the corresponding Sage patch is here
-http://boxen.math.washington.edu/home/dima/patches/twisted11.patch
-(to be applied against rkirov's flask version of the notebook
-http://code.google.com/r/rkirov-flask/)
+The new package is at http://sage.math.washington.edu/home/jason/twisted-11.0.0.spkg
+
+The new sage notebook at http://code.google.com/r/jasongrout-flask-sagenb/ is needed to test this package
+

[jasongrout]

comment:4

See also #11497, which has a possible fix that we may need to apply, maybe?

[kcrisman]

comment:5

Replying to @jasongrout:

See also #11497, which has a possible fix that we may need to apply, maybe?

Apparently not... see that ticket.

[jdemeyer]

Replying to @dimpase:

The new sage notebook at http://code.google.com/r/jasongrout-flask-sagenb/ is needed to test this package

Please explain what you mean with this: needed to "test" this package?

[jasongrout]

comment:7

The changes necessary to test this package are included in the http://code.google.com/r/jasongrout-flask-sagenb/ notebook, and not in the current notebook. Thus, to test this spkg, someone will need to install the new flask server as well.

[jdemeyer]

comment:8

Replying to @jasongrout:

The changes necessary to test this package are included in the http://code.google.com/r/jasongrout-flask-sagenb/ notebook, and not in the current notebook. Thus, to test this spkg, someone will need to install the new flask server as well.

You mean also to "use" this package, or only to "test" it? That's confusing. Is flask-sagenb required or only recommended? Should this be merged into Sage or not?

Also, I would really appreciate some kind of roadmap from the flask-sagenb people to eventually be merged into Sage (I've said this many times without any good answer). Because it looks more and more that flask-sagenb is a fork of sagenb with no real plan for eventually getting back into Sage.