-
Notifications
You must be signed in to change notification settings - Fork 2.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
Make a 2.2 release #953
Comments
Yeah, seems like a good time for a new release. There's a good number of bug fixes and some nice new features. I'd suggest postponing #934 for the next release, so it gets some time in master just in case there are any backward compatibility concerns. Also, it's related to #864 so if we find any need to adjust the casters it would be good to keep everything in one release and change things only once. For the rest of the PRs, I very much agree with your assessment. |
Would be great if #960 could make it into a 2.2 release. |
(From the peanut gallery): initial experience with pybind11 has been good other than brief documentation. Could really use #805 as soon as available. |
Updates:
So, my thinking is: postpone the first one, finish the other 4 and call it a release. Would that work or is there anything else? |
I'm not so happy with #901 yet, so dropping that for now sounds good to me. +1 for the rest. |
Sounds good to me. |
All of the PRs discussed above have been merged. I've gone over the changelog one more time, fixed some typos, noted some of the last-minute additions and added a short entry for the upgrade guide: 4c54044 If there's nothing else, I think this might be good to go. |
I'm ready to push the button. @jagerman, anything left from your end? |
Nope, I think we're good to go! |
Ok, done! -- the PyPi package is pushed, and the one on conda forge will be shortly. |
We have a decent amount of new features and bug fixes for a new stable v2.2 release. Some big features (embedding support seems the biggest), lots of minor ones, and various bug fixes have landed into
master
over the last four months. I'm not suggesting we release it tomorrow, but I think we should start thinking about where to draw the line for 2.2.PRs I think we should aim to merge:
pybind11.h
or not), and then I'll update the documentation accordingly before merging.py::local
support for keeping a type's registration local to the module). This was a sort of experiment to think about fixing Eventual collisions between opaque STL containers #919, but I think it worked out into a nice feature -- and I was actually surprised just how little code it actually needed to implement. This still needs me to write up the documentation, but I'll do that in the next couple of days.Extended options object to choose between the print of __repr__ and __str__ (edited title) #901 (cutting off the maximum length in generated signatures) is a nice cosmetic feature. It needs some more tweaking, but if that happens it seems worth including.--> for v2.3Constexpr type signatures for C++11 and semi-constexpr for MSVC #934 (constexpr type signatures for C++11 and MSVC). Currently has a minor merge conflict, but aside from that I think it's ready to merge.--> for v2.3Other features in the queue that I think might not make it:
enum_<>
due to backwards-compatibility issues with howenum_
worked; beyond that I'm not entirely sure of the status.Thoughts?
The text was updated successfully, but these errors were encountered: