1. Mailing Lists
  2. Contributors
  3. Re: 14.0 branches

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: 14.0 branches

Re: 14.0 branches

Avatar

Re: 14.0 branches

by
Open Architects Consulting, Houssine BAKKALI
- 13/10/2020 10:07:21

I'm curious to know how specific module version dependency will be handled with pip... At least with github we can rely on the repository state at time t.

This case won't happen often but sometimes fix or improvements on module A, imply dev on module B so you will depend on a certain version on module B for the version bringing the fix or improvements on module A.

Or an other case is that on version of module B(on a different repository) brings a bug or regression on you module A so you may want to stick with one version of the module B. How you handle that ?

Anyway I'm not against this move as far as we still have a way to handle the dependency without pip.

On 13/10/2020 09:57, Daniel Reis wrote:
I believe the external_dependencies manifest key supports pinned versions.


On 13/10/2020 08:36, Pedro M. Baeza (Tecnativa) wrote:

> Stéphane, how to pin specific Python libraries versions in this 

> workflow in the generated requirements.txt? We have several places 

> with this requirement.

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe


Virus-free. www.avast.com

Reference