Skip to content
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

Merged
merged 1 commit into from
Apr 1, 2017
Merged

Wrong msvc version #773

merged 1 commit into from
Apr 1, 2017

Conversation

SylvainCorlay
Copy link
Member

@SylvainCorlay SylvainCorlay commented Mar 31, 2017

190024210 is for update 3
190024215 is for update 3 with Cumulative Servicing Release

@SylvainCorlay
Copy link
Member Author

SylvainCorlay commented Mar 31, 2017

cc @wjakob @jagerman you probably want to get this one in shortly and push out a 2.1.1...

@jagerman
Copy link
Member

jagerman commented Apr 1, 2017

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.

@JohanMabille
Copy link
Contributor

vs_tb1

@jagerman jagerman merged commit 37ef74c into pybind:master Apr 1, 2017
@jagerman
Copy link
Member

jagerman commented Apr 1, 2017

@wjakob - thoughts re: 2.1.1 release for this?

@SylvainCorlay SylvainCorlay deleted the update-3 branch April 1, 2017 21:42
@SylvainCorlay
Copy link
Member Author

@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.

@wjakob
Copy link
Member

wjakob commented Apr 7, 2017

@SylvainCorlay: ok, done -- feel free to merge the feedstock PR once the CI tests have passed.

@SylvainCorlay
Copy link
Member Author

The issue is that this comes after the backward incompatible removal of borrow and stolen, so 2.1.1 would not be a good number, unless you branch out 2.1.0, include the patch and release.

@SylvainCorlay
Copy link
Member Author

SylvainCorlay commented Apr 7, 2017

@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.

@wjakob
Copy link
Member

wjakob commented Apr 7, 2017

@SylvainCorlay
Actually I just cherry-picked the MSVC version check -- otherwise it is completely identical to 2.1.0. However, there is some weirdness with SHA256 checksums that's preventing the feedstock from completing.

@dean0x7d
Copy link
Member

dean0x7d commented Apr 7, 2017

@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.

@SylvainCorlay
Copy link
Member Author

Btw, thanks a lot for making this release.

@wjakob
Copy link
Member

wjakob commented Apr 7, 2017

@dean0x7d: I've pushed v2.1.1 to stable.

@rwgk rwgk mentioned this pull request Feb 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants