Seth Morton

@argenisleon I realize it's been a couple of years since you filed these issues, and you may have found other solutions, but I have finally released them as part of...

> BTW, I would be amazing If we can vectorize fast_numbers. I would be more than happy to contribute. @argenisleon I realize so much time has passed you no longer...

I am going to close this because #45 *should* solve this problem - the return mechanism is cleaner so any problem where `NULL` can be returned erroneously should be caught...

I am going to close this because https://github.com/SethMMorton/fastnumbers/issues/45 *should* solve this problem - the return mechanism is cleaner so any problem where NULL can be returned erroneously should be caught...

In the next `natsort` release, the handling of `None` and NaN will be done automatically under-the-hood to always be consistently sorted. For the numbers case, this can be solved by...

If the fix is supposed to auto detect that a repository changed their default branch on GitHub from "master" to "main" and then provide "main" as a dropdown option instead...

Huh, that is strange. It used to work - I imagine something has changed with how GitHub is serving these pages. I'll see what I can do.

Fixed - I split it into two and kept the old page name as a landing page.

You can already enable this functionality by creating a simple key out of regular expressions. ```python In [1]: import re In [2]: data = ['a-category-1', 'a0-item-1', 'a1-item-2', 'b-category-2', 'b0-item-1', 'b1-item-2']...

I'm not sure I follow - can you please demonstrate how it is more flexible? Also, your suggestion would require a complete re-write of `natsort`, so I think I will...