-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Wrong msvc version #773
Wrong msvc version #773
Conversation
Do you have easy access to a machine with stock 2015u3 installed? If so, can you confirm that the full test suite builds and runs successfully in 190024210? (In other words, do we depend on anything fixed between u3 and u3+CSR?) AppVeyor checks obviously can't tell that, since AppVeyor runs with the update installed. |
@wjakob - thoughts re: 2.1.1 release for this? |
@wjakob would you guys consider making a release with that fix? The current version number check prevent the compilation of pybind11 for a lot of people on windows even with MSVC update 3. |
@SylvainCorlay: ok, done -- feel free to merge the feedstock PR once the CI tests have passed. |
The issue is that this comes after the backward incompatible removal of |
@wjakob Actually creating a 2.x branch in which you backport bug fixes sounds reasonable,. So that you can make bug-fix releases for 2.x, while working on 3.0 in the master branch. |
@SylvainCorlay |
@wjakob On a semi-related note, the stable version of the docs is outdated: http://pybind11.readthedocs.io/en/stable/changelog.html. Updating the stable branch to v2.1 requires a force push so I wanted to check in, rather than just do it. As an alternative, RTD considers the newest tagged release to be stable so the branch isn't strictly needed and can be simply removed -- RTD would automatically update when new tags are pushed. |
Btw, thanks a lot for making this release. |
@dean0x7d: I've pushed v2.1.1 to stable. |
190024210 is for update 3
190024215 is for update 3 with Cumulative Servicing Release