-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update for 0.45.0RC1 release changelog #4297
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR. This is a pretty much there but it seems like a few things were missed, noted in comments. Thanks.
Joshua Adelman added support for ``x in range(...)`` in #4129. | ||
|
||
|
||
General Enhancements: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to be missing a bunch of PRs...
$ git log 0.45.0dev0..HEAD|grep -i "Merge pull"|egrep -i "#[0-9][0-9]+"|wc -l
shows 60, I manually cross referenced these against those on the milestone (which was not complete in itself, but is now).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
my script stopped prematurely. the list of PR has been fixed now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't see these anywhere:
- Use callable instead of checking __module__ #4145
- typed-list #4151
- Make Parfors cacheable #4155
- Developer docs for caching #4211
?
Also, I just noticed that this proposed change log update is stylistically inconsistent with the records since 0.35.0, from then on the PRs are ordered from lowest ticket number to highest, this one does highest to lowest.
|
||
Joshua Adelman added support for ``x in range(...)`` in #4129. | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i've updated the contributors
CHANGE_LOG
Outdated
Version 0.45.0 | ||
-------------- | ||
|
||
In this release, Numba gained an experimental `numba.typed.List <pending_link>`_ container as a future replacement of the `reflected list <pending_link>`_. In addition, functions decorated with ``parallel=True`` can now be cached to reduce compilation overhead due to the auto-parallelization the function. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this release, Numba gained an experimental `numba.typed.List <pending_link>`_ container as a future replacement of the `reflected list <pending_link>`_. In addition, functions decorated with ``parallel=True`` can now be cached to reduce compilation overhead due to the auto-parallelization the function. | |
In this release Numba gained an experimental `numba.typed.List <pending_link>`_ container as a future replacement of the `reflected list <pending_link>`_. In addition, functions decorated with ``parallel=True`` can now be cached to reduce compilation overhead associated with the auto-parallelization the function. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The comma is not needed after "release"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Up to you, I'm not sure it needs it, but it's the most minor of details :) either way is fine. Was more concerned with the due to
at the end of the line.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed due to
, kept comma.
as titled.