On 2016-10-13 10:56, Jori Mäntysalo wrote:
I opened https://trac.sagemath.org/ticket/2169 to make some example.
I guess you mean that for example
ValueError("%s and %s must be positive integers." % (m, n))
should be as it is, but
ValueError("the poset is not ranked")
changed to ArithmeticErr
On 2016-10-12 18:14, Ethan Petersen wrote:
there was an "Error building OpenBLAS"/"Error installing package
openblas-0.2.19" with a suggestion to email this google group with the attached log file.
I'm glad that you did that! Almost *nobody* seems to read that message.
If anyone has ideas on
On 2016-10-12 13:39, Jori Mäntysalo wrote:
elements = D.topological_sort()
More bikeshedding: in this case, I would even consider ArithmeticError.
It's not strictly arithmetic, but it does indicate a mathematical issue.
I tend to use ArithmeticError for mathematical errors (something
On 2016-10-12 18:56, Jori Mäntysalo wrote:
So we have now a common view that 'type' in TypeError should (mostly?)
refer to types in wrong class, wrong category etc
For Sage, I would certainly add "wrong parent" to this.
Python also uses TypeError to indicate a function which is called with
th
On 2016-10-12 12:47, Jori Mäntysalo wrote:
After #21687 there are 341 lines in 172 files with
except Exception:
What can happen in, say has_vertex() in generic graphs, when it has the
code
try:
hash(vertex)
except Exception:
return False
return self._backend.ha
On 2016-10-11 09:38, Eric Gourgoulhon wrote:
Hi,
Since Sage 7.4.rc0, the patchbots hades and poseidon fail with the message:
[openblas-0.2.19] ./openblas_utest: error while loading shared libraries:
libgfortran.so.3: cannot open shared object file: No such file or directory
This is https://t
On 2016-10-11 19:05, Kwankyu Lee wrote:
I stopped hades. Is the fault with the patchbot, not with Sage 7.4.rc0?
No idea, I don't know the cause of the problem on hades.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this gr
On 2016-10-11 17:56, John Cremona wrote:
I will do that -- but I have never done anything other than follow
those instructions, and never knowking started running the patchbot
inside a Sage shell!
I never said it was your fault. It could very well be that the issue was
in the implementation or
On 2016-10-11 20:34, Frédéric Chapoton wrote:
I now have this problem on my own machine:
sage/rings/finite_rings/integer_mod.pyx:1688:10: '_floordiv_' already
defined
and this has nothing to do with any patchbot..
Since you seem to be the only one having this problem, you need to give
more d
On 2016-10-11 19:04, Frédéric Chapoton wrote:
if you look here, you see that almost all bots have failed to build 7.4.rc0:
https://patchbot.sagemath.org/ticket/0/
Some of these are temporary problems due to #21672. You will see that
arando for example managed to build some tickets successfull
On 2016-10-11 09:38, Eric Gourgoulhon wrote:
[sagelib-7.4.rc0] sage/rings/finite_rings/integer_mod.pyx:1688:10: '_floordiv_'
already defined
It seems that this machine is running the Sage patchbot within a Sage
shell, which is not supported. Because of this, the environment variable
PIP_INST
On 2016-10-11 10:14, John Cremona wrote:
That's me, send me your ssh key.
Here it is. Remember to give me the login details.
--
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
On 2016-10-11 09:38, Eric Gourgoulhon wrote:
Hi,
Since Sage 7.4.rc0, the patchbots hades and poseidon fail with the message:
[openblas-0.2.19] ./openblas_utest: error while loading shared libraries:
libgfortran.so.3: cannot open shared object file: No such file or directory
while fermat fail
On 2016-10-11 09:38, Eric Gourgoulhon wrote:
[sagelib-7.4.rc0] sage/rings/finite_rings/integer_mod.pyx:1688:10: '_floordiv_'
already defined
This looks like a typical error which was fixed by #21441. However, that
ticket is merged, so I don't have an explanation.
If someone can give me acce
On 2016-10-10 16:13, Victor Shoup wrote:
One more question, relating to $(MAKE). There are a number of scripts besides
the makefile that also invoke make. Should these also be modified? But then the
mechanism would have to be different (environment variable?). Before I can sort
that out, I wou
On 2016-10-07 15:04, Simon King wrote:
Nice! I see many checkmarks there. So, is stuff ready to use already
It's very much work in progress...
We have only really just started working on this.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To
On 2016-10-07 13:59, Simon King wrote:
That's why I ask here how to do it right...
Well, that's partially why we have
https://github.com/OpenDreamKit/OpenDreamKit/issues/87
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from thi
On 2016-10-07 14:02, Johan S. H. Rosenkilde wrote:
Would it be extremely difficult to attempt to satisfy this?
Python 3 would certainly make it a lot harder. Compare:
$ python2 -c "print(hash('hello'))"
840651671246116861
$ python2 -c "print(hash('hello'))"
840651671246116861
$ python2 -c "pri
On 2016-10-07 13:35, Johan S. H. Rosenkilde wrote:
The implementation of __hash__ on finite fields claims to be the same as
for 'object'.
Could be:
$ sage -c 'print(hash(object()))'
8790924175895
$ sage -c 'print(hash(object()))'
8771665328407
--
You received this message because you are subs
On 2016-10-07 13:35, Johan S. H. Rosenkilde wrote:
Should __hash__ be constant across Sage invocations?
No. I see no reason why it should be.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emai
On 2016-10-07 12:35, Simon King wrote:
Also, I'd like to build documentation. Sébastien has pointed me to
https://github.com/seblabbe/slabbe as an example of code that uses
Sage's doc formatting, and people here have pointed me to google docs.
However, my question is: Is the Makefile that I find
On 2016-10-06 12:58, 'Julien Puydt' via sage-devel wrote:
For those sage-is-upstream packages, I was pointing the helper to
http://files.sagemath.org/spkg/upstream/
but now it looks like those are not available anymore on the
sagemath.org server.
I believe that this is a temporary outage o
When running "git fetch", I get
remote: warning: unable to access
'/home/erik_m_bray/.config/git/attributes': Permission denied
--
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, se
On 2016-09-24 15:58, Thierry wrote:
On Sat, Sep 24, 2016 at 06:34:33AM -0700, Frédéric Chapoton wrote:
sage4 is going on as usual with 7.4.beta6, always giving us generously
wrong BuildFailed reports.
How was it not blocked when testing ticket 0 ? Perhaps should we require
each patchbot to ret
If you have an OS X system and want to help Sage and PARI:
1. Checkout the branch at https://trac.sagemath.org/ticket/21582
2. Run "./sage -i -c all-build"
3. Run "./sage -tp --long src/sage/libs/pari" (or "make ptestlong" if
you have the time)
4. Report back to sage-devel
--
You received t
On 2016-09-21 16:15, Jonathan Bober wrote:
(I've swtiched from sage-support to to sage-devel.)
I can test and review.
See https://trac.sagemath.org/ticket/21582
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and
On 2016-09-23 08:51, Ralf Stephan wrote:
What has that to do with stopping the bot (or monitoring it at all, for
that matter)?
Nothing with that. But it has *everything* to do with fixing the bot.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
On 2016-09-23 08:00, Ralf Stephan wrote:
Please stop spamming BuildFailed.
Please review #21430 (i.e. don't shoot the messenger but listen to the
message).
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and sto
On 2016-09-21 16:15, Jonathan Bober wrote:
(I've swtiched from sage-support to to sage-devel.)
I can test and review. I think I know what to do and I would have just
tried to implement this myself, except that it would take me a while to
figure out how to make the change in such a way that it fi
On 2016-09-21 14:42, Thierry wrote:
Hi,
while trying to build and test Sage Debian Live 7.3, i notice some issue
with meataxe package. While doctests pass on the VM is was built on
(Pentium3 kvm-emulated), the doctests give a lot of errors when the same
binary is run on another platform (it is t
On 2016-09-21 13:55, Frédéric Chapoton wrote:
This is because the patchbot called with "sage -patchbot" needs
currently to be launched from the branch of
https://trac.sagemath.org/ticket/20736
Well, *you* (or anybody else) could help by reviewing that ticket.
--
You received this message becau
Hello, this is a reminder that currently 3 blocker tickets need review.
All of them have some discussion, but they all seem stalled:
* Set JUPYTER_CONFIG_DIR
https://trac.sagemath.org/ticket/21430
* Old installed version of Cython is used
https://trac.sagemath.org/ticket/21441
* CoinBackend: _
On 2016-09-19 19:51, Thierry wrote:
you
should first remove SR(2.3) and 2*pi from your first list
That's a problem with the Symbolic Ring. Obviously, it doesn't coerce to
a real field (since it contains things like "sin(x)") but these
constants *should* coerce.
Anyway, I can always special-
On 2016-09-19 18:50, William Stein wrote:
That's only "dangerous" if you expect reset to do the same thing as
restart sage
I would guess that users *do* expect that.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group
On 2016-09-19 18:37, Travis Scrimshaw wrote:
The closest I can get is "foo in RR". This fails for CC(2.3, 0), but I
consider that to be a real number.
I would say it's a complex number which happens to have a real value.
But it is not a real number. It's the difference between *coercion* and
Hello,
is there a simple way to check in Sage that something is a real number
in some form? That is, I am looking for a predicate which returns True
on all the following things:
int(2)
ZZ(2)
float(2.3)
QQ(23/10)
RR(2.3)
RDF(2.3)
SR(2.3)
2*pi
but not on things like
"2.3"
CC(2.3, 0)
SR.symbol
On 2016-09-19 15:55, 'Martin R' via sage-devel wrote:
I use it all the time, mainly for "x", "n", and "pi":
But never reset() without arguments?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving e
The "interact" wiki page
https://wiki.sagemath.org/interact
is seriously broken: I guess it was meant to use the Sage cell server to
make the examples actually work but it doesn't do that anymore. What is
worse: also the source code is not shown, making the examples almost
totally useless...
Hello,
is there anybody who uses the functions reset() or restore() from
src/sage/misc/reset.pyx
They are meant to "reset" the global state in the interactive session to
what it was when Sage started up. This seems useless (why not just quit
Sage and restart it?) and dangerous (it resets glo
On 2016-09-19 11:06, YannLC wrote:
Should this be patched in Sage? patched upstream? left to the user?
Certainly in upstream PARI.
--
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,
After doing some Sage development, I ran doctests and 2 GAP tests
failed. The reason:
sage: from sage.libs.gap.assigned_names import *
Exiting Sage (CPU time 1m58.64s, Wall time 2m36.84s).
This is almost 2 minutes of CPU time (so it cannot be blamed on I/O) in
a Sage session just doing this. T
On 2016-09-16 02:05, Paul Masson wrote:
What exact steps did you take to build Sage?
Yes, we need more details. In case you upgraded from an older version of
Sage, this is probably an instance of #21441.
--
You received this message because you are subscribed to the Google Groups
"sage-deve
On 2016-09-15 23:21, Francois Bissey wrote:
lcalc: is no surprise. It uses a number of obsolete features, not sure
how long gcc itself will build it.
This is a bit off-topic, but for lcalc we should also at some
investigate whether we really need the package. It could very well be
that all fe
On 2016-09-14 13:34, Dima Pasechnik wrote:
One still would have to do something to provide fortran, though.
Exactly, so it's pointless to build Sage with clang since you won't be
able to compile any Fortran code. And I think that mixing compiler
suites (clang + gfortran) does not really work
On 2016-09-14 10:18, Vincent Delecroix wrote:
On 14/09/16 10:14, Jeroen Demeyer wrote:
On 2016-09-14 10:07, Vincent Delecroix wrote:
Apparently, there needs to be a libc with headers on the host to have
anything related to compilation working properly. Is that right?
Obviously yes. You
On 2016-09-14 10:07, Vincent Delecroix wrote:
Apparently, there needs to be a libc with headers on the host to have
anything related to compilation working properly. Is that right?
Obviously yes. You cannot compile C code without a working toolchain
(this includes a compiler, assembler, linker
On 2016-09-13 12:40, Stan wrote:
Would it be a possible workaround to just pip install entrypoints and
configparser?
Just entrypoints would be sufficient.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop r
On 2016-09-13 11:34, Stan wrote:
Actually, I am a bit confused here. For some reason|||jupyter| is not
found when I call it at the prompt, using Debian Jessy. Why is it found
when I call it from within a jupyter notebook using %%sh or os.system?
Because Jupyter is installed within Sage. You nee
On 2016-09-13 11:10, Stan wrote:
Every time I run either jupyter nbconvert or ipython nbconvert, I get
the following error message:
ImportError: No module named entrypoints
This might have been fixed by
https://trac.sagemath.org/ticket/21261
--
You received this message because you are subscr
I think it is far more important to do that on the release buildbot. The
patchbot is still an optional thing, which reviewers are free to ignore.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving em
Reported upstream at
https://github.com/ipython/ipython/issues/9944
https://github.com/jonathanslenders/python-prompt-toolkit/issues/392
--
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
On 2016-09-11 10:48, Johan S. H. Rosenkilde wrote:
Jeroen Demeyer writes:
https://ccache.samba.org/
And I forgot to mention that I have 2 complete Sage installation trees
so I can let one compile while I use the other.
Thanks, that's useful. Do you need any special setup or care for m
On 2016-09-11 08:43, Jeroen Demeyer wrote:
On 2016-09-10 18:36, Johan S. H. Rosenkilde wrote:
How do you guys cope with that?
https://en.wikipedia.org/wiki/Patience
https://ccache.samba.org/
And I forgot to mention that I have 2 complete Sage installation trees
so I can let one compile
On 2016-09-10 18:36, Johan S. H. Rosenkilde wrote:
How do you guys cope with that?
https://en.wikipedia.org/wiki/Patience
https://ccache.samba.org/
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receivi
On 2016-09-10 00:03, Paul Masson wrote:
Why would recythonizing be necessary when only changing the same file on
the same branch?
You are not changing just one file. When you checkout a new branch, a
lot of files get changed. When you checkout the old branch again, a lot
of files get changed
On 2016-09-09 23:34, Paul Masson wrote:
I'm a bit confused by your answer, because I've been seeing the same
sort of behavior. For the last week I've been rebuilding a branch based
on 7.4.beta2. With minor changes to one file, sage -b has been running
very quickly. Today I made one minor change a
On 2016-09-09 18:29, leif wrote:
See also https://trac.sagemath.org/ticket/21430 for a very recent,
related discussion.
No, it's not related at all.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receivi
On 2016-09-09 12:56, Marco Cognetta wrote:
It has happened to me where I build sage, turn off my computer, turn it
back on, and build it again. There were no changes made in the meantime
and it still does the cythonizing step.
Are you really sure that you remember this correctly? Turning off an
On 2016-09-09 10:20, Daniel Krenn wrote:
On #21204 (with 7.4.beta3) as well as on #21205 (with 7.4.beta4) patchbot
Gentoo Base System/2.2/x86_64/3.2.1-gentoo-r2/sage4
fails building with
[widgetsnbextension-1.2.6] OSError: [Errno 13] Permission denied:
'/home/worker/.jupyter'
This is h
On 2016-09-09 09:47, leif wrote:
Jeroen Demeyer wrote:
On 2016-09-09 08:23, Simon King wrote:
Is there a cleaner/less costly way to remove a file?
Obviously yes:
#include
remove(const char *pathname);
For files, unlink().
Depends on what kind of systems you want to support. remove() is
On 2016-09-09 08:23, Simon King wrote:
Is there a cleaner/less costly way to remove a file?
Obviously yes:
#include
remove(const char *pathname);
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receivin
On 2016-09-09 08:43, Marco Cognetta wrote:
However, if I change to a
new branch that has no changes which would necessitate recythonizing
code, it will go through the cythonizing step again.
What makes you think that there are no changes which would necessitate
recythonizing?
Cython does dep
On 2016-09-07 17:08, William Stein wrote:
like running top and parsing the output...
Yes, there was a big "WTF?" moment when I saw that :-)
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails
On 2016-09-07 15:09, leif wrote:
[x] Use it in other places as well
(related to multiprocessing, such as
doctesting, docbuilding, building the
Sage library -- in the long run)
It's not a multiprocessing package. It's more a replacement for typical
Unix
On 2016-09-07 14:48, Vincent Delecroix wrote:
Under the assumption that there is nothing more in memory_info.py than
in psutil
Well, psutil goes way beyond what memory_info.py provides. The only
logic that we would still need to keep from memory_info.py is these few
lines, which can easily be
Hello,
at https://trac.sagemath.org/ticket/21421 we propose to add the Python
package "psutil" as standard package for Sage. The tarball is 308KB,
installed it is about 624KB. The use case is replacing
src/sage/misc/memory_info.py
From https://pypi.python.org/pypi/psutil
psutil is a cross-p
General comment to all people complaining about Sphinx: reviewing
existing Sphinx-related tickets such as #20577 will show that you
actually care and will encourage other Sage developers to continue
working on Sphinx.
--
You received this message because you are subscribed to the Google Groups
On 2016-09-02 18:13, Nicolas M. Thiery wrote:
AdditiveGroups().AdditiveCommutative()
AdditiveGroups() does not exist.
--
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 emai
Should we move all categories in a catalog, e.g. rename
FiniteSemigroups
to
categories.FiniteSemigroups
Even if you think that categories belong in the top-level namespace, I
think it would still be useful to have a catalog such that
TAB-completion can give a list of all named categories in
On 2016-08-31 23:26, Vincent Delecroix wrote:
Hello,
In the optional package giacpy there are some extension classes that
depend on SageObject.
Does it really only need SageObject? I see no reason why giacpy would
need to do that. So the easiest solution seems to make giacpy *not*
depend on
On 2016-08-30 23:10, Dima Pasechnik wrote:
please post (or email me) headers in an example of your message.
Here is a worse example, a delay of 2 hours and 40 minutes:
Received: from o1.30nn.fshared.sendgrid.net
(o1.30nn.fshared.sendgrid.net [167.89.55.59])
(using TLSv1.2 with ciphe
On 2016-08-30 23:10, Dima Pasechnik wrote:
please post (or email me) headers in an example of your message.
Just an example of one notification with a small delay. Here you see a
delay of 6 minutes (note the different timezone, CEST==UTC+2).
[...]
Received: from o1.30nn.fshared.sendgrid.net
The patchbot tmonteil-debian-jessie-32 is spamming all tickets as
BuildFailed because of "No space left on device".
See for example
https://patchbot.sagemath.org/log/21126/debian/8.3/i686/3.16.0-4-586/tmonteil-debian-jessie-32/2016-08-31%2001:20:27?short
--
You received this message because y
On 2016-08-30 19:44, leif wrote:
Anyway, our current policy is that *only* the release manager is allowed
to close tickets, so I wouldn't do without first asking.
I have the "power" to close tickets, but I don't do that because of this
reason. The only exceptions are tickets which are obviousl
On 2016-08-30 17:28, Ralf Stephan wrote:
I propose to make it an error
to mix elements of rings with positive characteristics (or symbolic Mod)
and symbolic variables.
Is it easy to actually do that?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" gro
On 2016-08-28 18:59, Simon King wrote:
Is it possible to use "sage -t" on such docs?
I would guess that the doctesting is *not* affected by the formatting of
the surrounding documentation.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To un
On 2016-08-26 14:40, Thierry wrote:
So, what is the usecase for package typed 'pip' ?
It's only a convenient user interface: the user does not need to know
whether a package is available using pip or as Sage package: "./sage -i
PKGNAME" will work.
--
You received this message because you ar
pip packages are not real packages. If you really want to depend on a
"pip" package, the best way would be to convert it to a real package.
Also:
* standard packages should only depend on standard packages.
* optional packages should only depend on standard or optional packages.
* experimenta
On 2016-08-19 12:19, Jeroen Demeyer wrote:
Looking at how sage4 runs now, it looks like it is getting an outdated
ticket list somehow. First of all, it doesn't see any ticket numbers
above #21184.
Now the ticket list seems to be updated. I still don't know how the
patchbot gets
On 2016-08-19 12:34, Simon King wrote:
*unless* the user has somehow installed an old version manually
Or *unless* the build has not finished yet, which is my use case.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this gr
Looking at how sage4 runs now, it looks like it is getting an outdated
ticket list somehow. First of all, it doesn't see any ticket numbers
above #21184.
And it thinks that #12866 has positive_review, while in reality it is
closed:
[2016-08-19 10:16:06] #12866: start rating
rating 0 after a
On 2016-08-19 12:02, Thierry wrote:
Hi,
nginx is configured to use http2, which is the successor of spdy. I
removed it, is it better ?
Yes, it works now both from Firefox and Chromium. I don't know if the
problem was client-side or server-side but at least it works now.
Thanks,
Jeroen.
--
There seem to be some problems, possibly related to SSL. My firefox
browser just shows a blank page for https://patchbot.sagemath.org (not
even an error message)
Chromium gives an error page with
This site can’t be reached
The web page at https://patchbot.sagemath.org/ticket/21288/ might be
I created a ticket:
https://trac.sagemath.org/ticket/21288
--
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 sage-devel+unsubscr...@googlegroups.com.
To post to this
Hello,
What is the recommended way to check if the latest version of a given
Sage package is installed? The function is_package_installed() only
checks whether *some* version of the package is installed, which might
not be the latest version.
Jeroen.
--
You received this message because you
On 2016-08-19 08:37, Ralf Stephan wrote:
The sage4 patchbot spams BuildFailed because of
Fatal error: bliss/graph.hh: No such file or directory
[sagelib-7.4.beta1] #include "bliss/graph.hh"
It seems that bliss is not installed, but Sage thinks that it is
installed. I wonder what could cause
On 2016-08-19 04:16, James Khan wrote:
Hi!
Many thanks for your message and kind help.
I am running virtual machine on windows 7 and the sage 7.3 link is not
ready yet (the source code is there but not the sage-7.3.ova) so I am
stuck with 7.2 for the time being :(
I have indeed tried ./sage -i
On 2016-08-18 16:43, Simon King wrote:
What do you mean by Singular interface?
If I understand correctly, your package has an interface for GAP,
Singular and Sage and these are all independent from eachother. I am
asking that, if somebody has Singular installed but not GAP and not
Sage, that
On 2016-08-18 11:22, Simon King wrote:
What are you talking about? The current optional Sage package "meataxe"
is the latest upstream from Aachen.
I was under the impression that you needed special patches and that "the
latest upstream from Aachen" did not work for you. Anyway, it doesn't
mat
On 2016-08-18 00:02, Simon King wrote:
Slightly elaborating on my suggestion: Split the code from the old-style
p_group_cohomology-2.1.6.spkg into four parts, namely
1. an optional package "meataxe", which provides a C library and some
executables and which is *not* a Python package. It is us
On 2016-08-17 21:32, Simon King wrote:
It will provide a C library
I would *not* recommend putting C libraries in Python packages. First of
all, it doesn't really make sense (if it has nothing to do with Python,
it should not be a Python package). Second, the Python build system
cannot handl
On 2016-08-17 16:53, Simon King wrote:
So, does the cohomology spkg qualify as an "independent" Python module?
Perhaps it *could* be a independent Python module. One thing which is
not clear to me is to what extent your package would need changes to
Sage itself. If you need to make non-trivia
On 2016-08-16 22:28, Volker Braun wrote:
gdb on OSX should work, the only issue is that Apple decided that only
root shall have sufficient permissions to use it (PTRACE)
So in practice it doesn't work :-)
--
You received this message because you are subscribed to the Google Groups
"sage-devel
On 2016-08-16 14:04, Erik Bray wrote:
Hi all,
Is there a make target for building/installing all *optional* packages
as well as the standard ones?
First of all: not every optional package should be installed. There are
packages like gmp and python3 which should not mindlessly be installed.
On 2016-08-15 20:25, William Stein wrote:
It would be more standard to have an
explicit library import, which -- on import -- would print out
something about it being experimental and unstable.
Whether it's a separate library or part of Sage doesn't really matter
for this discussion. So I rea
On 2016-08-14 14:41, Frédéric Chapoton wrote:
As an intermediate step in our long way to python3, I would like to be
able to compile all the .pyx files in py3.
Except for #21246 (please review)
What about imports? Are all imports in Cython files converted to proper
absolute/relative imports w
On 2016-08-14 14:41, Frédéric Chapoton wrote:
Otherwise, one will have to get rid /by hand/ of all the `__cmp__`
methods everywhere, that will become obsolete in python3.
Don't confuse the cmp() function with __cmp__() methods! Getting rid of
cmp() and getting rid of __cmp__() are a priori dif
On 2016-08-12 16:41, Jeroen Demeyer wrote:
Could you give more details with the *exact* commands that you ran with
the *exact* output that those commands produced?
And also the output of "git status" at the point of failure.
--
You received this message because you are subscri
Your email is quite vague (for example, what is "version 16821")?
As long as you're not checking out a very old version of Sage, running
"make" should work except maybe in docbuilding. If docbuilding fails,
then "make doc-clean; make" should work.
Could you give more details with the *exact*
On 2016-08-12 11:24, leif wrote:
Yeah, the doctest framework should automatically base the tolerance on
such comparisons... ;-) :P
I don't know how serious you use, but you have to keep in mind that the
doctest framework works with strings. The main problem is that you would
need to guess the
601 - 700 of 3222 matches
Mail list logo
