Proposal: Add optional support for local installation using venv + pip install -e . (alternative to uv)

[spyke7]

Hi all!
I want to contribute to open science labs, so I came across conecting-osp project and wanted to test it out and noticed that the current installation workflow primarily depends on uv, which works perfectly with the existing uv.lock setup.

However, I wanted to propose an alternative (optional) way to install and run the project locally — especially for contributors or environments where using uv might not be convenient.

The idea is to make it possible to run the project using the standard Python venv + pip install -e . workflow without breaking existing uv functionality.
I just slightly want to extend the pyproject.toml file without changing anything. It would work perfectly fine with the existing setup as well as if someone wants to just simply create a venv and install it locally in the developer mode.
Also the proposed changes are going to be good in terms of maintainability.

I’ve tested the modified setup locally — both uv installation and standard pip editable installs work fine side-by-side.
If this sounds good, I’d love to open a small PR with the changes and update the README to include both installation methods.

[spyke7]

pyproject.toml will be looking something like this -

[project]
name = "connecting-osp"
version = "0.1.0"
description = "Add your description here"
readme = "README.md"
requires-python = ">=3.11"
dependencies = [
    "jupyterlab>=4.3.6",
    "pandas>=2.2.3",
    "quarto-cli>=1.6.42",
]

[build-system]
requires = ["setuptools>=61.0"]
build-backend = "setuptools.build_meta"

[tool.setuptools]
packages = []

[tool.setuptools.package-data]
"*" = ["*.csv", "*.json", "*.yml", "*.yaml"]

If it is ok then I will very much happy to generate a pull request.