[Numpy-discussion] Re: spam on the mailing lists

[matti . picus]

Upate: since there is a clear delineation of spammers vs legitimate posts, I 
would like to tweak the policy [0] and from now on a single spam message will 
move email addresses down a category: from authorized to moderated and from 
moderated to unsubscribed. I have changed the policy statement accordingly, 
pending disagreement here. It makes the bookkeeping simpler since we don't have 
to track spam messages (we get on average 1 or 2 a day)

Matti 

[0] https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com

[Numpy-discussion] Tensor typing meeting (15 Nov) slides & video

[Stefan van der Walt]

I thought this might be of interest to Bas and others.

- Original message -
From: Matthew Rahtz via Typing-sig
Date: Tuesday, November 16, 2021 02:31

Thanks to everyone for coming! Recording is here 
,
 and the slides are at Dealing with DTypes 
.
 Details of this and previous tensor typing meetings are available here 
.

Our next tensor typing meeting will tentatively be on *Monday the 13th of 
December*. See you then!

A quick summary of the talk is below.
 * How should we handle data type promotion in stubs?
 * Option 1: One overload for each possible combination of dtypes
 * Option 2: One overload for each result dtype
 * Option 3: Don't handle type promotion
 * Option 4: Use a dtype class hierarchy and exploit Union type operator 
behaviour
 * Option 5: Propose a type promotion operator
 * Option 6: Propose a 'nearest common parent' operator
 * Option 7: Propose a type lookup table operator
 * Consensus during discussion was that since it looks like a new type operator 
*would* be required, we should probably hold off on dealing with this until the 
community shows a strong desire for this feature, and in the meantime just not 
handle data type promotion in stubs.

___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com

[Numpy-discussion] Re: installing numpy on OpenIndiana

[Matti Picus]

  
  
Your mail ended up in my spam bucket, maybe that is why no-one
  responded.



On 11/11/21 8:58 pm, asyropou...@aol.com wrote:


  ld: fatal: file _configtest.o: wrong ELF class: ELFCLASS64


There is something seriously off with the way the compiler is
  being called. 



We don't support OpenIndiana. Are there python user groups you
  could reach out to?



This is the first error you need to solve. The usual way to build
  numpy from source is via `pip install`, not using the github
  tarballs. This should solve the versioneer problem. There are
  various options to `pip install` that will allow you more
  flexibility when trying to recover from a broken build. I do see
  you have `-m64` in the gcc command line, is that normal for
  building on this platform?


Matti

  

___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com

[Numpy-discussion] NumPy 1.22.x has been branched

[Charles R Harris]

Hi All,

Just as the subject line says.

Chuck
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com