Of course, you are right :) I more meant that maybe we can replace these
messages with messages saying something like "Placeholder text as a
workaround for Mercurial bug #1033 (fixed in 2008)" to avoid people getting
the idea (from browsing the Sage source code) that this is still an issue
in 2
Well this question is sort of answered automatically if we start making all
__init__.py as mentioned on that ticket, namely make them contain just:
import all
Personally I wouldn't mind the placeholders to remain there in the
otherwise empty __init__.py files just so that developers still using
Necrobump - can we get rid of these lines or are they still important? Is
the fixed Mercurial bug I mentioned what necessitated these lines? I was
reminded of this by ##11762 which touches the __init__ files.
-Keshav
Join us in #sagemath on irc.freenode.net .
--
To post to this group, se
Seems like it was fixed in 2008: revision
http://selenic.com/repo/hg/rev/9db24a36d182 fixing
http://mercurial.selenic.com/bts/issue1033
(?)
-Keshav
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@g
On Fri, Jun 17, 2011 at 2:55 PM, Keshav Kini wrote:
> I asked some guys in #mercurial and they said they'd never heard of
> repository corruption from empty files or mercurial not being able to commit
> empty files. What's the reason for these comments? Or are they just FUD? :)
I believe patch is
What's up with these comments?
11870 Sat Mar 28 16:10:58 2009 -0700 sage/algebras/quatalg/__init__.py: #
quaternion algebra init file
14468 Sun Apr 25 12:04:13 2010 +0200 sage/coding/source_coding/__init__.py:
# Just a comment so that __init__.py is not an empty file.
9029 Sun Mar 23 19:08:49 20
