Migration from flit

[WolfgangFahl]

pypa/flit#590 points me here.
When i try to only change the build system i get:

ValueError: Missing `tool.hatch.version` configuration

I'd love to get a pointer to the mandatory fields needed. What makes a pyproject.toml work for hatch?

https://stackoverflow.com/questions/tagged/hatch

doesn't seem to exist.

an internet search points to:

https://hatch.pypa.io/latest/version/

Which i don't understand since there is already a

dynamic = ["version", "description"]  

in my pyproject.toml. Is my assumption wrong that pyproject.toml is for making sure the build system change is hassle free
If not special feature of any of the tools is used?

I'll continue by try and error from here ...

# see https://flit.pypa.io/en/latest/pyproject_toml.html
[build-system]
#requires = ["flit_core >=3.2,<4"]
#build-backend = "flit_core.buildapi"
requires = ["hatchling"]
build-backend = "hatchling.build"

[project]
name = "justpy"
authors = [
  {name = "Eli Mintz", email = "eli.mintz@gmail.com"}
]
maintainers = [
  { name = "Wolfgang Fahl", email = "wf@bitplan.com" },
]
readme = "README.md"
# flit_core.config.ConfigError: license field should be <class 'dict'>, not <class 'str'>
license = { file="LICENSE" }
dependencies = [
        'starlette>=0.20.4', 
        'uvicorn>=0.18.3', 
        'itsdangerous>=2.1.2', 
        'websockets',
        'addict>=2.4.0', 
        'jinja2>=3.1.2', 
        'demjson3>=3.0.5',
        'hjson>=3.1.0',
        'PyYAML>=6.0',
        'httpx>=0.23.0', 
        'aiofiles',
        'twine', 
        'wheel'
    ]

requires-python = ">=3.7"    
classifiers=[
    "Development Status :: 4 - Beta",
    "Environment :: Web Environment",
    "Programming Language :: Python :: 3 :: Only",
    "Programming Language :: Python :: 3.7",
    "Programming Language :: Python :: 3.8",
    "Programming Language :: Python :: 3.9",
    "Programming Language :: Python :: 3.10",
    "Operating System :: OS Independent",
    "Topic :: Software Development :: User Interfaces",
    "Intended Audience :: Developers",
    "Intended Audience :: Education",
    "Intended Audience :: Science/Research",
    "License :: OSI Approved :: Apache Software License"
    ]
dynamic = ["version", "description"]   
 
[project.urls]
Home = "https://justpy.io/"
Documentation = "https://justpy.io/"
Source = "https://github.com/justpy-org/justpy"

[project.optional-dependencies]
test = [
  "aiohttp",
  "asynctest",
  "bokeh", # example
  "green",
  "pandas", # example
  "psutil",
  "pydeck", # example
  "selenium",
  "testfixtures",
  "webdriver-manager"
]

[WolfgangFahl]

surprisingly the flit default to look for the version string in the init.py of the package needs to be specifically set for hatch ...

[tool.hatch.version]
path = "justpy/__init__.py"

[ofek]

Yes Hatch adheres to https://peps.python.org/pep-0020/

Explicit is better than implicit.

😄

[ofek]

Is my assumption wrong that pyproject.toml is for making sure the build system change is hassle free [...] If not special feature of any of the tools is used?

Implementations of dynamic metadata differ between tools. Did you read https://hatch.pypa.io/latest/version/?

[WolfgangFahl]

Yes i had to and was surprised. So at least the https://en.wikipedia.org/wiki/Principle_of_least_astonishment got it's share of the discussion :-) Expectation management is obviously hard. Let's see how the first automatic release goes ...

[WolfgangFahl]

@ofek hurray we got a pypi 0.7.0 with a jpcore package ... impressing ... thanks a lot!

[ofek]

Happy to help!