[sage-devel] Please test

2021-03-29 Thread Kwankyu Lee
Hi all, The patch in the ticket https://trac.sagemath.org/ticket/31536 aims to solve a few problems in displaying sage objects in jupyter environment. As we are fear of any regressions, please test the patch with your favorite sage objects. Thank you. -- You received this message because

Re: [sage-devel] Re: Move MemoryAllocator to PyPI?

2021-03-29 Thread 'Jonathan Kliem' via sage-devel
On 29.03.21 21:53, Matthias Koeppe wrote: On Monday, March 29, 2021 at 12:08:36 PM UTC-7 jonatha...@googlemail.com wrote: I think in case of a pxd files things are a bit different. If someone uses cysignals and memory_allocator in the same place, e.g. cdef MemoryAllocator mem =

Re: [sage-devel] Re: Move MemoryAllocator to PyPI?

2021-03-29 Thread Matthias Koeppe
On Monday, March 29, 2021 at 12:08:36 PM UTC-7 jonatha...@googlemail.com wrote: > I think in case of a pxd files things are a bit different. If someone uses > cysignals and memory_allocator in the same place, e.g. > > cdef MemoryAllocator mem = MemoryAllocator() > sig_on() > foo =

Re: [sage-devel] Re: Move MemoryAllocator to PyPI?

2021-03-29 Thread 'Jonathan Kliem' via sage-devel
I propose removing the sig_block / sig_unblock from MemoryAllocator alltogether. I think it is really bad practice to put an extension class method into sig_on / sig_off and this would be the only use case that this is good for anyway (I doubt that this is safe in the first place --

Re: [sage-devel] Re: Move MemoryAllocator to PyPI?

2021-03-29 Thread Matthias Koeppe
On Monday, March 29, 2021 at 9:21:05 AM UTC-7 jonatha...@googlemail.com wrote: > On Mar 29, 2021 5:26 PM, Matthias Koeppe wrote: > > This suggestion is not compatible with modern Python packaging > (PEP-517/518). There is no such thing as an "optional build dependency". > > Is it acceptable

Re: [sage-devel] Re: Move MemoryAllocator to PyPI?

2021-03-29 Thread 'Jonathan Kliem' via sage-devel
On Mar 29, 2021 5:26 PM, Matthias Koeppe wrote: > > On Monday, March 29, 2021 at 6:25:28 AM UTC-7 vdelecroix wrote: >> >> I think it is desirable to have the possibility to enable or disable >> cysignals manually. In other words >> enable + "no cysignals present" -> error >> enable +

Re: [sage-devel] Re: Move MemoryAllocator to PyPI?

2021-03-29 Thread Matthias Koeppe
On Monday, March 29, 2021 at 6:25:28 AM UTC-7 vdelecroix wrote: > I think it is desirable to have the possibility to enable or disable > cysignals manually. In other words > enable + "no cysignals present" -> error > enable + "cysignals present" -> compilation with sigs > disable + "whatever"

Re: [sage-devel] Re: Move MemoryAllocator to PyPI?

2021-03-29 Thread 'Jonathan Kliem' via sage-devel
On Mar 29, 2021 3:23 PM, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > > +1 for having it inside https://github.com/sagemath > > I think it is desirable to have the possibility to enable or disable > cysignals manually. In other words >    enable + "no cysignals present" -> error >  

Re: [sage-devel] Re: Move MemoryAllocator to PyPI?

2021-03-29 Thread Vincent Delecroix
+1 for having it inside https://github.com/sagemath I think it is desirable to have the possibility to enable or disable cysignals manually. In other words enable + "no cysignals present" -> error enable + "cysignals present" -> compilation with sigs disable + "whatever" -> compilation

Re: [sage-devel] Re: Move MemoryAllocator to PyPI?

2021-03-29 Thread 'jonatha...@googlemail.com' via sage-devel
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.