On Thu, May 13, 2021 at 4:52 PM David Roe wrote:
>
>
>
> On Thu, May 13, 2021 at 6:09 AM Dima Pasechnik wrote:
>>
>> On Thu, May 13, 2021 at 1:34 AM 'Travis Scrimshaw' via sage-devel
>> wrote:
>> >
>> > Own tag might be a goood way forward as the code itself can run on Python
>> > 3.7 by avoidi
On Thu, May 13, 2021 at 6:09 AM Dima Pasechnik wrote:
> On Thu, May 13, 2021 at 1:34 AM 'Travis Scrimshaw' via sage-devel
> wrote:
> >
> > Own tag might be a goood way forward as the code itself can run on
> Python 3.7 by avoiding the multiprocessing. It would be purely to state
> that we don't
On Thu, May 13, 2021 at 1:34 AM 'Travis Scrimshaw' via sage-devel
wrote:
>
> Own tag might be a goood way forward as the code itself can run on Python 3.7
> by avoiding the multiprocessing. It would be purely to state that we don't
> want to test the mp parts of the code. How do I make an option
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
