On Thu, Jan 6, 2022 at 4:43 PM wrote:
> Thanks for your answer.
>
> I think i understand it - is it that `f64_info.max - f64_info.min` does
> not fit in float64? because it approximates `2 * f64_info.max`?
>
Well, it "fits" into a float64 by becoming `inf`, which is a valid float64
value, just o
I'm not sure I know what that is? do you have a reference I can follow?
___
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-discuss
Thanks for your answer.
I think i understand it - is it that `f64_info.max - f64_info.min` does not fit
in float64? because it approximates `2 * f64_info.max`?
In that case, I agree with Klaus, linspace should be able to handle this?
___
NumPy-Discussi
Hi, Danuta!
This sounds great! I’m excited to team up with you once again!
Every good wish,
Inessa
Inessa Pawson
Contributor Experience Lead | NumPy
ine...@albuscode.org
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe sen
That's great, thanks! Hopefully I'll get time to sort that out soon.
Peter
On Thu, Jan 6, 2022 at 3:23 PM Matti Picus wrote:
>
> On 6/1/22 2:15 pm, Peter Cock wrote:
>
> > Hello Matti, Charles,
> >
> > ...
> >
> > Do you have any advice on how to request TravisCI credits (I'd be happy to
> > dis
On 6/1/22 2:15 pm, Peter Cock wrote:
Hello Matti, Charles,
...
Do you have any advice on how to request TravisCI credits (I'd be happy to
discuss off list), or would you advise us to focus on the migration now (which
pushes back any release plans).
Thank you,
Peter
Here is what travis-ci wr
Hello Matti, Charles,
I'm a minor numpy contributor but mostly follow the mailing list with an eye
on any impacts downstream for Biopython. Like numpy and scipy etc, we
had been using TravisCI to build our wheels:
https://github.com/biopython/biopython-wheels
Lots of other projects using multibu
