[16.0][IMP] resource_booking: pyproject.toml

[norlinhenrik]

No description provided.

[pedrobaeza]

This is not correct. The file goes inside a module folder, not on the root, and it's populated automatically by pre-commit when needed.

[norlinhenrik]

But there is no such automation in 16.0, and I don't know how to set it up.
Can you please help me with this, or accept the PR?

[norlinhenrik]

Sorry, I meant to put it inside resource_booking.

[pedrobaeza]

I don't get the goal of this, because it's perfectly fine working with the previous approach. Anyway, I don't use pip for Odoo and I don't like it.

[norlinhenrik]

Have you tried uv as presented on the OCA days (see repo, slides and talk)? I think it is really cool. :)

[tool.uv.sources]
odoo-addon-resource-booking = { git = "https://github.com/OCA/calendar", subdirectory = "resource_booking" }

× Failed to download and build odoo-addon-resource-booking @ │ git+https://github.com/OCA/calendar#subdirectory=resource_booking
╰─▶ /home/henrik/.cache/uv/git-v0/checkouts/68862a3fc51fb503/9ddfab2/resource_booking does not appear to be
a Python project, as neither pyproject.toml nor setup.py are present in the directory

[tool.uv.sources]
odoo-addon-resource-booking = { git = "https://github.com/OCA/calendar", rev = "refs/pull/144/head", subdirectory = "resource_booking" }

Problem solved

[pedrobaeza]

Yeah, the umpteenth Python package manager...

The question is that Odoo modules are not Python packages, and trying to make them to "appear" as if they are, only adds layers and layers and hacks, like the previous setup folderor this.tomlfile. Some think that is not too much, but for me is still twisting everything. And for not talking about Odooaddons_path` manipulation...

[norlinhenrik]

Try to install uv (e.g. sudo snap install astral-uv) and then:

git clone https://github.com/sbidoul/ocadays2024-odoo-project-demo -b uv-level4
cd ocadays2024-odoo-project-demo
uv run odoo

This is the easiest way I have ever seen to run a custom odoo project.

• Everything is configured in pyproject.toml.
• All dependencies become available in Odoo addons_path.
• We can specify the source of a specific module.
• uv.lock has the commit of each python source, including Odoo.

[pedrobaeza]

A Doodba copier template is easiest in my opinion and covering more cases (devel, prod and demo instances, Mailhog, debuggers...)

[norlinhenrik]

Doodba is good also, although it takes more steps to get started. The documentation is fairly good about setup and development. But I was not able to move on to test and production. Besides improving that part of the documentation, I suggest you make a doodba demo on the next OCA days, with slides and a repo showing step by step what to do. I just found now that you had a talk in 2020. I should have seen that before. Anyway, repetition is good.

Do you consider Doodba to be incompatible with installing Odoo as python modules?

[pedrobaeza]

Yes, it's incompatible by some reasons.

[norlinhenrik]

I see.

I didn't plan to reply, but I am curious why Odoo python modules make a problem in Doodba?

BTW: Thank you for all your open source contributions! ❤️ Doodba has many cool features integrated, and I would like to learn them eventually.

[pedrobaeza]

The reasons are technical, and they can be in any moment bypassed/fixed. Don't think it's another kind of resistance. It's just that I don't remember right now which ones.