Yo !
There are 9 tests in sage/graphs/graph_plot.py that are not
being run
Those are fixed in http://trac.sagemath.org/ticket/18658 (needs_review)
Nathann
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this
I am still trying to post revisions to sandpile.py. The next issue is
compiling sage with the git-trac directory. The file pexpect.py seems to
be missing. Here is the error message:
Found local metadata for conway_polynomials-0.4.p0
Using cached file
For graphs, the list is also long and is separated by theme (everything done
by hand) :
I also like those a lot:
http://doc.sagemath.org/html/en/reference/graphs/sage/graphs/graph_generators.html
http://doc.sagemath.org/html/en/reference/combinat/sage/combinat/designs/database.html
It would be
For graphs, the list is also long and is separated by theme (everything
done by hand) :
http://doc.sagemath.org/html/en/reference/graphs/sage/graphs/generic_graph.html
See also sage/graphs/graph_plot.py for an example of how __doc__ string is
being created using a for loop.
Sébastien
--
You
On Tue, 9 Jun 2015, Anne Schilling wrote:
Some of us at Sage Days 65 are looking at the long list of methods that
exist for certain objects, for example in the Permutation
http://doc.sagemath.org/html/en/reference/combinat/sage/combinat/permutation.html#sage-combinat-permutation
I have just
For graphs, the list is also long and is separated by theme (everything
done by hand) :
http://doc.sagemath.org/html/en/reference/graphs/sage/graphs/generic_graph.html
See also sage/graphs/graph_plot.py for an example of how __doc__ string is
being created using a for loop.
Sébastien
--
You
On 2015-06-10 08:05, John H Palmieri wrote:
It looks to me as though many of these should be run, but they are not
because of a combination of the formatting of the docstring and the
doctesting infrastructure.
Yes, this is
http://trac.sagemath.org/ticket/14272
--
You received this message
For graphs, the list is also long and is separated by theme (everything done
by hand) :
I also like those a lot:
http://doc.sagemath.org/html/en/reference/graphs/sage/graphs/graph_generators.html
http://doc.sagemath.org/html/en/reference/combinat/sage/combinat/designs/database.html
It would be
I've already tried that. I get the same error message.
On Wednesday, June 10, 2015 at 6:55:00 AM UTC-7, Volker Braun wrote:
Try to rebuild everything from scratch (make distclean make). Will take
a while...
On Wednesday, June 10, 2015 at 3:13:15 PM UTC+2, David Perkinson wrote:
I am
Which version of Sage are you trying to build and whats in
logs/pkgs/pexpect-2.0.p6.log? The first error is relevant, the last error
is probably not.
On Wednesday, June 10, 2015 at 4:09:11 PM UTC+2, David Perkinson wrote:
I've already tried that. I get the same error message.
On
Try to rebuild everything from scratch (make distclean make). Will take
a while...
On Wednesday, June 10, 2015 at 3:13:15 PM UTC+2, David Perkinson wrote:
I am still trying to post revisions to sandpile.py. The next issue is
compiling sage with the git-trac directory. The file
Hello,
I am having trouble installing development version of Sage on my Mac.
(OSX10.9.5, with CommandLineTools for XCode 6.1.1 installed)
The error is Error installing package mpfr-3.1.2.p0
Here is the tail of the log file created, which seems to point to not
finding float.h
(But it can be
This is the same problem I just posted: see the message with subject header
trouble compiling sage in git-trac.
On Wednesday, June 10, 2015 at 7:36:09 AM UTC-7, Dinakar Muthiah wrote:
Hello,
Yesterday, I tried to build the development branch of Sage on my machine
and failed. Apparently,
Hello,
Aaron Lauve at Sage Days 65 is having trouble installing development version of
Sage on my Mac.
(OSX10.9.5, with CommandLineTools for XCode 6.1.1 installed)
The error is Error installing package mpfr-3.1.2.p0
Here is the tail of the log file created, which seems to point to not finding
Sage version 6.8.beta3, released 2015-06-04
There is no logs/pkgs/pexpect-2.0.p6.log.
On Wednesday, June 10, 2015 at 7:17:30 AM UTC-7, Volker Braun wrote:
Which version of Sage are you trying to build and whats in
logs/pkgs/pexpect-2.0.p6.log? The first error is relevant, the last error
Hello,
Yesterday, I tried to build the development branch of Sage on my machine
and failed. Apparently, the error occurs when attempting to build
conway_polynomials-0.4.p0.
Here are my machine specs:
Lubuntu 14.10 Virtual Machine running on Mac OSX Lion
The underlying hardware is a MacbookAir.
I noticed the following in doctest/sources.py:
There are 7 tests in sage/combinat/dyck_word.py that are not
being run
There are 4 tests in sage/combinat/finite_state_machine.py that
are not being run
There are 6 tests in sage/combinat/interval_posets.py that
Yo !
Me neither. The current situation isn't ideal, but just removing one
page and merging everything else doesn't help.
That's not what the pull request does.
Nathann
--
You received this message because you are subscribed to the Google Groups
sage-combinat-devel group.
To unsubscribe
Well, that's a little bit insulting. I'm that nobody and just for
the record, I did work quite a lot of work last august.
Well no, nobody means nobody. You are the first one who told me
about these scripts that nobody understands.
You could also ask me -- but despite that, I do not really
git-trac should never be imported in Sage, and it doesn't look that way
from the traceback.
SAGERUNTIME should depend on PEXPECT, directly or indirectly.
On Wednesday, June 10, 2015 at 5:32:35 PM UTC+2, Nathann Cohen wrote:
H... Even if it works it is not a good fix :-/
Volker, what
git-trac should never be imported in Sage, and it doesn't look that way from
the traceback.
Oh. True. It seems that /home/davidp/sage-devel/git-trac-command/ is
SAGE_ROOT O_o
SAGERUNTIME should depend on PEXPECT, directly or indirectly.
Yes yes yes, that makes sense. But right now it
Success!
Thanks for the help.
On Wednesday, June 10, 2015 at 8:25:59 AM UTC-7, Nathann Cohen wrote:
Yo !
which will take several hours, or is some variant of the following
better:
The second should work. No reason to destroy what you already built I'd
say.
Nathann
--
You
H... Even if it works it is not a good fix :-/
Volker, what do you think of this scenario:
- the git-trac module has been installed before conway_polynomials
- you don't need pexpect to *install* git-trac, but you need pexpect
to load the git-trac modules
- installing conway_polynomials calls
In case you didn't catch it, Nathann Cohen came up with a solution:
Find the file called 'dependencies' in
SAGE_ROOT/build/pkgs/conway_polynomials/ and replace the line
| $(SAGERUNTIME)
with
$(INST)/$(PEXPECT) | $(SAGERUNTIME)
Then run:
export SAGE_KEEP_BUILT_SPKGS='yes'
make
Post logs.
Usually its cruft in /usr/local that gets picked up.
On Wednesday, June 10, 2015 at 7:46:51 PM UTC+2, Mike Zabrocki wrote:
We are at Sage Days 65 and we are having trouble compiling Sage 6.7 on a
Mac with OSX 10.10 and a very recently updated xcode and command line tools.
The
Success!
Thanks for the help.
You can remove the modification that you made to that file, it is
useless now. You probably won't even need it next time you will update
your version of Sage (though you may need it if you run 'make
distclean' again).
And we will try to fix this soon.
Nathann
Since Apple declined to fix the rootpipe bug in OSX 10.9 I would
recommend to upgrade to OSX 10.10 asap, effectively you don't receive
security fixes any more.
Even then, why did you not upgrade to command line tools 6.2? They should
still run on OSX 10.9
On Wednesday, June 10, 2015 at
The log has filesystem references to the buildbot, so apparently you are
trying to use the binary build for development. Try to run make distclean
make overnight...
On Wednesday, June 10, 2015 at 7:46:51 PM UTC+2, Mike Zabrocki wrote:
We are at Sage Days 65 and we are having trouble
And we will try to fix this soon.
Done at #18666 [1] (needs_review)
Nathann
[1] http://trac.sagemath.org/ticket/18666
--
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
Thanks! I am trying it right now, and I will report if it works.
On Wednesday, June 10, 2015 at 12:25:43 PM UTC-4, David Perkinson wrote:
In case you didn't catch it, Nathann Cohen came up with a solution:
Find the file called 'dependencies' in
SAGE_ROOT/build/pkgs/conway_polynomials/ and
For whatever it's worth, I have the same issue. The mathjax stuff looks
like it's working, but then when processing hits 100%, all of the latex
is replaced with [Math Processing Error]. I have the following in my JS
console:
Error: TypeError: c.FONTDATA.FONTS.MathJax_Main[8212][5] is undefined
Volkar:
Here's more info:
weehawken:sage-git lauve$ gcc --version
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr
--with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 6.0 (clang-600.0.56) (based on LLVM 3.5svn)
Target: x86_64-apple-darwin13.4.0
Thread
We are at Sage Days 65 and we are having trouble compiling Sage 6.7 on a
Mac with OSX 10.10 and a very recently updated xcode and command line tools.
The message is that The following packages(s) may have failed to build:
libgd-2.1.1.p0
We looked and there were tickets #18293 and #18364 that
On Wednesday, 10 June 2015 11:41:37 UTC-6, Michael Orlitzky wrote:
For whatever it's worth, I have the same issue. The mathjax stuff looks
like it's working,
It is working and first shows you fast-preview using HTML fonts - it
appears very quickly and look OK for simple formulas, but
Hi all,
over at http://trac.sagemath.org/ticket/18437 we have
some heated debate about what to do about polybori.
Let me summarize the situation.
* at this moment polybori is dead upstream
* polybori is the last package using scons
* is one of the last packages, if not the last, not
ready for
CommandLineTools for XCode 6.1.1 is old and buggy... Also, are you sure you
are using the compiler you think you are using? You can have multiple ones.
Output of gcc --version?
On Wednesday, June 10, 2015 at 4:37:13 PM UTC+2, Anne Schilling wrote:
Hello,
Aaron Lauve at Sage Days 65 is
I have absolutely nothing invested in this, but I am curious about whether
bringing (as much as possible of) polybori into the Sage library or
extcode-successor or something would help people revivify the project? I
don't know how many people there are out there who would be potentially
On Wed, Jun 10, 2015 at 6:40 PM, François Bissey
francois.bis...@canterbury.ac.nz wrote:
Hi all,
over at http://trac.sagemath.org/ticket/18437 we have
some heated debate about what to do about polybori.
Let me summarize the situation.
* at this moment polybori is dead upstream
* polybori
I thought I was going to misrepresent stuff, but may be not to that extent.
If we fork polybori I do not see the point of patching it for sage on top
of the fork. (3) is very much out as far as I am concerned.
François
On 11/06/2015, at 14:08, R. Andrew Ohana andrew.oh...@gmail.com wrote:
On 06/11/15 14:39, William Stein wrote:
I could easily imagine Andrew and Francois and Jereon are all
dutifully imagining that I know all kinds of Polybori enthusiasts and
there are good reasons that Polybori really must be really well
supported in Sage. However, it turns out this at least
Ah, yes, that makes sense. I should have thought of that! Your suggestion
worked perfectly, thanks.
On Wednesday, June 10, 2015 at 3:39:03 PM UTC-5, Volker Braun wrote:
The log has filesystem references to the buildbot, so apparently you are
trying to use the binary build for development.
On Wednesday, June 10, 2015, Ralf Stephan gtrw...@gmail.com wrote:
There is not much difference between 1 and 2 because, while there is no
review mechanism for Pynac admin commits on github, it's on trac instead.
And the real problem is always the language barrier: adding C++ to an
already
Hi,
Can somebody (say at least 3-5 people) who actually *use* polybori on
a somewhat regular basis make some supporting remarks?I personally
have used polybori for anything, nor do I really know of anybody else
who has. If there aren't at least a few people who use it regularly,
then we
On Wednesday, June 10, 2015, François Bissey
francois.bis...@canterbury.ac.nz wrote:
On 06/11/15 14:39, William Stein wrote:
I could easily imagine Andrew and Francois and Jereon are all
dutifully imagining that I know all kinds of Polybori enthusiasts and
there are good reasons that
There is not much difference between 1 and 2 because, while there is no review
mechanism for Pynac admin commits on github, it's on trac instead. And the real
problem is always the language barrier: adding C++ to an already huge skillset
is too much for many authors and most reviewers,
On Wednesday, June 10, 2015 at 4:34:01 PM UTC+2, David Perkinson wrote:
There is no logs/pkgs/pexpect-2.0.p6.log.
So that explains your error. You need to check the build log to find out
why; presumably some dependency failed.
--
You received this message because you are subscribed to the
David: there is in SAGE_ROOT/build/pkgs/conway_polynomials/ a file
named 'dependencies', whose first line should be:
| $(SAGERUNTIME)
Could you replace it with
$(INST)/$(PEXPECT) | $(SAGERUNTIME)
And tell us if running 'make' works better then?
Nathann
On 10 June 2015 at 17:13,
So that explains your error. You need to check the build log to find out
why; presumably some dependency failed.
conway_polynomial does not state a dependency on pexpect. Couldn't
this be the problem?
Nathann
--
You received this message because you are subscribed to the Google Groups
Sure, I can try that. Should I enter:
make distclean make
which will take several hours, or is some variant of the following better:
export SAGE_KEEP_BUILT_SPKGS='yes'
make
Thanks.
On Wednesday, June 10, 2015 at 8:17:07 AM UTC-7, Nathann Cohen wrote:
David: there is in
Yo !
which will take several hours, or is some variant of the following better:
The second should work. No reason to destroy what you already built I'd say.
Nathann
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group
50 matches
Mail list logo
