with ''.
At least the last part should probably give an appropriate error message
telling when something (or what) went wrong:
if [ $? -ne 0 ]; then
echo 2 Error: Failed to copy ... to ...
exit 1
fi
SPKG.txt looks ok to me.
-leif
- The documentation says that if I want to make the package
the whole LaTeX stuff.]
Rebuilding dot2tex in contrast wouldn't be necessary.
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
sage-combinat-devel group.
To unsubscribe from this group and stop receiving
leif wrote:
John H Palmieri wrote:
On Wednesday, May 22, 2013 9:58:56 AM UTC-7, Nicolas M. Thiéry wrote:
On Wed, May 22, 2013 at 09:13:09AM -0700, kcrisman wrote:
A standard package which is only useful in the presence of
an optional
package doesn't make sense
, cf. #14600.
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
sage-combinat-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-combinat-devel+unsubscr
leif wrote:
See neighbour thread Dig through stack for printing an
object?.
Neighbour thread on sage-devel that is.
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
sage-combinat-devel group
* to read
because of its length (or width).
-leif
[1]
http://sagemath.org/doc/developer/coding_in_python.html#special-sage-functions
You see _add_ and wonder what it does and think that
_add_after_coercion_ or so would be a better name. But try to think
from the point of view
was mainly referring to the __foo__ vs. _foo_
part, where (I think) once you've read why they're both there, it's not
necessary to restate the difference everywhere by giving the latter a
different name.
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message
in combination with -
Werror[=...] or -Wno-error=... wouldn't be bad, too (if it was
enabled on a compiler-sensitive basis).
-Leif
--
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...@googlegroups.com
(the latter
runs tests in parallel).
(The standard tests shouldn't take much more than an hour, with
long tests enabled, perhaps up to two+. The long option includes
the standard tests.)
Thanks,
-Leif
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from
have fun, count the asterisks...)
-Leif
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http
=/usr/local/gcc-4.4.4
--with-as=/usr/local/binutils-2.20/bin/as --with-ld=/usr/ccs/bin/ld
--with-gmp=/usr/local --with-mpfr=/usr/local
Thread model: posix
gcc version 4.4.4 (GCC)
-Leif
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send
to hunt down the doggy code myself, but
find $SAGE_ROOT/devel/sage/sage -name *.pyx -exec touch {} \;
would probably do what the above intends to do, but in a slightly more elegant
way.
Exactly.
-Leif
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe
on the trac ticket.
Certainly.
-Leif
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http
On 24 Mai, 01:18, Tim Daly d...@axiom-developer.org wrote:
how about using:
find . -name *.pyx -exec touch {} \;
We can save one more character:
find . -name \*.pyx -exec touch {} \;
-Leif
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group
On 24 Mai, 14:26, geep999 peter.graham.gard...@googlemail.com wrote:
make ptestlong
All tests passed!
Total time for all tests: 4762.2 seconds
(=79.37 minutes with Linux 2.6.29.6 SMP x86_64 Intel(R)
Core(TM)2 Duo CPU E6550 @ 2.33GHz GenuineIntel GNU/Linux )
Thanks!
-Leif
--
To post
++ program against the 32-
bit libstdc++.so (in /usr/local/lib) instead of the 64-bit version in /
usr/local/lib64. (Actually it is forced to do so by libtool.)
-Leif
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel
we
got. This we regret deeply.
[...]
The MPIR web site (http://www.mpir.org/#about) does not state this,
especially not the motivation for the fork.
-Leif
--
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
.
After 4 fresh builds from scratch, the reason seems to have been
accidently setting CFLAGS to -march=native (reproducable).
ptestlong succeeded with the finally working build (empty CFLAGS).
(See sage-release for Ubuntu 9.04 x86/32-bit.)
-Leif
--
To post to this group, send an email to sage-devel
instead of
GMP and vice versa.)
-Leif
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http
for fixing bugs.
Can you put this in the Developer's Guide? ;-)
-Leif
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group
On 25 Mai, 02:13, Dr. David Kirkby david.kir...@onetel.net wrote:
On 05/24/10 05:26 PM, leif wrote:
Looks like the (fairly old) gcc/g++ in /usr/local is misconfigured; it
definitely tries to link a 64-bit (x86_64) C++ program against the 32-
bit libstdc++.so (in /usr/local/lib) instead
On 25 Mai, 11:18, leif not.rea...@online.de wrote:
What I wanted to say is that installing another version of gcc in /usr/
local on systems (like Linux distros) where there already is a
native one (gcc) in /usr is non-trivial, i.e. this doesn't work out
of the box.
With the native gcc
/group/sage-release/msg/dac6cb862ecf6a8e
-Leif
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http
On 25 Mai, 11:41, leif not.rea...@online.de wrote:
This is a known issue, and most probably ;-) not related to your
patch:
See e.g.http://groups.google.com/group/sage-release/msg/dac6cb862ecf6a8e
Direct link to the ticket:
http://trac.sagemath.org/sage_trac/ticket/9003
-Leif
--
To post
help narrowing the origin.
And what system are you on? (I guess it's some MacOS; CPU, 32bit?)
It wouldn't be bad if you add this information to
http://trac.sagemath.org/sage_trac/ticket/9003
-Leif
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group
On 26 Mai, 10:45, John Cremona john.crem...@gmail.com wrote:
Is it possible to remove spam postings to trac?
Seehttp://trac.sagemath.org/sage_trac/ticket/8681#comment:11(from
bascorp2)
Also on ticket #7613, comment 5 (by bascorp2, too).
-Leif
--
To post to this group, send an email
I want additional 2,4 MB in the Sage source distribution that
are only needed on !#$% (which already requires further
prerequisites, currently not included in Sage). /flame
[ ] No, I don't want Sage to work on Windows.
There are other alternatives.
-Leif
--
To post to this group, send
on sage-release/sage-
devel, with documentation of what was merged.
So far, I've found 17 tickets merged, 16 of them related to Cygwin;
some of them not closed the usual way.
(More to come on other threads, but or because it is early morning in
Seattle... ;-)
-Leif
--
To post to this group, send
? ;-)
50% of the tickets for 5.0 have already been closed (unfortunately,
that's only one out of two).
I like the risk assessment field idea.
Me too, perhaps give it a different name.
-Leif
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send
.
The search will now show up two more tickets - ready for review! :)
(I only hope the patches there don't have to be rebased again...)
-Leif
--
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
On 26 Mai, 19:23, William Stein wst...@gmail.com wrote:
On Wednesday, May 26, 2010, leif not.rea...@online.de wrote:
On 26 Mai, 03:38, William Stein wst...@gmail.com wrote:
On Tue, May 25, 2010 at 6:16 PM, Mike Hansen mhan...@gmail.com wrote:
Hello,
I propose to make Cephes (http
On 26 Mai, 19:39, leif not.rea...@online.de wrote:
On 26 Mai, 19:23, William Stein wst...@gmail.com wrote:
On Wednesday, May 26, 2010, leif not.rea...@online.de wrote:
On 26 Mai, 03:38, William Stein wst...@gmail.com wrote:
On Tue, May 25, 2010 at 6:16 PM, Mike Hansen mhan...@gmail.com
On 26 Mai, 20:00, Robert Bradshaw rober...@math.washington.edu
wrote:
On May 26, 2010, at 10:47 AM, leif wrote:
SNIP
There are other alternatives.
Such as?
* As I said above, incorporate it into Cygwin.
* Provide an optional spkg.
* Provide (it with) Cygwin or a patch to Cygwin
On 26 Mai, 20:25, Robert Bradshaw rober...@math.washington.edu
wrote:
On May 26, 2010, at 11:13 AM, leif wrote:
In the long term, many packages should be moved from the main tarball/
made prerequisites, such that you only have to download them if you
really need them.
One of the points
On 26 Mai, 20:46, Robert Bradshaw rober...@math.washington.edu
wrote:
On May 26, 2010, at 11:43 AM, leif wrote:
On 26 Mai, 20:25, Robert Bradshaw rober...@math.washington.edu
wrote:
On May 26, 2010, at 11:13 AM, leif wrote:
In the long term, many packages should be moved from the main
.
I Sage, there's no tab-completion for file names (and the syntax is
odd, and Sage takes too long to start up).
(There's no usage tab-completion in ./sage -hg ... either.)
From the shell, just type e.g. hg help commit... (./sage -hg help
commit)
-Leif
--
To post to this group, send an email
On 26 Mai, 21:50, Dr. David Kirkby david.kir...@onetel.net wrote:
On 05/26/10 05:34 PM, leif wrote:
On 26 Mai, 18:09, Robert Bradshawrober...@math.washington.edu
I like the risk assessment field idea.
Me too, perhaps give it a different name.
What would you call it? There are at least
commit messages. Ideally, Mercurial would provide the fields to
fill (like trac, though I still consider it sub-optimal, too) - with a
brief, concise explanation.
-Leif
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage
to some other thing).
-Leif
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
On 27 Mai, 00:52, Dr. David Kirkby david.kir...@onetel.net wrote:
On 05/26/10 09:48 PM, leif wrote:
On 26 Mai, 21:50, Dr. David Kirkbydavid.kir...@onetel.net wrote:
On 05/26/10 05:34 PM, leif wrote:
I like the risk assessment field idea.
Me too, perhaps give it a different name.
What
On 27 Mai, 01:11, William Stein wst...@gmail.com wrote:
On Wed, May 26, 2010 at 4:06 PM, leif not.rea...@online.de wrote:
On 27 Mai, 00:08, Tim Daly d...@axiom-developer.org wrote:
[...]
There is a choice between releasing often and releasing,
say, yearly. Sage releases about every week
-CDs for getting an impression
before updating/installing (though I even hate reboots).
And it's easy to have/keep multiple Sage installations, a rarely
available opportunity.
-Leif
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email
(...), show_changes(), create_patch(), export_patch(...)
etc.?
(The functions could then also explain what they do, if verbose=True.)
This could be useful for the next switch of the revision control
system, too. ;-)
-Leif
--
To post to this group, send an email to sage-devel@googlegroups.com
users won't care about updates because they're
made by admins; they will most probably notice them though.)
-Leif
--
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...@googlegroups.com
For more options, visit
On 27 Mai, 16:59, kcrisman kcris...@gmail.com wrote:
On May 27, 10:32 am, leif not.rea...@online.de wrote:
On 27 Mai, 02:34, William Stein wst...@gmail.com wrote:
On Wed, May 26, 2010 at 5:31 PM, kcrisman kcris...@gmail.com wrote:
Not without having someone over your shoulder
variables.
-Leif
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
to help output (of shell scripts in this
case)...
Maybe patches on trac should not be approved, if the guidelines are not
followed. ;-)
If the conventions are relaxed, yes. :)
(Oh, yes, I know that sage-sage is a bash-script.)
-Leif
--
To post to this group, send an email to sage-devel
-2.3
-Leif
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
-Leif
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
://trac.sagemath.org/sage_trac/ticket/9086
sage -t -long devel/sage/sage/sets/set.py # 1 doctests failed
Same on Linux.
-Leif
--
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...@googlegroups.com
For more
On 1 Jun., 17:45, Ondrej Certik ond...@certik.cz wrote:
Hi,
just found a video of a Matlab running in the phone:
http://www.mathworks.com/mobile/videos.html
Actually only an iPhone app.
(Regarding the thread title I was first thinking of a speech
recognition system... :) )
-Leif
I've replied to the sage-release thread...
http://groups.google.com/group/sage-release/browse_thread/thread/8df955269e44ead9#
-Leif
On 3 Jun., 00:02, William Stein wst...@gmail.com wrote:
On Wed, Jun 2, 2010 at 1:31 PM, Nicolas M. Thiery
nicolas.thi...@u-psud.fr wrote:
Dear release
of the slow down to Sphinx?
Could the use of macros be an alternative?
-Leif
--
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...@googlegroups.com
For more options, visit this group at http
On 3 Jun., 15:20, Florent Hivert florent.hiv...@univ-rouen.fr wrote:
On Wed, Jun 02, 2010 at 05:34:06PM -0700, leif wrote:
Any measures of the slow down to Sphinx?
I don't think it would be very measurable: Here is a comparison after issuing
# touch *.py sage -b time sage -docbuild
On 3 Jun., 18:58, Florent Hivert florent.hiv...@univ-rouen.fr wrote:
On 3 Jun., 15:20, Florent Hivert florent.hiv...@univ-rouen.fr wrote:
On Wed, Jun 02, 2010 at 05:34:06PM -0700, leif wrote:
Any measures of the slow down to Sphinx?
Does not really address my question. Think
]
sage -t -long devel/sage/sage/modular/abvar/homspace.py
[171.8 s]
sage -t -long devel/sa
The output buffer isn't flushed. You could try -verbose to get
closer to the doctest actually hanging.
-Leif
I wondered if this could be a lack of memory (the machine only has 2 GB
], Patching a Sage Package [3]);
I'm not sure if everybody will read the introductory Disseminating
Code for Sage [1]. Perhaps a hint in potentially affected spkgs'
SPKG.txt wouldn't be bad, too.
(The file permissions/ownership issue could also be mentioned in these
sections.)
-Leif
[1]
http
On 6 Jun., 19:02, Dr. David Kirkby david.kir...@onetel.net wrote:
On 06/ 6/10 04:43 PM, leif wrote:
[1]http://www.sagemath.org/doc/developer/disseminating_code.html#dissemi...
[2]http://www.sagemath.org/doc/developer/producing_spkgs.html#producing-...
[3]http://www.sagemath.org/doc
grammar.cc $;\
chmod +x testgh;\
./testgh;\
fi
Note that these are all from the same file. You could also take a look
at flexer.sh...
-Leif
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel
more left alone with (or pay much
for support hotlines).
-Leif
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group
passed.)
(Built with CFLAGS=-march=native -fno-strict-aliasing.)
-Leif
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group
with CFLAGS=-march=native -fno-strict-aliasing and CXXFLAGS=
$CFLAGS.)
-Leif
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com
it is
likely to be more portable (and nowadays should be supported on all
platforms...).
-Leif
With best regards,
Sergey mailto:sergey.bochka...@alglib.net
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send
into a long), use
intptr_t (oh wait, you can't, that's c99 only)
Actually, best to not use C if you want it to compile on anything. C
is broken. (Partly joking).
:-) Yes, reimplement all in pure lambda calculus.
-Leif
That's my opinion anyway. But if you *really, really* need c99, then
Sage
boxen, which is up).
-Leif
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
On 8 Jun., 20:33, William Stein wst...@gmail.com wrote:
It will be back soon...
Yes, it is up again.
Thanks,
-Leif
--
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...@googlegroups.com
For more options
upstream release).
We will see what Sage Days 23.5 bring... (see William's post above).
-Leif
--
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...@googlegroups.com
For more options, visit this group at http
) and then we could
make a nice, easy report of tickets by spkg.
+1
A drop-down box like component, without the version number?
We also have the keywords field. but that's unfortunately afaik
rather rarely used.
-Leif
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe
but not any more.
Something more to be investigated at the Sage/Singular meeting. :-)
-Leif
--
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...@googlegroups.com
For more options, visit this group at http
of
Singular was broken or not installed).
(I did not examine these tests, though I had been surprised how fast
they were finished.)
-Leif
--
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...@googlegroups.com
On 8 Jun., 22:14, Robert Bradshaw rober...@math.washington.edu
wrote:
On Jun 8, 2010, at 11:05 AM, leif wrote:
On 8 Jun., 19:25, Bill Hart goodwillh...@googlemail.com wrote:
My recommendation would be to stick with ANSI C as much as
possible. I
doubt comments // will be a problem
-1504.3.12~1/RELEASE_I386 i386 i386 MacPro1,1 Darwin
[kir...@bsd ~]$ pkgconfig
-bash: pkgconfig: command not found
though pkg-config exists on both Solaris (even my March 2005 release) and
Linux
systems.
Ooops? pkg-config vs. pkgconfig? ;-)
-Leif
--
To post to this group, send an email
paths in binaries are a known issue... ;-)
They do not necessarily break Sage after moving, but can be a security
issue (not really addressed yet).
This also affects binary dists (depending on where they have been
built).
-Leif
--
To post to this group, send an email to sage-devel@googlegroups.com
Maybe I missed some announcement?
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL:
, thanks for bringing back the services so quickly.
-leif
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
(where the error occurs); cf. #11447 [1].
Cheers,
-leif
[1] http://trac.sagemath.org/sage_trac/ticket/11447
--
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...@googlegroups.com
For more options, visit
On 13 Jul., 13:00, leif not.rea...@online.de wrote:
Please copy
http://spkg-upload.googlecode.com/files/python-2.6.4.p11.spkg
into your $SAGE_ROOT/spkg/standard/ directory and simply rerun make.
The updated spkg fixes the issue on /all/ (newer) Debians and
derivates (where the error occurs
' and
'sysctl' (or 'kern.osrelease') and make sure there's a proper less
than or alike.
I've fixed one instance of that in the MPIR 2.1.3.p3 spkg (#8664) just
a few days ago.
Just my 2 ct,
-leif
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group
*Slightly* related: ;-)
http://trac.sagemath.org/sage_trac/ticket/10458
(Doctest framework fails to parse multiline input pasted from sage
interactive prompt)
Hopefully Kini or me will return to and finish that...
-leif
--
To post to this group, send an email to sage-devel@googlegroups.com
supported different branches,
though it wouldn't be clear whether some dependencies are of
functional or just syntactical nature.
-leif
--
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...@googlegroups.com
box (like pocket calculators, phones and IRC
clients have it ;-) ). But perhaps that's also customizable when
embedding it into a page.
I observed that the output is interspersed with additional blank lines
(one or more in sequence), depending on how fast the server delivers.
-leif
--
To post
(only the after-context changed, cf.
http://trac.sagemath.org/sage_trac/ticket/8664#comment:121).
If no-one beats me, I'll open a ticket for upgrading MPFR to 3.0.1 +
latest upstream patches, and rewrite its spkg-install.
-leif
--
To post to this group, send an email to sage-devel
--
orthogonal properties; there's a lot of free software with closed
source, and there used to be also open source software (not in the
sense of open to contributing) which wasn't free, i.e. which one had
to license.
The symbols are ok, but I would omit the background graphic.
-leif
--
To post
On 3 Aug., 11:14, leif not.rea...@online.de wrote:
Hmmm, the font looks poor and not very well-designed (most disturbing
the kerning, as if some letters had been typeset manually or by M$
Word).
Note that I was referring to the png, not the PDF, which looks
slightly better.
-leif
always matters. ;-)
-leif
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
.
I.e., I did get some quite a while *after* trac was back, but the last
one I received is of 8:27 (PDT).
-leif
--
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...@googlegroups.com
For more options, visit
people not intentionally subscribed to them.
-leif
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL
-sage. Here, I see a
technical problem. Some replies are, technically, just comments. But
comments are not visible on the main ask-sage page - only proper
replies are visible.
There's also the IRC, channel #sagemath on irc.freenode.net, formerly
#sage-devel.
-leif
--
To post to this group
that all the sagemath computers are housed
in. Expect substantial downtime and random interruptions of
service for the near term.
-- William
Fortunately we have sage-flame...
-leif
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group
if others on the tickets will notice.
-leif
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http
/33 .)
-leif
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
imported later is
already imported right away, because we import sage/misc/all.py really
early on, which imports most functions from sage/misc/functional.py -
and that imports quite a bit of main Sage.
+1. I would love for this to get better cleaned up.
+N
-leif
--
To post to this group
packages ship with wrong permissions,
we should also report that upstream. (And checking file permissions
should be part of the review process; we should perhaps add a note on
that to the Developer's Guide.)
-leif
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe
as I know, nothing got queued up (according to Mike IIRC), so
unfortunately we'll need broadcast pings for all tickets modified
during the last few days.
Recent changes can be found here: http://trac.sagemath.org/sage_trac/report/33
-leif
--
To post to this group, send an email to sage-devel
Project Hosting will be READ-ONLY Tuesday at 9:00am CDT for brief
maintenance.
That's UTC-05, i.e. starting Tuesday 14:00 UTC if I'm not completely
wrong.
So if anybody should have urgent things to *upload*, do it now or
soon.
-leif
P.S.: Perhaps someone subscribed to sage-notebook could post
On 8 Aug., 20:59, Jeroen Demeyer jdeme...@cage.ugent.be wrote:
On 2011-08-08 20:11, leif wrote:
We could also create some post-install script that checks (and
optionally fixes) file permissions.
-1 because there is no reason to do it *post-install*, it would add
unnecessary complications
On 3 Aug., 09:51, leif not.rea...@online.de wrote:
On 2 Aug., 19:09, William Stein wst...@gmail.com wrote:
There is now a high priority wishlist of bugs/issues to work on for
Sage Days 32 (Bug Days):
http://wiki.sagemath.org/days32/wishlist
Of course, if anybody wants to start
after some
reasonable time, I'd set it to either Reported upstream. No
feedback. or Reported upstream, but no sufficient feedback. or the
like.
If no-one objects, can anybody change the trac configuration
accordingly?
-leif
P.S.:
I'd also like to have an SPKGs: field, to put the base package
See http://trac.sagemath.org/sage_trac/ticket/11663#comment:6 ff. for
reasons why it is in general *not* sufficient to just change the
permissions of all upstream files (in src/).
-leif
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send
it a feature rather than a bug.. ;-)
-leif
--
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...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http
1 - 100 of 1259 matches
Mail list logo
