Hi,
it's been over a year since the last activity on
https://github.com/sagemath/cysignals.
This could well be, because it is a good shape, but looking at the issues,
I'm not too sure about that. Here are some issues, I know of:
- sig_on/sig_off is poorly maintained and not thread safe
- cysig
Sure. Since this is written in cython, using
https://cython.readthedocs.io/en/latest/src/userguide/parallelism.html
might be a good choice.
This is also used in
`src/sage/geometry/polyhedron/combinatorial_polyhedron/face_iterator.pyx`.
Note the first two lines of the file. With those lines, yo
Hi Frédéric,
due to https://trac.sagemath.org/ticket/33027 I have given up on running my
patchbot.
Jonathan
Frédéric Chapoton schrieb am Montag, 17. Januar 2022 um 21:31:31 UTC+1:
> and to fix the remaining doc-cleaning issue, please upgrade again to the
> master branch of github (aka tag 3.0
Sorry for being late to the party.
To save Volker the headache, I would propose setting the environment
variable SAGE_DOCTEST_RANDOM_SEED to zero for buildbots (see
https://trac.sagemath.org/ticket/32761).
It's not the job of buildbots to discover random test failures (patchbots
on the other ha
Dear Vincent,
this has been resolved in https://trac.sagemath.org/ticket/33026 (positive
review, but not closed).
Jonathan
vdelecroix schrieb am Mittwoch, 5. Januar 2022 um 09:04:13 UTC+1:
> Dear all,
>
> In the following patchbot report
>
>
> https://patchbot.sagemath.org/log/32553/Linux/1_SM
Hi there,
I run a patchbot (panke), which completely slowed down because of maxima
threads that ate away my memory. There were like 10 of them. Is this a bug?
Killing those threads the patchbot keeps on running just fine. So
apparently, they were really lost.
Jonathan
--
You received this me
FF = GF(next_prime(100))
M = Matrix(FF, [[1, 2], [3, 4]])
M.__init__??
reveals that the indices are casted into a long. This might be the problem.
Using Py_ssize_t or size_t might have been a better choice.
Jonathan
dim...@gmail.com schrieb am Mittwoch, 1. Dezember 2021 um 20:56:16 UTC+1:
>
Thanks for the report. For cysignals we have the ticket
https://trac.sagemath.org/ticket/32576 and github issue
https://github.com/sagemath/cysignals/issues/150.
furutaka@gmail.com schrieb am Montag, 22. November 2021 um 04:17:55
UTC+1:
> Forgot to attach this...
>
> 2021年11月22日(月) 11:31 K
See https://trac.sagemath.org/ticket/32211 for package upgrade.
Bill Hart schrieb am Mittwoch, 17. November 2021 um 19:44:30 UTC+1:
> Hi all,
>
> I just tagged Flint-2.8.4. This is a critical bug fix release and so
> we strongly recommend upgrading.
>
> * Fix a serious bug in fmpz_mod_poly_xgcd fo
I have have found a fix elsewhere and copy/pasted it in
https://github.com/sagemath/cysignals/pull/151, this might already solve
the issue.
Fixes this and possibly upgrading cysignals is now
https://trac.sagemath.org/ticket/32576.
Manuel González schrieb am Samstag, 25. September 2021 um 23:52:
Sorry for the wrong reference, I guess the following reference is better:
https://lists.gnu.org/archive/html/info-gnu/2021-08/msg1.html
Maybe compiling cysignals without march native is also and option until
this problem is resolved for cysignals.
jonatha...@googlemail.com schrieb am Samstag
https://github.com/openbsd/src/commit/ea0d1f1fdbdc98dc215aafd8869e67812566a636#diff-abef93fb3c734d17f027b68052e70aac7e9949432392fb4910c1578ca087534a
MINSIGSTKSZ is no longer a constant, which causes this problem.
Does it compile, when you add `--std=c11` to your `CFLAGS`.
E.g. do `sage -sh` and
Thanks for the answers.
I didn't realize this whole issue was this involved. It's certainly
interesting.
For now I think there is nothing wrong with registering
`NumberFieldElement` as `numbers.Numbers`, see
https://trac.sagemath.org/ticket/32206.
Jonathan
mathzeta2 schrieb am Donnerstag, 1
Hi, I was looking into typing a bit and realized that our number field
elements are not registered as numbers. So the following will not evaluate
to true:
sage: import numbers
sage: K. = QuadraticField(2)
sage: isinstance(a, numbers.Number)
Is there a reason, we do not register number fields in
Dear all,
most of sage's doctest are independent of random seeds by now. It would be
nice if you could not add new doctests that depend on the random seed of
the doctester.
Usually one needs to be carefull when adding doctests with `random_element`
and `some_elements`. If you not sure on how t
resolution: Get conda running (if not already
installed). There is plenty of help out there for this. Once you got conda
running, we can help you.
dim...@gmail.com schrieb am Freitag, 25. Juni 2021 um 08:29:51 UTC+2:
> On Fri, 25 Jun 2021 at 07:12, 'jonatha...@googlemail.com&#
I did a large computation on a redhat application server 1 1/2 years ago
and I was very happy that I could just compile gcc to replace the version
4.x. There where a couple of problems though, but all of them could be
resolved. I can't reproduce this however, as those people have thankfully
pro
Are there objections of adding this new standard package, which consists of
the code from `ext/memory_allocator.*`?
This is now https://trac.sagemath.org/ticket/31591.
I would like to put it on `github.com/sagemath` but need either help or
permissions to do so.
The new package does not depend
> read that bug in detail.
>
> Thanks for the feedback.
>
> Best
> Freddie
> On Wednesday, May 5, 2021 at 1:01:39 AM UTC-7 dim...@gmail.com wrote:
>
>> we've fixed a memory leak in matrices recently (this fix will be in
>> 9.3), not sure if this is
It looks to me as if all of this ticket can be "fixed" to work with python
3.7 by just trying to import shared_memory.
`start_worker_pool` should probably raise a proper error message, if the
import of shared_memory failed previosly.
The few doctests that explicitly call `start_worker_pool` can
Dear Freddie,
thank you for the report.
Fortunatly or unfortunately, I can't reproduce this on sage 9.2 or on the
develop branch (on ubuntu focal with libflint-2.5.2 and debian buster with
sage's flint 2.6.3).
This might be a bug with flint. What flint are you using?
You can go into detail, t
+1
In addition to the above arguments, there are two other advantages (but
which do not justify deactivating jedi tab completion for sage-9.3):
- It's noticably faster without jedi.
- Keywords of functions appear first in the list, where they belong and not
somewhere hidden. (Deactivating jedi
https://github.com/kliem/memory_allocator
I started MemoryAllocator as a seperate project. I think it is almost ready
to push to PyPI. Any opinions? Do I need permission to publish it like
this? Should this be moved into a different repository? (E.g.
https://github.com/sagemath/memory_allocator
:
> On 19.03.21 11:13, François Bissey wrote:
>
> >
> >> On 19/03/2021, at 23:05, 'jonatha...@googlemail.com' via sage-devel <
> sage-...@googlegroups.com> wrote:
> >>
> >> We configure libaries with e.g. `--with-zlib="$SAGE_LOCAL"
Hi, I think I made a mistake in https://trac.sagemath.org/ticket/31482,
which might cause latte_int to fail building, if you use your systems cdd
(which almost no one does, because the headers in cdd/ and cddlib/ are
rejected currently).
However, it appears that we make this mistake all over s
This approach might not be pretty, but it seems to work fine.
I can use cysignals on cygwin, linux, mac and not use it on windows without
cygwin.
However, it would be much nicer to allow pip installing cysignals on
windows without cygwin in the first place. This would simplify this a lot.
jona
Dear all, I have two little projects that I want to put onto PyPI soon.
Both of them use MemoryAllocator, because I find it very nice to just
allocate memory and let pythons garbage collector take care of it.
MemoryAllocator only depends on cysignals, so it would make sense to make
it pip insta
> On Tuesday, February 9, 2021 at 6:52:51 AM UTC-8 Dima Pasechnik wrote:
>>>
>>>> it looks like https://github.com/davidhalter/jedi/issues/1615
>>>> and our version of jedi is older than the fix there.
>>>> Upgrade jedi (if this is possible
ython/jupyter
>>> upgrade, don't know) ?
>>>
>>> On Tue, Feb 9, 2021 at 1:56 PM 'jonatha...@googlemail.com' via
>>> sage-devel wrote:
>>> >
>>> >
>>> > Dear all,
>>> >
>>> > sage c
jedi (if this is possible without a full ipython/jupyter
>> upgrade, don't know) ?
>>
>> On Tue, Feb 9, 2021 at 1:56 PM 'jonatha...@googlemail.com' via
>> sage-devel wrote:
>> >
>> >
>> > Dear all,
>> >
>> > sage cr
Dear all,
sage crashes once in a while hard with some strange error.
Does anyone know what is going on? This is somewhat new. Not reproducible.
Happened to me maybe 3 or 4 times now at various occasions.
Jonathan
--
You received this message because you are subscribed to the Google Groups
"
For `sage -b` not working see https://trac.sagemath.org/ticket/31263 (on
positive review).
Sorry about that (I positively review the ticket that broke it).
dwb...@gmail.com schrieb am Samstag, 23. Januar 2021 um 14:28:00 UTC+1:
> I cannot build the documentation. It actually crashes python. I'm
Hi, could someone please review https://trac.sagemath.org/ticket/31036
I appreciate `sage --fixdoctests` and it made my life easier in the past.
However, it does not work for multiline tests or testing error raising.
This ticket is an attempt to fix this. And it's not a big ticket:
1 files chan
You need to login somehow.
You have previously logged in with your github account `gh-bollu`. This
works as well. After you log in, the edit options will appear.
Of course you can also create a sage account, which also lets you edit
https://wiki.sagemath.org/ and maybe you prefer not to link yo
I tried to compile more things with C++ and things just got worse. But
maybe I did it wrong, that is also possible.
Anyway, using sets as an alternative wasn't really sucessfull. It is a bit
slower. Turns out the data structure is pretty good.
David Coudert schrieb am Dienstag, 12. Januar 2021
Super weird. I think it is a cython bug, but I'm not sure.
The problem seems to be that the parent class has the same method. I need
to enforce the correct method
by
self.foo(u) -> SparseGraph.foo(self, u)
This seems to work (compiles and the doctests pass).
jonatha...@googlemail.com schrieb a
Prepending
# distutils: language = c++
to src/sage/graphs/base/sparse_graph.pyx makes my compilation crash.
Does anyone know, how to fix it. I'm on develop and I'm getting the
following compilation error. Does anyone know how to resolve this? Thank
you.
Jonathan
(I want to see whether cpp set
13, 2020 at 11:55 AM 'jonatha...@googlemail.com' via
> sage-devel wrote:
> >
> > Thank you François.
> >
> > I was doubtful that your answer would help, but it did finally after
> some googling.
> >
> > I had to run
> >
> >
pen_Args_l+0x22b)[0x7fa87edda23b]
> /srv/public/shared/DGI-sage/local/lib/python3.8/site-packages/matplotlib/
> ft2font.cpython-38-x86_64-linux-gnu.so(+0xd35f)[0x7fa87eddc35f]
>
>
> I’d say it is trying to open a font file to which it has no right.
>
> François
>
> >
>
> [10 0 0 0 1]
> [-1 1 0 0 0]
> [-1 0 1 0 0]
> [-1 0 0 1 0]
>
> David
>
> On Wed, Nov 11, 2020 at 7:19 AM 'jonatha...@googlemail.com' via
> sage-devel wrote:
>
>>
>> Given rational v
Given rational vectors and consider their linear span.
How do I obtain a basis of the ZZ^d-submodule (a basis for the contained
lattice points).
E.g. given
[
(1, 0, 0, 0, 1/10),
(0, 1, 0, 0, 1/10),
(0, 0, 1, 0, 1/10),
(0, 0, 0, 1, 1/10)
]
How do I obtain this or something equivalent:
[[1, 0,
trap-clean
> ./bootstrap
> ./configure
> make
>
>
>
>
>
>
> On Mon, Oct 26, 2020 at 9:16 AM 'jonatha...@googlemail.com' via
> sage-devel wrote:
>
>> I freshly updated to ubuntu focal and wanted to remake sage and failed.
>> See attached log.
>&
I freshly updated to ubuntu focal and wanted to remake sage and failed. See
attached log.
I ran `make dist-clean` and `make clean` and `./configure` various times
and I have no clue why it tries to uninstall gmpy and why it fails.
The claim is that it could not find python, but I'm using system
We are not able to create a branch on
https://trac.sagemath.org/ticket/30402:
$ git push --set-upstream trac public/30402 perl: warning: Setting locale
failed. perl: warning: Please check that your locale settings: LANGUAGE =
(unset), LC_ALL = (unset), LC_PAPER = "de_DE.UTF-8", LC_ADDRESS =
"d
Thanks. I still can only guess, if people care about large bitsets like
this.
I can try to make it available with the same syntax and then however likes
it, can just use it.
Sébastien Labbé schrieb am Dienstag, 22. September 2020 um 16:07:15 UTC+2:
> Am I the only one using larger bitsets?
>>
emtation
>>>> > detail. With this ticket I can pretty much tell the face-structure
>>>> that it
>>>> > consists of a roaring bitmap of atoms and coatoms and adapt a few
>>>> basic
>>>> > functions to the name scheme of that (I also need
;> About 2: the C library CRoaring seems a good match but does not
>>> seem to contain any assembler or advanced CPU instructions. Does it?
>>> It is hard to figure out how well is implemented and maintained the
>>> Python interface PyRoaringBitMap.
>>>
>>&g
ng seems a good match but does not
>> seem to contain any assembler or advanced CPU instructions. Does it?
>> It is hard to figure out how well is implemented and maintained the
>> Python interface PyRoaringBitMap.
>>
>> Le 16/09/2020 à 17:18, 'jonatha...@goo
maintained the
> Python interface PyRoaringBitMap.
>
> Le 16/09/2020 à 17:18, 'jonatha...@googlemail.com' via sage-devel a
> écrit :
> > Dear Vincent, thanks for your reply.
> >
> > To sum up my reply: Should I try to replace bitsets completely by
>
e bitsets. Sparse
> could be implemented as sets via has tables or binary trees,
> etc
>
> [1]
>
> https://cython.readthedocs.io/en/latest/src/userguide/language_basics.html?highlight=pxi#cython-file-types
>
> Le 16/09/2020 à 11:59, 'jonatha...@googlemail.com' v
Dear all, I want to redesign the bitset structure of combinatorial
polyhedron and move it to `data_structures/bitset.pxi`. This includes some
changes to bitset.pxi. Please comment, whether the proposed design changes
on the ticket are ok. Mostly they are the following:
1. Define most of the fun
51 matches
Mail list logo
