On Thursday, June 20, 2013 8:33:47 AM UTC-7, Nathann Cohen wrote:
WHY should this
thing be implemented like that when there are non-intrusive ways to
make find_stat work ?
Please propose a mechanism that
* Only occupies a single line of code
* Outside of the method body, so it is
On Thursday, June 20, 2013 9:34:48 AM UTC-7, Nathann Cohen wrote:
More seriously, wouldn't changing the decorator to something that
registers the method and not change it do the trick
There decorator performs two functions currently:
1) label the method as a combinatorial map
2) transform
I did read the source before posting on the subject, and your message makes
no sense in that context.
* Decorators have their place.
* A non-decorator way to add maps to the database should be added
eventually.
* Premature optimizations are bad.
--
You received this message because
http://www.python.org/dev/peps/pep-0318/
On Friday, June 21, 2013 1:43:13 PM UTC-7, Dima Pasechnik wrote:
Why does one even need a decorator in Simon's proposal?
http://www.python.org/dev/peps/pep-0318/
I think a decorator like this makes the code unreadable, and if it can
be avoided then
You have some half-built gfortran in the path, try make distclean to
start the build from scratch.
On Saturday, June 22, 2013 2:49:07 AM UTC-7, Wai Man Chung wrote:
I have taken advice of Volker Braun and run sudo yum install gcc-c++
gcc-gfortran, then I run make again, it runs for a while
Congratulations! I really appreciate your tireless work as release manager.
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Does it work if you switch your locale temporarily to English? (set
LANG=en_US). Did Sage build its own gfortran? Can you post the config.log?
Found package pynac-0.2.6 in spkg/standard/pynac-0.2.6.spkg
pynac-0.2.6
Extracting package
If its the PPL clash then you can try the compilerwrapper: First run make
distclean, then download the spkg from http://trac.sagemath.org/10572 and
then run ./sage -f /compilerwrapper-1.2.spkg
On Monday, June 24, 2013 7:30:34 AM UTC-4, leif wrote:
Volker Braun wrote:
Does it work if you
Its not just PPL, other libraries break system-wide stuff too. Its just
more noticeable since borked gcc = immediate end of game. Really, the
problem is setting LD_LIBRARY_PATH in the first place. Any messing around
with ppl to minimize the chance of breakage is just putting lipstick on a
pig.
There is also the libgd / libjpeg issue #12276 if you need more examples of
what is wrong with LD_LIBRARY_PATH
On Monday, June 24, 2013 10:36:54 AM UTC-4, leif wrote:
And the only other spkg that frequently causes trouble (although
recently much less than it used to) is readline,
--
You
Dear Sage developers,
Jennifer Balakrishnan and myself will be organizing a Sage development
conference in Oxford, UK, on September 23-29. See
http://wiki.sagemath.org/days53 for details This workshop will be one of
the first in the new Mathematical Institute which is currently being
Attaching files in the notebook doesn't work currently (might have never
worked). Attaching files on the command line should work. See also:
https://github.com/sagemath/sagenb/issues/169
http://trac.sagemath.org/sage_trac/ticket/14523
--
You received this message because you are subscribed to
Yep, its the ppl library conflict:
/usr/lib/gcc/i586-mageia-linux-gnu/4.7.2/cc1: symbol lookup error:
/lib/libppl_c.so.4: undefined symbol:
_ZN23Parma_Polyhedra_Library13have_sse_unitE
On Tuesday, June 25, 2013 11:49:26 PM UTC-4, Taekyung Kim wrote:
This is my config.log file.
But what do
Thanks, I added the info to the bug report. It is not an OS issue since I
get the same failure on Fedora 19 x86_64.
On Wednesday, June 26, 2013 12:00:51 AM UTC-4, Jon Silverberg wrote:
Thanks for the reply. I know that attaching files in a notebook did work
quite well in Mac os 10.7.x and
. Should I make again first?
2013년 6월 26일 수요일 오후 12시 59분 6초 UTC+9, Volker Braun 님의 말:
Yep, its the ppl library conflict:
/usr/lib/gcc/i586-mageia-linux-gnu/4.7.2/cc1: symbol lookup error:
/lib/libppl_c.so.4: undefined symbol:
_ZN23Parma_Polyhedra_Library13have_sse_unitE
On Tuesday, June
Trivial fix to make sage -f url work again (NEEDS REVIEW)
http://trac.sagemath.org/sage_trac/ticket/14820
On Wednesday, June 26, 2013 12:20:52 AM UTC-4, Volker Braun wrote:
The automatic download is broken.
--
You received this message because you are subscribed to the Google Groups
sage
On Wednesday, June 26, 2013 10:19:52 AM UTC-4, Christian Stump wrote:
or replacing the almost 50 is_??? by
has_property(???), including antisymmetric which should rather be
is_antisymmetric
I think this is a terrible pattern. There is nothing wrong with having lots
of methods, Python
Same here, my desktop dropped off the net and will probably have to wait
until I'm back home.
On Thursday, June 27, 2013 5:40:48 PM UTC-4, Dima Pasechnik wrote:
On 2013-06-27, Simon King simon...@uni-jena.de javascript: wrote:
Hi!
Is there currently a problem with the patchbots on
*Putting on my Physicist hat*
You should be taking the actual standard deviation into account, too. Most
likely, patchbot number one gave less consistent timings, possibly due to
background jobs, mechanical harddisk, or memory pressure. This is why it
failed to detect any effect, not because
I had my desktop rebooted manually.
You can't call the plugin directly, but it is very straightforward code and
it would be easy to turn it into a standalone script that just compares any
two sage trees.
--
You received this message because you are subscribed to the Google Groups
I can confirm the regression, after a few seconds I get
TypeError: ECL says: Memory limit reached. Please jump to an outer pointer,
quit program and enlarge the
memory limits before executing the program again.
The process that consumes the memory is sage-ipython (in the ECL shared
library),
On Friday, June 28, 2013 10:56:48 AM UTC-4, Simon King wrote:
This would be nice to have! As I wrote on the other thread, I took 20
samples of sage -startuptime without and 20 with the patches, but I
am not totally confident how to interprete it.
Yes, especially since it turns out to be
See the other
thread https://groups.google.com/d/msg/sage-devel/s-LAqd0pXlg/XVX0xQLAS9IJ
On Friday, June 28, 2013 10:54:50 AM UTC-4, Simon King wrote:
Speaking about statistics: On my own machine, I made 20 runs of
sage -startuptime with (1) only the dependencies of the ticket
applied,
The interface checks whether the utility program points2placingtriang
from TOPCOM is available, and didn't find it in your install. Do you have
Sage's current spkg of TOPCOM installed or some other version?
Just for the record, you almost certainly want
This sounds even worse, the triangulation module is pure python but you got
an exception ignored which must have come from some C/Cython code.
On Monday, July 1, 2013 5:22:44 PM UTC-4, William wrote:
Exception pexpect.ExceptionPexpect: ExceptionPexpect() in generator
object _TOPCOM_exec at
You need to restart the notebook since the test output is cached...
On Monday, July 1, 2013 9:36:36 PM UTC-4, Ursula wrote:
On 7/1/2013 8:26 PM, Volker Braun wrote:
The interface checks whether the utility program points2placingtriang
from TOPCOM is available, and didn't find it in your
:26:03 PM UTC-4, Ursula wrote:
On 7/1/2013 8:42 PM, Volker Braun wrote:
You need to restart the notebook since the test output is cached...
Yes, that seems to have solved the problem. You might want to add a
note to this effect in the documentation for Triangulations of a point
Do we have a wiki page with more up-to-date overview? If not it would be
nice to create one...
On Wednesday, July 3, 2013 10:50:39 AM UTC-4, kcrisman wrote:
See http://wstein.org/edu/2012/1062/projects/final/miloshevich-nason/ for
now-fairly-old status update. Not that we don't have enough
On Wednesday, July 3, 2013 11:06:02 AM UTC-4, Ursula wrote:
So why doesn't TOPCOM install with Sage by default?
Its a relatively large package for relatively small feature (regularity
testing of generated triangulations and finding triangulations that are not
connected by flips to the
Occasionally the patchbot client dies when it can't reach the server. It
would be better if it would retry indefinitely until the server is up
again. Relevant log follows:
REPORT
{'base': '5.11.beta3',
'deps': [13422],
'machine': ['Fedora', '18', 'x86_64', '3.9.5-201.fc18.x86_64', 'desktop'],
+1 for switching Algebras to CommutativeUnitalAlgebras (or so) and the
using Algebras for the most general algebra.
In fact, I don't understand why Algebras has to be in the global namespace.
I've never once found it useful to start an interactive session by
instantiating a new category. The
I think the support for generators in Parents is basically non-functional
at this point. You are better of implementing your own gens() method. See
also my related question here:
https://groups.google.com/d/msg/sage-devel/3c0vPGOWWMI/AUGgiTrJIigJ
ParentWithGens is deprecated, it is only in the
I'd be happy if there were more frequent reviews of updated packages, for
example I packaged Gap-4.6.3 (http://trac.sagemath.org/14039) and it just
lingered on trac until 4.6.4 came out. IMHO we should just get rid of some
of the red tap for pure version bumps; If the package maintainer makes
On Friday, July 5, 2013 7:33:49 AM UTC-4, Franco Saliola wrote:
categories.tab
That would be nice, too. Then you don't get useless (for interactive use)
categories showing up when you use tab-completion to search for
non-category stuff but you can still write doctests without having to
Sorry if I wasn't clear, the package maintainer must of course make sure
that the doctests pass. Usually there are some minor changes, e.g. we do
doctest the GAP version number which will always change. Or the output
order of the upstream source changes. That does require some good judgement
On Thursday, July 4, 2013 2:26:02 PM UTC-4, Snark wrote:
(1) My debian package only ships the dimension 11-enabled executables ;
Just to confirm, that is useless. Palp needs to be complied for different
dimensions. And you need to be careful with filesystem timestamp
granularity if you want
On Friday, July 5, 2013 3:06:55 PM UTC-4, Snark wrote:
And you need to be careful with filesystem
timestamp granularity if you want to do that programmatically, see the
palp spkg.
I don't understand what you mean at all.
Unless you exactly follow what the spkg does I'd recommend you
On Friday, July 5, 2013 3:42:13 PM UTC-4, Snark wrote:
- provides its own set of configure.ac + GNUmakefile.am, which were
forwarded upstream last time (but I still have to do it again with the
latest changes), where I added the various targets ;
Sounds good, I take it that it installs
On Saturday, July 6, 2013 1:02:54 AM UTC-4, Snark wrote:
Do we really need nef.x, poly.x, etc. ; I mean if the executables names
don't reflect what they are good for, perhaps we (both in sage and in
debian) should stick to -numd.x variants?
In principle we don't need an unnumbered poly.x,
And speaking of version bumps, there is a trivial IPython update that has
been sitting on trac for two weeks:
http://trac.sagemath.org/14810
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group and stop receiving emails
Frédéric Chapoton has written a patch at http://trac.sagemath.org/14733
that will beautify the Sage startup banner using some UTF-8 characters to
draw the box. This will display incorrectly in terminals that do not
support UTF-8. In that case, Sage still works but the box around the banner
is
On Monday, July 8, 2013 4:51:28 AM UTC-4, Nils Bruin wrote:
all the colour stuff should shut off automatically for a dumb terminal).
The colors are ansi escape sequences, they have nothing to do with unicode
for the record
Why require it for *just* the banner?
As I said already, we
On Monday, July 8, 2013 6:46:40 AM UTC-4, vdelecroix wrote:
If we allow an UTF-8 banner then we may also allow UTF-8 string
representations for Sage objects (why not?).
Kind of off topic, but I think there is no doubt that we will be using
UTF-8 for string representations at some point in
Look at Integer.__mod__ vs. Rational.__mod__, this'll make it clear how to
fix it.
Apparently the design decision was to call Rational.__mod__(int, Rational)
in that case. It would be nice to have some explanation why.
On Tuesday, July 9, 2013 6:28:20 AM UTC-4, Travis Scrimshaw wrote:
On Wednesday, July 10, 2013 10:27:08 AM UTC-4, Dima Pasechnik wrote:
ssh from strange terminals often garbles any kind of ascii art, leave
alone being UTF-8 clean etc.
I've been doing export TERM=vt100 much too much to trust
these things.
Do you actually have an example or are you just
Since evidently nobody who weighted in so far has actually tried the patch,
here are screenshots of a few different terminals:
http://boxen.math.washington.edu/home/vbraun/UTF8/
In particular, Putty works beautifully if you set it to UTF-8. And if you
don't then you can still use Sage just
If the special method returns NotImplemented, then Python will call the
reflected version. So if __mod__(a,b) returns NotImplemented, then Python
will call __rmod__(b,a). I think somewhere the dynamic class stuff strips
out the r and forwards it to __mod__(b,a), though that is definitely not
I would be in favor of having the sensible notation, that is, change what
is currently in Sage.
With Sage-6.0 coming up there would be a natural transition point. It is
easy to have a warning shown the first time that you multiply two
permutations and not show it in DOCTEST_MODE. We would then
On Friday, July 12, 2013 11:58:13 PM UTC-4, David Joyner wrote:
It boils down to defining a permutation group via a left action or
a right action. Some people favor left-actions, some right-actions.
But the question is, how is this right action that you speak of implemented
in Sage?
On Sunday, July 14, 2013 4:49:36 AM UTC-4, vdelecroix wrote:
As Volker Braun mentioned, the main problem is that it is possible to
write p(i) in Sage! I suggest that we remove the __call__ attribute of
permutations (it does not exists in GAP but I do not know for other
softwares). If we
Ideally there would not be a user-visible way to find out how Sage is being
run. Otherwise we'll just end up with code that only works with the
interface that the developer prefers (like the OSI disaster in ACPI
tables).
The differences should be abstracted away by the Sage api, so to show
That is correct. The change_ring() methods in Sage return a new object and
do _not_ modify the original object:
sage: x = toric_varieties.P2()
sage: x.base_ring()
Rational Field
sage: x.change_ring(GF(3)).base_ring()
Finite Field of size 3
sage: x.base_ring()
Rational Field
Similar:
sage: R =
Yes that line looks suspicious...
On Monday, July 15, 2013 7:40:36 PM UTC-4, Ursula wrote:
# Direct conversion a/b to F does not work in Sage-4.6.alpha3,
# so we go through SR, even though it is quite slow.
coefficients = (F(SR(coef)) for coef in coefficients)
--
You received this message
Thanks, looks great.
Is there a way to attach a git branch to the ticket via the web interface
or do you have to go through the XML-RPC? In other words, is there any
other documentation than
https://github.com/sagemath/sage_trac/blob/master/plugins/ticket_branch.py
On Wednesday, July 17,
I can confirm that its working for me. Here is my .ssh/config:
--- begin of snip ---
Host trac
Hostname trac.sagemath.org
#IdentityFile ~/.ssh/id_rsa_git if you want to use non-default
User git
Port
--- end of snip ---
$ ssh trac help
hello vbraun, this is gitolite3 (unknown)
When I click on the branch (u/mmezzarobba/fix_micro_release) then I get a
504 Gateway Time-Out. It seems that the three-way diff doesn't like that
old == base:
Timeout:
center is not a function but a method of Polyhedron_base. I suggest you
read up on object-oriented programming and Python if that that doesn't
answer your question.
I'm definitely interested in hyperplane arrangements, though. Do you have a
particular data structure in mind or is your plan to
a.is_separating_hyperplane
Please let me know if there are other things you would like to see
included.
Thanks,
Dave
On Sunday, July 21, 2013 2:34:16 PM UTC-7, Volker Braun wrote:
center is not a function but a method of Polyhedron_base. I suggest you
read up on object-oriented
On Sunday, July 21, 2013 8:35:24 PM UTC-4, davidp wrote:
At the moment, I just have Hyperplane as a class deriving from
AffineSpace (my version of AffineSpace, that is, which I will change, as
noted above), and HyperplaneArrangement deriving from object. Can you
spell out your idea a bit
If the class is just used internally to keep track of intersections of
hyperplanes then it doesn't really matter what it is called since it will
not be in the global namespace. In fact, you probably only need
HyperplaneArrangement constructor and the hyperplane_arrangements factory
in the
Upstream does not allow the input transformer to fail, so either its a
not-yet-implemented feature in IPython or we are abusing the IPython
mechanism to parse the input where only trivial transformations should be
done. Can you post this to the ipython mailinglist?
On Wednesday, July 24,
On Thursday, July 25, 2013 2:05:38 PM UTC-4, Jeroen Demeyer wrote:
On 07/08/2013 04:05 AM, Volker Braun wrote:
Of course, various Sage source files are already UTF-8 encoded,
Editors like vim for
example can correctly transcode between file and terminal encodings. If
your terminal
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:
The __classcall__ is used just as a shortcut (well arguably its not shorter
but lets say it is for the sake of the argument) for the factory function
pattern. That is,
def Foo(x):
return Foo_class(x)
class Foo_class:
def __init__(self, x):
is 100% equivalent to:
class
On Sunday, July 28, 2013 9:06:54 PM UTC-4, Simon King wrote:
Sure. But the question is: SHOULD there be more than a factory function?
Well I don't really want to defend __classcall__ feature, but the fact is
that the way it is used in Sage is not restricted to creation of instances
of the
The recommended workflow for Sage is the Simple Workflow. You can use
github or any other repo to collaborate, but you'll have to push the final
result to the Sage trac server to add it to a ticket. You should base your
edits on the most recent Sage version. You can already use git, we'll
On Wednesday, July 31, 2013 1:45:42 AM UTC-4, Travis Scrimshaw wrote:
I don't like factory functions since you call Permutations(blah) and get
an object of type Permutations_class, which make the code more difficult to
understand wrt type-checking.
First of all you shouldn't type check.
On Wednesday, July 31, 2013 8:57:35 PM UTC-4, Travis Scrimshaw wrote:
Suppose you have [...]
Sometimes you might have to check the type in library code, but it
shouldn't be necessary for the user. You'll have to know about the factory
function pattern if you want to read and understand
Use timeit to benchmark:
sage: timeit('1+1')
625 loops, best of 3: 729 ns per loop
man time will explain real/user/sys if you want to know:
The time command runs the specified program command with the
given arguments. When command
finishes, time writes a message to standard
I tend to be in favor of the True/False/raise Exception model for testing
equality, but has anybody looked into what would be involved to transition
the Sage ilbrary? I imagine we would have to adapt a lot of code.
On Wednesday, July 31, 2013 5:33:30 AM UTC-4, kro...@uni-math.gwdg.de wrote:
timeit() repeats the benchmark a number of times and prints the best time.
Sometimes the run time is slower because of background processes, and the
best time over all loops is a reasonably stable measure of how fast the
code really is. The number of loops is just for your information; tests
On Friday, August 2, 2013 2:55:03 PM UTC-4, Keshav Kini wrote:
It's not recommended? Debian seems to recommend it:
https://wiki.debian.org/Locale#SSH_Client
Well its definitely not recommended if your locale is not installed on the
remote computer you are logging in to ;-)
OpenSSH
Its always hard to please everybody, We haven't really reached any
consensus, nor does it sound like there is much to be gained by further
discussion. So i'll set the ticket to positive review and leave you with
Lichtenberg's aphorism:
Ich weiss nicht, ob es besser wird, wenn es anders wird.
For the record, the future is UTF-8 instead of ISO-8859-1 / Latin-1. Unless
you have a need to stick to the old ways its better to use en_GB.utf8
On Friday, August 2, 2013 3:42:16 PM UTC-4, John Cremona wrote:
The diagnosis was correct: I was ssh-ing from my desktop where the set
is our
Hi all,
I'm planning to be in San Diego from Nov 8-10 so I could come relatively
easily to the first three days...
Best,
Volker
On Tuesday, August 6, 2013 10:58:13 PM UTC+1, Anne Schilling wrote:
Dear Sage-(combinat) developers!
Dan Bump, Travis Scrimshaw and I are planning to host Sage
There are currently three mentors listed at
http://wiki.lmona.de/get_involved/projects, are we just talking about
replacing one? Or all? IMHO there needs to be at least one person familar
with Sage on the project since she isn't that familiar with the process.
Also, I think we should really
Since the factorization starts with 2^64 it looks like there is something
wrong with how uint64_t is being used in the computation. Possibly a
32-bit/64-bit problem.
On Saturday, August 10, 2013 8:30:06 PM UTC+1, Snark wrote:
Le 10/08/2013 21:04, rjf a �crit :
for what it's worth, here's
Whats experimental about it? unstable pari, compiler, both? The currently
stable Pari has at least one bug
with unspecified behavior in a setjmp() that may be cause trouble depending
on the compiler.
On Monday, August 12, 2013 11:19:29 AM UTC+1, Snark wrote:
Le 10/08/2013 22:16, Volker
On Monday, August 12, 2013 12:36:45 PM UTC+1, Snark wrote:
It's experimental because it's Felix Salfelder's build system.
So I guess that means Pari without patches/mp.c.patch
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from
For the record, I found out how you end up with the U+200B, this always
happens when you paste a url from a trac page with chrome. For example, the
sage trac homepage has
Your trac account also grants you access to a class=ext-link
href=http://wiki.sagemath.org;span class=icon/spanthe sage
This is http://trac.sagemath.org/ticket/14737
On Wednesday, August 14, 2013 8:00:53 PM UTC+1, Snark wrote:
Hi,
the compilation fails in singular with:
In file included from ../kernel/si_gmp.h:4:0,
from ../kernel/structs.h:15,
from weight0.c:13:
This is http://trac.sagemath.org/ticket/14694
On Friday, August 16, 2013 9:54:07 PM UTC+1, François wrote:
Hi Roland,
Not inappropriate, but the request is better made on the sage-devel
mailing list. I may try to shepherd it personally but I am not the only
person that can do it. I
I noticed the same thing. It would be nice if we would get delete
permissions for questions (and ideally also for user accounts) with a
certain karma threshold.
On Saturday, August 17, 2013 1:53:11 PM UTC+1, kcrisman wrote:
There has been a fairly regular stream of spam on ask.sagemath.org
With the new Trac and Git it becomes much easier to script actions on
tickets and source code changes. The proposed sage-dev scripts will add
that such functionality to the Sage command line. But I think the full
potential to tie together Trac/Git would be a graphical user interface that
leads
Without the new atlas you won't be able to use AVX so that shiny new CPU
will not get even close to maximum floating point performance.
If you just want to compile Sage quickly then use an atlas that you compile
once (or your OS version) and set SAGE_ATLAS_LIB when building Sage.
--
You
Different ATLAS versions have different routines so the architectural
defaults for one version don't necessarily match another version.
If you don't want top performance then you can always set
SAGE_ATLAS_ARCH=fast or SAGE_ATLAS_ARCH=base when compiling Sage, this will
use some generic
Can you post the ATLAS bulid log, not the whole log that has everything
munged together?
Also, please try
On Monday, August 19, 2013 1:30:01 PM UTC+1, Christian Nassau wrote:
The full build log is at
http://nullhomotopie.de/sage512build.log.gz
Cheers,
Christian
--
You
On Monday, August 19, 2013 2:33:52 PM UTC+1, John Cremona wrote:
I don't know how to extract that from the munged version (which is
still being written to).
$SAGE_ROOT/logs/pkgs/atlas-3.10.1.p3.log
Also, please try
anything!
I meant:
sage
-f
Yes, shoud be fixed by http://trac.sagemath.org/ticket/15045
On Monday, August 19, 2013 2:47:41 PM UTC+1, Christian Nassau wrote:
On 08/19/2013 03:30 PM, Volker Braun wrote:
Can you post the ATLAS bulid log, not the whole log that has
everything munged together?
Here it is: http
On Monday, August 19, 2013 5:07:32 PM UTC+1, Nicolas M. Thiéry wrote:
Exception RuntimeError: 'maximum recursion depth exceeded' in
function remove at 0x398c2a8 ignored
Would anyone have any clue on what might be the cause or how to debug
this?
Obviously you are deleting
On Monday, August 19, 2013 5:57:01 PM UTC+1, Dima Pasechnik wrote:
it should be possible to tell Sage to use Atlas from the previous build,
just as one is able to use a system-wide Atlas.
It is, just point SAGE_ATLAS_LIB at the directory containing the ATLAS
libraries.
--
You received
Both sagecell.sagemath.org and trac.sagemath.org live on the same IP, so
they can't both use SSL. Which is a pity, we need https to avoid broken
transparent proxies and we should be using SSL with trac too. But two
name-based vhosts with SSL is generally a bad idea, though it can be hacked
That is because of the new
displayhook http://trac.sagemath.org/ticket/14469, which decides whether to
show something graphically by whether an object has a _graphics_() method
or not. Apparently pymongo uses a getattr hack that claims to have all and
every method implemented, and then fails
You need a UTF-8 capable terminal (independently of Sage it would be a good
time to switch). See also screenshots at:
http://boxen.math.washington.edu/home/vbraun/UTF8/
On Tuesday, August 20, 2013 2:14:41 PM UTC+1, John Cremona wrote:
5.12 introduced a new encoding for the Sage header. I
On Tuesday, August 20, 2013 2:51:41 PM UTC+1, John Cremona wrote:
It is GNOME Terminal 2.28.2. The banner looks fine on my laptop --
running ubuntu 12.04 -- but not when I log into a remote machine
(ubuntu 12.04) from my desktop .
What are you running on your desktop? The terminal
Does it work if you start the terminal on your desktop with
LANG=en_GB.UTF8 gnome-terminal
(or whatever other UTF8 locale you have installed)
On Tuesday, August 20, 2013 3:04:19 PM UTC+1, John Cremona wrote:
On 20 August 2013 14:58, Volker Braun vbrau...@gmail.com javascript:
wrote
At least you see that you have a problem with UTF8 immediately and not only
after you send in patches with the wrong encoding
On Tuesday, August 20, 2013 5:53:37 PM UTC+1, Snark wrote:
Le 20/08/2013 18:27, Dima Pasechnik a écrit :
And you people didn't believe me when I said that UTF-8
Slnr decodes base64 in bodies by default since version 0.9.6.4. Which is at
least 10 years old by now. Which version are you using?
On Wednesday, August 21, 2013 4:01:49 AM UTC+1, Dima Pasechnik wrote:
So, could you (or someone else) please tell me how to configure slrn so
that I can read
mysterious reason. You need to add
interpret mime.sl
to your .slrnrc
On Wednesday, August 21, 2013 1:37:37 PM UTC+1, Simon King wrote:
Hi Volker,
On 2013-08-21, Volker Braun vbrau...@gmail.com javascript: wrote:
--=_Part_9509_16842449.1377077319452
Content-Type: text/plain
Hmm doesn't work with slrn 1.0.1 but works with slrn pre1.0.2-9. I guess
its a cutting-edge feature.
On Wednesday, August 21, 2013 3:13:53 PM UTC+1, Simon King wrote:
Hi Volker,
On 2013-08-21, Volker Braun vbrau...@gmail.com javascript: wrote:
Most messages in sage-devel are actually
701 - 800 of 3731 matches
Mail list logo
