This was due to the trac change. I've updated the patchbot to
understand the this (and it's actually much cleaner as there are
csv/tsv formats now so I don't have to parse the html). It'll take a
while to actually update all the tickets in question.
On Thu, Jul 25, 2013 at 2:32 AM, David Loeffler
Hey William,
On Thursday, July 25, 2013 8:27:21 PM UTC+5:30, Volker Braun wrote:
The problem is that exceptions raised by the inputsplitter are not handled
by IPython. I've asked at IPython-devel at
http://python.6.x6.nabble.com/InputSplitter-and-SyntaxError-td5025938.htmlbut
didn't get
Hi Robert,
That's excellent -- thanks! One question: there are some tickets (e.g.
#14366) where it is not picking up correctly information in the ticket
comments specifying which patches to apply. Is it possible that this
part of the patchbot's code has also been broken by the trac update?
(I
Hey Andrew,
I believe there's a minor bug with the new trac server: the names in the
replying to get the same markup as the ticket number. In particular, if a
ticket is closed, they names will have a strikeout through them. Ex.
http://trac.sagemath.org/ticket/14031. Or is this the expected
Hey everyone (especially cygwin people),
I've been trying for the past 2 hours to build sage 5.11.beta3 on
cygwin64, however it continuously fails when building zlib. I've
multiple-checked that I've installed all of the dependencies (and
overkilled on some of them too), and I've installed
On Fri, Jul 26, 2013 at 3:19 AM, David Loeffler
d.a.loeff...@warwick.ac.uk wrote:
Hi Robert,
That's excellent -- thanks! One question: there are some tickets (e.g.
#14366) where it is not picking up correctly information in the ticket
comments specifying which patches to apply. Is it possible
At the very least, lets be careful to avoid fancy invisible unicode
characters: https://groups.google.com/forum/#!topic/sage-devel/LjC75cae7XI
On Thu, Jul 25, 2013 at 9:52 PM, William Stein wst...@gmail.com wrote:
On Mon, Jul 8, 2013 at 2:05 PM, Robert Bradshaw
rober...@math.washington.edu
Although (perhaps?) surprising, some languages don't have spaces and
require zero-width space to designate word boundaries for line breaks.
On Friday, July 26, 2013 3:02:41 PM UTC-4, Robert Bradshaw wrote:
At the very least, lets be careful to avoid fancy invisible unicode
characters:
