# Is it possible to cut a new release of numba?

**URL:** <https://numba.discourse.group/t/is-it-possible-to-cut-a-new-release-of-numba/1331>\
**Category:** Community Support\
**Created:** [May 13, 2022, 10:17pm UTC](https://numba.discourse.group/t/is-it-possible-to-cut-a-new-release-of-numba/1331 "2022-05-13T22:17:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ggydush-fn](https://yyz2.discourse-cdn.com/free1/user_avatar/numba.discourse.group/ggydush-fn/32/590_2.png) [@ggydush-fn](https://numba.discourse.group/u/ggydush-fn)\
**Post date:** [May 13, 2022, 10:17pm UTC](https://numba.discourse.group/t/is-it-possible-to-cut-a-new-release-of-numba/1331/1 "2022-05-13T22:17:50Z")

</div>

It looks like since 0.55.1, numba removed the upper bound bin on numpy (previously was 1.22). I was wondering if it would be possible to cut a new release with those changes so that I am able to use numba with a later version of numpy!

Thank you!  
-Greg

---

<div class="post-metadata">

**Author:** ![nelson2005](https://yyz2.discourse-cdn.com/free1/user_avatar/numba.discourse.group/nelson2005/32/47_2.png) [@nelson2005](https://numba.discourse.group/u/nelson2005)\
**Post date:** [May 14, 2022, 4:29pm UTC](https://numba.discourse.group/t/is-it-possible-to-cut-a-new-release-of-numba/1331/2 "2022-05-14T16:29:37Z")

</div>

Link to [milestone](https://github.com/numba/numba/milestone/61)

---

<div class="post-metadata">

**Author:** ![sircambridge](https://yyz2.discourse-cdn.com/free1/user_avatar/numba.discourse.group/sircambridge/32/591_2.png) [@sircambridge](https://numba.discourse.group/u/sircambridge)\
**Post date:** [May 15, 2022, 12:40pm UTC](https://numba.discourse.group/t/is-it-possible-to-cut-a-new-release-of-numba/1331/3 "2022-05-15T12:40:03Z")

</div>

I have the same problem. today I did a fresh install of python, and I got numpy ‘1.22.3’ and when I install numpy 0.55.1, I get “ImportError: Numba needs NumPy 1.21 or less”

is there a temporary workaround for this?

for now I just commented out L140: raise ImportError(“Numba needs NumPy 1.21 or less”) in site-packages/numba/ **init**.py

---

<div class="post-metadata">

**Author:** ![esc](https://yyz2.discourse-cdn.com/free1/user_avatar/numba.discourse.group/esc/32/49_2.png) [@esc](https://numba.discourse.group/u/esc)\
**Post date:** [May 16, 2022, 4:09pm UTC](https://numba.discourse.group/t/is-it-possible-to-cut-a-new-release-of-numba/1331/4 "2022-05-16T16:09:36Z")

</div>

Thank you for asking about this. We are currently working on NumPy 1.22 support here:

> <https://github.com/numba/numba/pull/8027>
>
> As title.
> 
> Fixes #7756
> Fixes #7757
> Fixes #7759
> Fixes #7760
> Fixes #7758
> 
> …Closes #7754
> 
> \<!--
> 
> Thanks for wanting to contribute to Numba :)
> 
> First, if you need some help or want to chat to the core developers, please
> visit https://gitter.im/numba/numba for real time chat or post to the Numba
> forum https://numba.discourse.group/.
> 
> Here's some guidelines to help the review process go smoothly.
> 
> 0. Please write a description in this text box of the changes that are being
> made.
> 
> 1. Please ensure that you have written units tests for the changes made/features
> added.
> 
> 2. If you are closing an issue please use one of the automatic closing words as
> noted here: https://help.github.com/articles/closing-issues-using-keywords/
> 
> 3. If your pull request is not ready for review but you want to make use of the
> continuous integration testing facilities here, please click the arrow besides
> "Create Pull Request" and choose "Create Draft Pull Request".
> When it's ready for review, you can click the button "ready to review" near
> the end of the pull request
> (besides "This pull request is still a work in progress".)
> The maintainers will then be automatically notified to review it.
> 
> 4. Once review has taken place please do not add features or make changes out of
> the scope of those requested by the reviewer (doing this just add delays as
> already reviewed code ends up having to be re-reviewed/it is hard to tell
> what is new etc!). Further, please do not rebase your branch on main/force
> push/rewrite history, doing any of these causes the context of any comments
> made by reviewers to be lost. If conflicts occur against main they should
> be resolved by merging main into the branch used for making the pull
> request.
> 
> Many thanks in advance for your cooperation!
> 
> \--\>

We are currently (today) still missing the 1.22 packages on `defaults` which would allow us to cut a clean build.

We are planning to release a 0.55.2 soon (next few days, maybe weeks) which will contain only the 1.22 patches – this should hopefully be compatible.

As for the NumPy version pin, for Numba, when we release, we pin the latest known working and tested version of NumPy on the release branch. So, the `main` branch doesn’t have any NumPy maximum, which enables smoother testing of new releases, but the released versions always will. We do this defensively because all the recent NumPy releases were incompatible with Numba for some reason and required additional patches to work.

Hope this helps!