8000 simplifying build process step2 in Azure Pipelines · Issue #287 · winpython/winpython · GitHub
[go: up one dir, main page]

Skip to content

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

Open
10 of 11 tasks
stonebig opened this issue Mar 12, 2016 · 6 comments
Open
10 of 11 tasks

simplifying build process step2 in Azure Pipelines #287

stonebig opened this issue Mar 12, 2016 · 6 comments

Comments

@stonebig
Copy link
Contributor
stonebig commented Mar 12, 2016

Build step should go in 3 isolated steps:

  • create_launcher should be moved at initial build step, along with scripts creation
  • define a predefined winpydir directory (no need to guess)
  • remove archis list
  • remove rootdir from everything (predefine a basedir and use CHANGELOGS_DIR instead)
  • simplify further changelogs following CHANGELOGS_DIR usage
  • pip install from requirements should be an independant mid-step,
  • create an installer should be an independant last step.

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:

  • go down to 4 "fat" branches for WinPython 2016-03 (against 6 currently).
  • continue reducing NSIS dependance / code, (https://github.com/pfmoore/shimmy not moving but there may be a simpler solution)
  • simplify and improve WinPythonZero so that :
    . 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.
  • simplify WinPythonZero building experience, so that more WinPython users can become builders on-the-go, redo every WinPython creation and building step from scratch.
@stonebig
Copy link
Contributor Author

less NSIS: #288

build directory known before starting of building

@stonebig stonebig changed the title simplfying build process step2 simplifying build process step2 Mar 17, 2016
@stonebig
Copy link
Contributor Author

build directory handling simplification: #298

@stonebig stonebig added this to the 2017-02 Matplotlib-2.0.1 / Jupyterlab-1.0 / Spyder-3.2 milestone Apr 23, 2017
@stonebig stonebig modified the milestones: 2017-03 JupyterLab-1.0beta / Spyder-4.0b2 , 2017-02 Matplotlib-2.0.2 / pandas-0.20.3 / numpy-0.13.1 / Spyder-3.2 Jul 16, 2017
@stonebig stonebig modified the milestones: 2017-03 Spyder-3.2.4 / pandas-0.21.0 / ipywidgets-7.1.0, 2018-02 WinPython-3.7 Oct 31, 2017
@stonebig
Copy link
Contributor Author

to reconsider when jupyterlab 1.0 will have, at last, landed

@stonebig stonebig changed the title simplifying build process step2 simplifying build process step2 in Azure Pipelines Feb 3, 2019
@stonebig
Copy link
Contributor Author
stonebig commented Feb 3, 2019

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

@stonebig
Copy link
Contributor Author

miracle done ... in a jupyterlite experiment: https://github.com/stonebig/my-demo2

@stonebig
Copy link
Contributor Author
stonebig commented May 4, 2025

users can now complete a "dot" version into a "slim" one, using hash requirements (except pandoc.exe)
as WinPython will move to un-installed packages, the cost/time of building a step2 in cloud shall become an option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant
0