Skip to content

Conversation

jcheng5
Copy link
Collaborator

@jcheng5 jcheng5 commented Aug 21, 2024

This builds properly, but it doesn't quite work on local builds; requests for shiny.js result in 404. I think it may have to do with the + character that setuptools_scm puts into the version string, e.g. 1.0.1.dev21+g4d7a2e5e.d20240821.

@jcheng5 jcheng5 marked this pull request as ready for review August 22, 2024 03:05
@jcheng5
Copy link
Collaborator Author

jcheng5 commented Aug 22, 2024

@wch @schloerke can either of you think of any downstream problems from shiny having version numbers that look like 1.0.1.dev27? In shinylive or something? Because this branch adds setuptools_scm and the way I've configured it, it will use version numbers like that for untagged builds.

@schloerke
Copy link
Collaborator

Projects:

  • py-shinywidgets: ✅ ; Does not use the shiny version
  • py-shinyswatch: ✅ ; Uses installed shiny package and only uses bootstrap version.
  • shinylive assets: ✅ ; Does not use shiny version
  • py-shinylive: ✅ ; Currently only uses assets version and it's own package version
  • shinylive quarto extension: ✅ ; It only compares the shinylive assets version.
    • There could be possible issues in the future if we add .dev versions to py-shinylive. But in the current form it should work as long as the major and minor versions are not confused with .dev.

I may have missed something and would like @wch to add his stamp of approval. But I have confidence so far!


If we do need it on the packaging side, we can leverage packaging.version import Version for version comparison.

To remind myself... Unlike R where versions go from 1.1.0 to 1.1.0.9000, python's .dev signals a dev version of the number that it's attached to. So after a 1.1.0 release, py-shiny should immediately update the version to 1.2.0.dev. As Version("1.2.0.dev0") < Version("1.2.0") is True.

@jcheng5
Copy link
Collaborator Author

jcheng5 commented Aug 22, 2024

TODO: Check if additional (unwanted) files are included in the sdist package bundle due to using setuptools_scm

@jcheng5 jcheng5 force-pushed the pyproject.toml branch 2 times, most recently from 38916ca to 0f21df9 Compare August 22, 2024 20:13
@jcheng5 jcheng5 requested a review from machow August 23, 2024 00:11
@jcheng5 jcheng5 merged commit 77a6792 into main Aug 23, 2024
48 checks passed
@jcheng5 jcheng5 deleted the pyproject.toml branch August 23, 2024 16:42
schloerke added a commit to machow/py-shiny that referenced this pull request Sep 5, 2024
* main:
  setup.cfg -> pyproject.toml (posit-dev#1625)
  docs(navset): Add server function to navset docs (posit-dev#1596)
  Pin syrupy to avoid pytest-rerunfailures incompatibility (posit-dev#1632)
  refactor: `shiny create` and `shiny add test` supporting functions (posit-dev#1629)
  Update CHANGELOG.md
  Fix posit-dev#1601: Force text/javascript for .js files
  Work around griffe 1.0 breaking changes
  feat(shiny create): Support simpler syntax for `--github` flag (posit-dev#1623)
  Make sure `Chat.messages(format='google')` converts role assistant -> model (posit-dev#1622)
  Fix `NormalizerRegistry.register()` (posit-dev#1619)
  Update JS/CSS from shiny and bslib (posit-dev#1617)
  Add ability to update `Chat()`'s input placeholder (posit-dev#1594)
  docs: Add double-quotes to shiny[theme] (posit-dev#1605)
  `json.dump()` each websocket message once instead of twice (posit-dev#1597)
  docs: Update note on style keys allowing for kebab-case (posit-dev#1595)
  docs: fix navset function links (posit-dev#1590)
  Get `ui.Chat()` working inside Shiny modules (posit-dev#1582)
  bug(notification): Allow for duration to be `None` and passed to client (posit-dev#1577)
  Fix logic for detection of support files in docs (posit-dev#1580)
  docs(navset): Add examples for navset (posit-dev#1579)
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.

3 participants