1. Mailing Lists
  2. Contributors
  3. Re: CI Builds now uses requirements from odoo repository

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: OCA/rma, odoo 10 and crm.claim

Re: CI Builds now uses requirements from odoo repository

Avatar

Re: CI Builds now uses requirements from odoo repository

by
SYLEAM SARL, Sylvain Garancher
- 12/07/2017 23:19:29
For the record, the issue with mock on the report-print-send repo was a bad use of mock 1.0.1 (which seems to say that a method has been called when this is not the case...).
This PR fixes the unit tests : https://github.com/OCA/report-print-send/pull/97

Regards,
--
Sylvain


2017-07-12 21:38 GMT+02:00 Leonardo Rochael Almeida <leorochael@gmail.com>:
Hi,

On 12 July 2017 at 16:08, Moises Lopez <moylop260@vauxoo.com> wrote:
Before:
 - We had a custom requirements.txt from OCA/maintainer-quality-tools (MQT) repository.

Now:
 - We deleted the previous custom requirements.txt from MQT
 - We are using the original odoo's requirements.txt

PR:

New possible errors
[...]
2. odoo 10.0 deleted packages.
  - Example "unittest2"
    - PR related: https://github.com/OCA/connector/commit/3e8d50754252e

Solutions
For both cases the fix is adds explicitly the package and version to requirements.txt root file of your project.

Please, for the unittest2  case, do not re-add the file to `requirements.txt`. Instead simply replace all references to `unittest2` to `unitest` in your addon.

`unittest2` is a backport of `unittest` from Python 2.7 back to earlier versions of Python. There is no reason to use it.

Best regards,

Leo

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



********************************************************************************
Ce message et toutes les pièces jointes (ci-après le "message") sont établis à
l'intention exclusive de ses destinataires et sont confidentiels. Si vous
recevez ce message par erreur, merci de le détruire et d'en avertir
immédiatement l'expéditeur. Toute utilisation de ce message non conforme à sa
destination, toute diffusion ou toute publication, totale ou partielle, est
interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer
l'intégrité de ce message, SYLEAM décline toute responsabilité au titre de ce
message, dans l'hypothèse où il aurait été modifié.

This message and any attachments (the "message") is intended solely for the
addressees and is confidential. If you receive this message in error, please
delete it and immediately notify the sender. Any use not in accord with its
purpose, any dissemination or disclosure, either whole or partial, is prohibited
except after formal approval. The internet can not guarantee the integrity of
this message. SYLEAM cannot therefore be liable for the message if modified.
********************************************************************************

Reference