Scientific Python
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
      • Invitee
      • No invitee
    • Publish Note

      Publish Note

      Everyone on the web can find and read all notes of this public team.
      Once published, notes can be searched and viewed by anyone online.
      See published notes
      Please check the box to agree to the Community Guidelines.
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Sharing URL Help
Menu
Options
Versions and GitHub Sync Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
Invitee
No invitee
Publish Note

Publish Note

Everyone on the web can find and read all notes of this public team.
Once published, notes can be searched and viewed by anyone online.
See published notes
Please check the box to agree to the Community Guidelines.
Engagement control
Commenting
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
  • Everyone
Suggest edit
Permission
Disabled Forbidden Owners Signed-in users Everyone
Enable
Permission
  • Forbidden
  • Owners
  • Signed-in users
Emoji Reply
Enable
Import from Dropbox Google Drive Gist Clipboard
   owned this note    owned this note      
Published Linked with GitHub
Subscribed
  • Any changes
    Be notified of any changes
  • Mention me
    Be notified of mention me
  • Unsubscribe
Subscribe
# Planning Meeting: Build Systems, CI Infrastructure **Date:** Friday 12:00 - 1:00 PM **Topics:** Build Systems, CI Infrastructure **Issues:** [#3](https://github.com/scientific-python/summit-2023/issues/3), [#5](https://github.com/scientific-python/summit-2023/issues/5) ### Attendees - Juanita Gomez - Brigitta Sipőcz - Jarrod Millman - Stéfan van der Walt - Leah Wasser - Martin Fleischmann - Paul Ivanov - Tyler Reddy - Henry Schreiner - Mridul Seth - Levi Wolf - Madicken Munk - Greg Lee ## Relevant links - https://scientific-python.org/specs/spec-0004/ - https://scientific-python.org/specs/spec-0005/ ## Ideas from issues **Brigitta**: - job that tests nightly wheels/dev versions. Maybe a separate job that tests pre-releases. - job that tests the oldest supported versions of declared dependencies - cron jobs: notification are not working properly on github, we should implement a small tool, workaround to get notifications to maintainers - filterwarnings to error out on warnings: expected warnings should be handled in CI, or ignored. Erroring out by default provides enormous help to notice new deprecations while upstream dependencies are still in their dev cycle (assuming there is a job that uses the dev versions/nightly builds) Also, this could include documentation about the available CI tooling, though there is a risk involved here with keeping this up-to-date. **Dan McCloy**: encouragement / guidance / templates for member projects on setting up a CI job that uses pip --pre or nightlies or some other way of getting early warning of breaking changes in dependencies. This could involve tutorial/documentation material (#21) as well as template files (#10) **Brigitta:** another piece: cron github jobs to issue send out notifications (preferably staying within github rather than an email, but email is still better than the current not really predictable mess). Of course, it would be best if github would start supporting it, but I don't think we should wait for them as it could take years. Chatted with Ross about this, but haven't come up with an actual implementation to make it happen. ------------------------------------------------------- ## Meeting notes Jarrod: two issues, not sure which one to start with. - let's start with build system stuff. - working with networkX - not a lot of building difficulties there - CIbuildwheel system Henry: - [scikit-build / scikit-build-core](https://github.com/scikit-build/scikit-build-core), [meson / meson-python](https://meson-python.readthedocs.io/en/latest/) avoid setuptools - question: what do we want to address - there are lots of things that would be needed. - scikit-HEP development pages - reporeview.dev? - cookie-cutter that has 12 different backends - put it under a better name? Jarrod: - most projects are aware of 3.12 coming out - 3.12 removes distutils, but doesn't affect all that many projects - Except those based on numpy.distutils? - But, in next beta (on Monday, 5/22), setuptools no longer in default environment; so libraries won't build without `pyproject.toml` - ~300 projects using scikit-build, 80 did not have a pyproject.toml Leah: - people are confused about which project they should be using to get started - what are the general standards that work for people that are not using pure python * sounds like there is some examples in scikit build docs for fortran?? Henry: - https://scikit-build-core.readthedocs.io/en/latest/getting_started.html - there needs to be better documentation on examples showing multiple systems Jarrod: - there may be some churn, like there was with version control Henry: - CMake is heavily used. Building subproject while building a project. Leah: - Sometimes options are overwhelming, and some people just want an answer. Ross: - as someone that wants to just be a consumer of this - PyPA's distributing binary extension is "FIXME" and has been, for years - https://packaging.python.org/en/latest/guides/packaging-binary-extensions/#publishing-binary-extensions Jarrod https://github.com/scientific-python/spin - common interface to build docs, run test - currently works with meson-python - extension of devpy Henry: - why not use tox and nox? Example from Stéfan - https://github.com/scikit-image/scikit-image/blob/main/.spin/cmds.py Henry: - I think a large part of the reason dev.py got developed is there was no editable install at the time. Ross: - `pip install -e .` and `make html` used to work on all of the projects Henry: - standardization could be a set of commands that all projects support. ## CI discussion Brigitta: - two draft SPECs to push over the draft status GH actions # Action Plan - review/compare/unify spin/nox/tox - S: can we get nox to print a proper help string? E.g.: ``` $ spin docs --help Usage: spin docs [OPTIONS] 📖 Build documentation By default, SPHINXOPTS="-W", raising errors on warnings. To build without raising on warnings: SPHINXOPTS="" spin docs Options: --clean Clean previously built docs before building --install-deps / --no-install-deps Install dependencies before building [default: install-deps] --build / --no-build Build skimage before generating docs [default: build] --help Show this message and exit. ``` That would get us 80% of the way there. - create a place where we collect topics to learn about - port scikit-hep developer docs and use for training at summit - finish/implement [SPEC 4 (nightly wheels)](https://specs.scientific-python.org/spec-0004/) and [SPEC 5 (CI best practices)](https://specs.scientific-python.org/spec-0005/), and [issue #3](https://github.com/scientific-python/summit-2023/issues/3) - leah - id love to work a bit on suggestions / examples for non pure python packaging - build pygrapviz wheels (Ross has SDist that can be installed but is struggling with packaging the required deps into the wheels)

