GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Confusing versioning of Python package versus Core WebUI · Issue #14 · webui-dev/python-webui

Confusing versioning of Python package versus Core WebUI #14

New issue
Copy link
New issue
Copy link
Open
Open
Confusing versioning of Python package versus Core WebUI#14
Copy link

Description

@kvbik
kvbik
opened on Nov 30, 2023
Issue body actions

Starting with 10ebb25 there was an increment from v2.4.1 to v2.4.2, but the Core WebUI used was still v2.4.1, couple commits later the Core was incremented also, but so was the python wrapper to v2.4.3.

I am no expert on building wrappers and semantic version of those, but I find it rather confusing. I understand the need of iterating the Python wrapper over the same Core version. So maybe what was done before, eg.: v2.4.2.X was bit better?

UPDATE: ok, semantic versioning discourages [1] from keeping the same version number for wrapper and the core library. But maybe in our case here it is not that bad - if they don't differe in one number of the scheme CORE.MAJOR.MINOR.PATCH.

[1] semver/semver#352 (comment)

Activity

  1. hassandraga commented on Nov 30, 2023

    @hassandraga
    hassandraga
    on Nov 30, 2023
    Member
    More actions

    Thank you for suggesting that. This is an important point. We tried to standardize all wrappers (Versions, dealing with binaries...), but we found out that each wrapper has different needs, so we decided to let each wrapper follow its path. It's not the final decision, but it's going well for now.

    should never pin the FooJS version to the Foo version
    [1] semver/semver#352 (comment)

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions
      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.