-
Notifications
You must be signed in to change notification settings - Fork 317
simplifying build process step2 in Azure Pipelines #287
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
Comments
less NSIS: #288 build directory known before starting of building |
build directory handling simplification: #298 |
to reconsider when jupyterlab 1.0 will have, at last, landed |
listening Steve, it seems Azure Pipelines will give unlitimited build time, which is the need of the second stage https://talkpython.fm/episodes/show/191/python-s-journey-at-microsoft |
miracle done ... in a jupyterlite experiment: https://github.com/stonebig/my-demo2 |
users can now complete a "dot" version into a "slim" one, using hash requirements (except pandoc.exe) |
Uh oh!
There was an error while loading. Please reload this page.
Build step should go in 3 isolated steps:
Nsis code should be more cleanly isolated along the way.
This should nicely fit the perspective of scipy wheels being in standard pypi this fall 2016
2016-04-08: I just discover that Almar Klein has given-up on "Pyzo" as a distribution:
pyzo/pyzo#379. "too much a burden"
To avoid that very same risk, work is going on this direction:
. users can play a "receipe" or just "pip install" what they need over it (support mingwpy & friends)
. the very same method can be used to build a "fat" branch in the cloud.
The text was updated successfully, but these errors were encountered: