profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/bealdav/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

bealdav/erp_rename 1

rename odoo modules

bealdav/account-financial-tools 0

Odoo Accountant Financial Tools and Utils

bealdav/adminer 0

Database management in a single PHP file

bealdav/connector-interfaces 0

Odoo Generic Connector for ODBC, .CSV,...

pull request commentOCA/product-attribute

14.0 mig product profile

@sebastienbeau can be merged

sebastienbeau

comment created time in 4 days

PullRequestReviewEvent

push eventbealdav/e-commerce

David Beal

commit sha b75e8d4ed3439d26356304d4cd715b0b30288fd5

whishlist: add active field in whishlist.item to allow to unpublish website product

view details

push time in 7 days

pull request commentOCA/edi

[14.0][IMP] base_ubl: return supplier and customer nodes to allow customization

/ocabot merge minor

FerranCforgeFlow

comment created time in 11 days

issue commentodoo/odoo

Python version for Odoo 15.0

Thanks @d-fence for your quick reply. That's the odoo's position and we respect it.

Now OCA have its own decision to take to run the CI :

  • follow the lowest python version compatible with Odoo (a future obsolete/unsecure version). This version is required by very few people in the community (probably also people running with a very old odoo version)
  • use the mainstream python version (maybe the version use in .sh, 3.9 or 3.8), then we'll speak the same bugs as said by @Yajo

And then this decision should be the OCA one not these of Odoo I suppose.

my 2 cents

bealdav

comment created time in 12 days

issue commentodoo/odoo

Python version for Odoo 15.0

Thanks for your reply @mart-e

Forcing people to upgrade is not good for the planet either (new hardware,...)

Upgrade is just once, CI cycle is for each PR at least.

I didn't know that recent recent version of debian or python required new hardwares (which ones). Maybe you have news on this topic, it could be interesting.

It sounds weird to have a new fresh odoo version with deprecated python libs on next month (security)

Thanks

cc @d-fence

bealdav

comment created time in 12 days

PullRequestReviewEvent

issue commentodoo/odoo

Python version for Odoo 15.0

Odoo policy seems to be version in last Debian stable

https://github.com/odoo/odoo/pull/71437#issuecomment-853865869

Last Debian stable is Bullseye/11 and has Python 3.9

https://wiki.debian.org/Python#Supported_Python_Versions

Then should we waiting for 3.9 for Odoo15 ?

bealdav

comment created time in 13 days

issue commentodoo/odoo

Python version for Odoo 15.0

I have heard than odoo.sh have python 3.8

bealdav

comment created time in 13 days

issue openedodoo/odoo

Python version for Odoo 15.0

Impacted versions:

15.0

Steps to reproduce:

Use Odoo in master / 15.0

Current behavior:

As we can see here https://github.com/odoo/odoo/blob/master/setup.py future Odoo 15.0 rely on python 3.6.

In the same time here is python calendar https://endoflife.date/python

I think to support older python versions for a fresh odoo version has manydrawbacks

  • it prevent to use new python features in odoo itself or in any contributed modules (paid or free).
  • it contrains developpers to support misc use cases (required at least for paid module)
  • redondant CI workflows are played everyday to support these versions it's not really good for planet

Expected behavior:

An option could be to focus on the python version used in odoo.sh Then only change the version in manifest

created time in 13 days

issue closedpyexcel/pyexcel-ods

Python 3.4 causes travis fails

Thanks for your project and thanks to support .ods It seems there is a single point which put your branch red

Travis answer is:

This lxml version requires Python 2.7, 3.5 or later.

May be you can consider to remove support of python 3.4

You're project could be more visible with a green branch

Thanks

closed time in 13 days

bealdav

issue closedOCA/social

RFC manage your daily job with messages and activities, i.e leads

Use case example but can be applied on any model:

  • you need to check what's happens on leads.
  • lead form describe what the lead are but not what are next actions and what's happened in the past
  • you need to check many leads at once, first see those with most events on them to manage your teams vendors
  • you have to filter relevant messages or activities based on your own criteria
  • some systematic odoo message must be exclude because they no added value for you business management
  • a tree view on your object could be a good starting point

Possible implementation:

  • define an sql view to group mail.message with mail.activity
  • apply domain to exclude noisy and irrelevant odoo messages
  • allow to group by user and lead, etc
  • quick access on concerned lead
  • quick create new message/activity
  • ... to complete

