answered 13 years ago
This was fixed by #11549. The fix will be available in Sage 4.7.2.
You can apply the changes on that ticket to your copy of Sage using these instructions from the developer guide.