Import from clipboard

Advanced permission required

Your current role can only read. Ask the system administrator to acquire write and comment permission.

This team is disabled

Sorry, this team is disabled. You can't edit this note.

This note is locked

Sorry, only owner can edit this note.

Reach the limit

Sorry, you've reached the max length this note can be.
Please reduce the content or divide it to more notes, thank you!

Import from Gist

Import from Snippet

or

Export to Snippet

Are you sure?

Do you really want to delete this note?
All users will lose their connection.

Create a note from template

Create a note from template

Oops...
This template is not available.
Upgrade
All
  • All
  • Team
No template found.

Create custom template

Upgrade

Delete template

Do you really want to delete this template?
Turn this template into a regular note and keep its content, versions, and comments.

This page need refresh

You have an incompatible client version.
Refresh to update.
New version available!
See releases notes here
Refresh to enjoy new features.
Your user state has changed.
Refresh to load new user state.

Sign in

Forgot password

or

By clicking below, you agree to our terms of service.

Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
Wallet ( )
Connect another wallet

New to HackMD? Sign up

Help

  • English
  • 中文
  • Français
  • Deutsch
  • 日本語
  • Español
  • Català
  • Ελληνικά
  • Português
  • italiano
  • Türkçe
  • Русский
  • Nederlands
  • hrvatski jezik
  • język polski
  • Українська
  • हिन्दी
  • svenska
  • Esperanto
  • dansk

Documents

Help & Tutorial

How to use Book mode

How to use Slide mode

API Docs

Edit in VSCode

Install browser extension

Get in Touch

Feedback

Discord

Send us email

Resources

Releases

Pricing

Blog

Policy

Terms

Privacy

Cheatsheet

Syntax Example Reference
# Header Header 基本排版
- Unordered List
  • Unordered List
1. Ordered List
  1. Ordered List
- [ ] Todo List
  • Todo List
> Blockquote
Blockquote
**Bold font** Bold font
*Italics font* Italics font
~~Strikethrough~~ Strikethrough
19^th^ 19th
H~2~O H2O
++Inserted text++ Inserted text
==Marked text== Marked text
[link text](https:// "title") Link
![image alt](https:// "title") Image
`Code` Code 在筆記中貼入程式碼
```javascript
var i = 0;
```
var i = 0;
:smile: :smile: Emoji list
{%youtube youtube_id %} Externals
$L^aT_eX$ LaTeX
:::info
This is a alert area.
:::

This is a alert area.

Versions and GitHub Sync
Upgrade to Prime Plan

  • Edit version name
  • Delete

revision author avatar     named on  

More Less

No updates to save
Compare with
    Choose a version
    No search result
    Version not found
Sign in to link this note to GitHub
Learn more
This note is not linked with GitHub
 

Feedback

Submission failed, please try again

Thanks for your support.

On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

Please give us some advice and help us improve HackMD.

 

Thanks for your feedback

Remove version name

Do you want to remove this version name and description?

Transfer ownership

Transfer to
    Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

      Link with GitHub

      Please authorize HackMD on GitHub
      • Please sign in to GitHub and install the HackMD app on your GitHub repo.
      • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
      Learn more  Sign in to GitHub

      Push the note to GitHub Push to GitHub Pull a file from GitHub

        Authorize again
       

      Choose which file to push to

      Select repo
      Refresh Authorize more repos
      Select branch
      Select file
      Select branch
      Choose version(s) to push
      • Save a new version and push
      • Choose from existing versions
      Include title and tags
      Available push count

      Upgrade

      Pull from GitHub

       
      File from GitHub
      File from HackMD

      GitHub Link Settings

      File linked

      Linked by
      File path
      Last synced branch
      Available push count

      Upgrade

      Danger Zone

      Unlink
      You will no longer receive notification when GitHub file changes after unlink.

      Syncing

      Push failed

      Push successfully