cc @clementmbr @MiquelRForgeFlow @pedrobaeza @Yajo @JordiBForgeFlow @LoisRForgeFlow @alexey-pelykh @sebastienbeau

closed time in 13 days

bealdav
PullRequestReviewEvent

pull request commentOCA/edi

[13.0][IMP] base_ubl: hook to add the AdditionalAccountID ubl field

/ocabot merge minor

FerranCforgeFlow

comment created time in 20 days

PullRequestReviewEvent

push eventakretion/purchase-workflow

David Beal

commit sha b828d9c94da5f34c81cb55d4542486ddab73742d

FIX move hook_pending_proposal_approval position call

view details

push time in a month

push eventakretion/purchase-workflow

David Beal

commit sha 3fac494c099247d4a6788d228a989fa22df79636

IMP purch_upd_approval: allow to update delay without reset order

view details

push time in a month

push eventakretion/purchase-workflow

David Beal

commit sha 965f36c88802e092cd6ff7a17647d06522090241

IMP purch_upd_approval: allow to update delay without reset order

view details

push time in a month

push eventakretion/purchase-workflow

David Beal

commit sha 625ee13ffb020f1b3336a2f311618ea4ac5ed962

IMP purch_upd_approval: allow to update delay without reset order

view details

push time in a month

push eventakretion/purchase-workflow

David Beal

commit sha 2775db7478329bb96119b5395b07138b31d0a6ed

IMP purch_upd_approval: allow to update delay without reset order

view details

push time in a month

pull request commentOCA/edi

[13.0][IMP] base_ubl: add customer as an argument in _ubl_add_item method

/ocabot merge minor

FerranCforgeFlow

comment created time in a month

PullRequestReviewEvent

push eventakretion/purchase-workflow

David Beal

commit sha 06497abc10d1d15cc3c9c1b14658b00416ce091e

IMP purch_upd_approval: allow to update delay without reset order

view details

push time in 2 months

pull request commentOCA/edi

[13.0][IMP] base_ubl: add customer as an argument in _ubl_add_item method

OK I'll dive into. Thanks a lot

FerranCforgeFlow

comment created time in 2 months

pull request commentOCA/oca-github-bot

[ADD] rebase_bot

I don't know if it's in the intention of this PR but it could be a good option if author of the PR could apply itself this rebase cmd. But not mandatory

MiquelRForgeFlow

comment created time in 2 months

pull request commentOCA/edi

[13.0][IMP] base_ubl: add customer as an argument in _ubl_add_item method

Hi thanks @FerranCforgeFlow , it seems there are already merged code here ? like in https://github.com/OCA/edi/pull/421/files

Maybe a rebase could only let real updates. Or I missed something ? Thanks

FerranCforgeFlow

comment created time in 2 months

pull request commentOCA/oca-github-bot

[ADD] rebase_bot

l love the idea of this PR. Any hope to be merged in September ?

MiquelRForgeFlow

comment created time in 2 months

pull request commentOCA/edi

[13.0][IMP] account_invoice_ubl & base_ubl: add hooks

Sometimes runbot is unpredictable, I try to merge as it.

FerranCforgeFlow

comment created time in 2 months

pull request commentOCA/edi

[13.0][IMP] account_invoice_ubl & base_ubl: add hooks

/ocabot merge patch

FerranCforgeFlow

comment created time in 2 months

Pull request review commentOCA/edi

[13.0][IMP] account_invoice_ubl & base_ubl: add hooks

 def _ubl_add_header(self, parent_node, ns, version="2.1"):         issue_date = etree.SubElement(parent_node, ns["cbc"] + "IssueDate")         issue_date.text = self.invoice_date.strftime("%Y-%m-%d")         type_code = etree.SubElement(parent_node, ns["cbc"] + "InvoiceTypeCode")-        if self.type == "out_invoice":-            type_code.text = "380"-        elif self.type == "out_refund":-            type_code.text = "381"+        type_code.text = self._ubl_get_invoice_type_code()         if self.narration:             note = etree.SubElement(parent_node, ns["cbc"] + "Note")             note.text = self.narration         doc_currency = etree.SubElement(parent_node, ns["cbc"] + "DocumentCurrencyCode")         doc_currency.text = self.currency_id.name +    def _ubl_get_invoice_type_code(self):+        if self.type == "out_invoice":+            type_code = "380"

suggested but not mandatory

FerranCforgeFlow

comment created time in 2 months