Poetry build_backend

[iamamutt]

How is everyone doing development (poetry equivalent of pip install -e .) using poetry as the build-backend? Appending sys.path? Full package install not in dev mode? Poetry core hasn't released this merged PR yet that implements PEP 660. I think after that release we will only need a pyproject.toml file and no setup.cfg or setup.py.

In order to use pip install -e I have to have the following files:

setup.cfg

[metadata]
name = aeon_mecha
version = 0.0.0

[options]
zip_safe = False
packages = find:
include_package_data = True
package_dir =
    =.

[options.packages.find]
where = .
exclude =
    tests
    docs

[options.entry_points]
console_scripts =
    aeon_ingest = aeon.dj_pipeline.ingest.process:cli

setup.py

from setuptools import setup

if __name__ == "__main__":
    setup()

pyproject.toml

[build-system]
requires = ["setuptools", "poetry-core>=1.0.0"]
build-backend = "setuptools.build_meta"

[project]
name = "aeon_mecha"
version = "0.0.0"
description = "Code for managing acquired data. Includes preprocessing, querying, and analysis modules."
authors = ["Jai Bhagat jkbhagatio@gmail.com", "Goncalo Lopes <goncaloclopes@gmail.com>"]
license = ""
readme = "readme.md"
python = ">=3.9.4"
homepage = "https://github.com/projectAeon/data-management"
repository = "https://github.com/projectAeon/data-management"
documentation = "https://github.com/projectAeon/data-management"

[tool.poetry]
name = "aeon_mecha"
version = "0.0.0"
description = "Code for managing acquired data. Includes preprocessing, querying, and analysis modules."
authors = ["Jai Bhagat <jkbhagatio@gmail.com>", "Goncalo Lopes goncaloclopes@gmail.com>"]

[tool.poetry.dependencies]
python = ">=3.9.4"
graphviz = "*"
jupyter = "*"
jupyterlab = "*"
matplotlib = "*"
numpy = "*"
opencv-python = "*"
pandas = "*"
plotly = "*"
scikit-learn = "*"
scipy = "*"
seaborn = "*"

[tool.poetry.dev-dependencies]
bandit = "*"
black = "*"
flake8 = "*"
pytest = "*"
setuptools = "*"
tox = "*"

[tool.poetry.scripts]
aeon_ingest = "aeon.dj_pipeline.ingest.process:cli"

[tool.black]
line-length = 88
target-version = ["py39"]
color = true

[tool.isort]
# make it compatible with black
profile = "black"
color_output = true

keywords = []

classifiers = [  #! Update me
  "Development Status :: 3 - Alpha",
  "Intended Audience :: Developers",
  "Operating System :: OS Independent",
  "Topic :: Software Development :: Libraries :: Python Modules",
  "License :: OSI Approved :: MIT License",
  "Programming Language :: Python :: 3",
  "Programming Language :: Python :: 3.9",
]

[jkbhagatio]

Did you try just running setup.py in develop: python setup.py develop ? Did that not work?

Poetry core hasn't released this merged PR yet that implements PEP 660. I think after that release we will only need a pyproject.toml file and no setup.cfg or setup.py

yes this will be nice when that PR is merged

[iamamutt]

Did you try just running setup.py in develop: python setup.py develop ? Did that not work?

Yes this will work if setup.py and/or setup.cfg are filled out appropriately with info from pyproject.toml as above. Will also give a deprecated warning to use pip.

[jkbhagatio]

Hm ok, I didn't get that deprecation warning last time I tried this. I will make necessary changes specified here in the 'reorg' branch and update the pyenv + poetry set-up instructions there before closing this

[jkbhagatio]

done