On 24/02/2014 17:00, Daniel Reis wrote:
>
> Hi all,
>
> In a merge proposal for 7.0. came up the question of what Python
> versions should the code be compatible with.
>
> In particular, a dictionay comprehension is used the, available in
> Python 2.7 but not compatible with Python 2.6.
> For refer
On Mon, Feb 24, 2014 at 9:01 PM, Nicolas Jeudy wrote:
>
> 2014-02-25 0:43 GMT+01:00 Raphael Valyi :
>
>> --theirs
>
>
> Can you explain --theirs ?
> I actually try to maintain saas-3 with OCB merge with gihub and it is ok I
> think. I just have many i18n conflict :)
> So if you can explain --their
Hello Pedro,
I think the easiest is to merge official v8 into OCB in a v8 OCB serie
branched from the current v7 OCB.
Now, speaking about automation of the thing, we have to take a step back:
for several reasons, OCB and official v7 belong to different projects and
cannot easily be merged due to
Hi all,
I'm wondering what will be the strategy for integrating all current patches
on future v8 OCB that have been integrated on OCB v7 branch and that are
not going to land on official v8 branch. Can it be easily automated?
Regards.
___
Mailing list:
Title: Eric CAUDAL
+1
Eric Caudal
CEO
--
Elico Corporation, Shanghai branch
OpenERP Premium Certified Training Partner
Cell: + 86 186 2136 1670
Office: + 86 21 6211 8017/27/37
Skype: elico.corp
eric.cau...@elico-corp.com
http://www.elico-corp.co
On the community side, we could encourage the following:
* importing from __future__
* handling exceptions in a forward compatible way
* not using longs
* handling string, bytes and unicode in a forward compatible way
* using proper shebangs in scripts which are only python2 compatible
(#!/usr/bi
On 02/24/2014 05:27 PM, Ferdinand Gassauer wrote:
>
> I think in general the code should be 2.6 compatible for.
>
Agreed. I think it would make sense to follow the OpenERP distribution's
defacto[1] compatibility with Python releases which would include 2.6
for modules compatible with OpenERP 7.0.
You are right, Raphael, but first effort must come from OpenERP itself,
because I think up to now, OpenERP base doesn't work with Python 3, doesn't
it? Next LTS release of Ubuntu may include by default only Python 3 [1], so
maybe it could be a push forward to improve this compatibility.
Regards.
Hello,
I have no strong opinion on that this, but still I share mine: I would say
once we are able to ensure we can follow current Python releases (3.x),
then we can afford the luxury to look backward to try no breaking older
Python versions.
As we are unable to catch up with the Python 3.x line,
You should check the OpenERP WebClient JSON-RPC since it has an specific
implementation to manipulate the payload, more specifically the uid of the
session and the httpsession params to maintain the HttpSession in OpenERP
server, you could look at instance.web.Session class in coresetup.js and
in i
On 2014-02-24 20:00, Daniel Reis wrote:
I think in general the code should be 2.6 compatible for.
For example: in September 2013 the available virtual debian image came
with python 2.6
camptocamp for example uses a specially compiled python version for the
OpenERP server to avoid python confl
Hello all,
I'm trying to build a WebApp proof-of-concept for OpenERP.
It should be a offline-first, mobile-first app, and work independently
from OpenERP's webclient.
For my proof-of-concept I'll be using Boostrap and Backbone with
LocalStorage.
These components are already part of OpenERP's
Hi all,
In a merge proposal for 7.0. came up the question of what Python versions
should the code be compatible with.
In particular, a dictionay comprehension is used the, available in Python
2.7 but not compatible with Python 2.6.
For reference, the MP is:
https://code.launchpad.net/~dreis-p
On 2014-02-05 03:58, Carlos Vásquez wrote:
Ferdinand,
I think you can do this with access rules, we have done similar things
with attachments using rules.
Hi Carlos!
Some (not all) attachments must be only visible by members of the group
who created the attachment and has access right to
Thanks Leonardo Pistone,
I knew a bit about openerp-connector already, but I didn't know
openerp_connector_file.
I'm clueless about base_synchro however.
Does it serve the same purpose as openerp-connector? Are there features
in base_synchro that can't be found in openerp-connector?
Lionel.
L
On 2014-02-24 14:50, Dominique Chabord wrote:
* For big companies it is out of question to migrate every 6,12,18 month
The old system we have developed was enhanced in functionality, but
no "migration" was necessary for +25 YEARS!!!
We just changed the hardware, the underlying database
Review: Approve code review, no tests
LGTM
--
https://code.launchpad.net/~camptocamp/openerp-product-attributes/6.1-fix-search-no-lot-attributes-lep/+merge/204296
Your team OpenERP Community is subscribed to branch
lp:openerp-product-attributes/6.1.
_
The proposal to merge
lp:~camptocamp/openerp-product-attributes/6.1-fix-search-no-lot-attributes-lep
into lp:openerp-product-attributes/6.1 has been updated.
Status: Needs review => Merged
For more details, see:
https://code.launchpad.net/~camptocamp/openerp-product-attributes/6.1-fix-searc
Hello J-A
Le 24/02/2014 11:14, J-A Eberhard / Open Net Sàrl a écrit :
> The price should adjust to the customer perceived value.
> A customer willing to migrate might be ready to pay 50% more.
> A customer that has already migrated, will be please to pay 50% less, and
> keep the warranty going.
i also agree that the pricing model should change and not the one price
fits it all.
i'm not an openerp partner but an enduser. For me the only value its
migration too but i dont agree to pay for an 1 year enterprise contract for
all user with all the things i actually dont need except migration.
I'm agree with Eberhard, cost of migration it's the most expensive part of
total cost. And our customers don't like it. Then like new features of
OpenERP but they don't want to pay for migration too much. So they just
still use old versions and I guess it's not good for OpenERP S.A. too.
my 2 cent
Hello,
The question is not the ratio between our earnings and OpenERP earnings.
The question is the ratio, for the customer, between the cost and the value
received.
If the customer don't see enough value, there is just no earnings to share.
For the customer, the perceived value is the migratio
> Dear Erick, from my point of view, OpenERP SA need change the way of
> make business, to let to their partners earn money too. This is very
> difficult because the head of OpenERP SA prove to be autocratic. An
> example of this show on http://v6.openerp.com/node/1311 slide 9 , that
> says: about
Lionel,
openerp-connector ( http://openerp-connector.com ) is a general
framework for connectors and other things
If you mean openerp_connector_file, (
https://lists.launchpad.net/openerp-connector-community/msg00213.html
), that is a new module that (at the moment) performs the same import
as th
Hi,
Would someone care to elaborate on what is different in base_synchro and
openerp-connector please? or point me to a feature sheet for base_synchro?
I' trying to get an overview of the existing database sync tools for
OpenERP so I can choose the right tool for an upcoming project.
Thanks in
On 02/24/2014 09:54 AM, Alexandre Fayolle wrote:
> However this raises a couple of bootstrapping issues : if I have a
> virtualenv without setuptools, how am I supposed to install buildbot
> slave inside it. Or do you mean one virtualenv for the buildbot slave
> (with setuptools) and another one f
On 22/02/2014 12:04, Georges Racinet wrote:
> On 02/22/2014 08:54 AM, Michael Telahun Makonnen wrote:
>> Hi Alexandre,
>>
>> I didn't know about python -S. Thanks for sharing that.
>
> Yes, we didn't think of it either.
> We've been using virtualenvs without setuptools for that same purpose,
> and
27 matches
Mail list logo
