Community mailing list archives
Re: Odoo new api, python3 [was: Re: Odoo ecommerce vs magento]by
thanks @anthony for sharing all this information.
On Tue, May 3, 2016 at 12:37 AM, Antony Lesuisse <firstname.lastname@example.org> wrote:
Development branches are public for Odoo community you can check the current task here: https://github.com/odoo/odoo/pulls?page=1&q=is%3Apr+is%3Aopen+label%3ARD And here for the Enterprise modules (if you are a partner or an odoo enteprise customer): https://github.com/odoo/enterprise/pulls There are many things under developement. Lots of small improvement, every detail matters. Functionaly the biggest change for v10 will be the new manufacturing. https://www.odoo.com/fr_FR/page/manufacturing Another big change IMHO will be the perfomance improvement, we already merged a few branches (i.e. cache based on generation for recordset https://github.com/odoo/odoo/commit/f5f7df9d ). My favortie branch atm is the qweb jit compiler it will speed up to 60x the speed of webpage generation (only for website pages it has almost no effect on the backend). There is a branch that reduce the number of rpc call done to load an action (each time you click on a menu item). Many apps will undergo small (or not so small) improvements, just example with hr.expense https://github.com/odoo/odoo/pull/11104 we will add an alias expense@, take a picture of an expense and send it with the price in the subject and it will create the expense. Then you can select all the expense and group them in a report to submit them for approval. Once approved you will be able to mark the expense paid, so that you can use the app for yourself even if you company doesnt use odoo. You may check the daily commits on odoo/odoo or if you have database on the saas, check the releases notes we publish for the saas releases every 2 month as they provide a nice condensed changelog. I will ask @mat to send a copy of the release notes to community@ each time we deploy them. On 05/03/2016 12:07 AM, Car Wash Sales wrote: > Do you have a odoo roadmap to share? > > On Monday, May 2, 2016, Antony Lesuisse <email@example.com> > > > > > -- > > Fabien > > > > _______________________________________________ > > Mailing-List:https://www.odoo.com/groups/community-59 > > Post to: mailto:firstname.lastname@example.org <mailto:email@example.com> > > Unsubscribe:https://www.odoo.com/groups?unsubscribe > > > > > > _______________________________________________ > > Mailing-List:https://www.odoo.com/groups/community-59 > > Post to: mailto:firstname.lastname@example.org <mailto:email@example.com> > > Unsubscribe:https://www.odoo.com/groups?unsubscribe > > > > > > > > > > -- > > > > _______________________________________________ > > Mailing-List:https://www.odoo.com/groups/community-59 > > Post to: mailto:firstname.lastname@example.org > > Unsubscribe:https://www.odoo.com/groups?unsubscribe > > > > _______________________________________________ > Mailing-List: https://www.odoo.com/groups/community-59 > Post to: mailto:email@example.com > Unsubscribe: https://www.odoo.com/groups?unsubscribe > > _______________________________________________ > Mailing-List: https://www.odoo.com/groups/community-59 > Post to: mailto:firstname.lastname@example.org > Unsubscribe: https://www.odoo.com/groups?unsubscribe >> <mailto:email@example.com>> wrote: > > The switch/case patch has been applied to python 2.7 , so i think the speed > is similar. python2.7 is stable and works perfectly and we have all the > dependecies that we need. > > Our priority now is to migrate all our code to the new orm api. (stock has > just been pushed last week) This will be completed before the v10 release. > > The v10 release will still support the old api. Once released we will remove > support for the old api in master that should give us a 10% speed increase for > the python code and cleaner stack traces. > > Once this is completed we will consider migrating to python3, either for v11 > or for v12. All our dependecies are now available in python3 (except ldap). > Odoo experience 2016 will be a good place to discuss this transition. Python3 > is on our radar it's just low priority right now. > > http://lwn.net/Articles/646888/ > > On 05/02/2016 03:53 PM, Esteban Echeverry - Nubark wrote: > > I also think that moving towards Python 3 compatibility is a must right now. > > We develop our own modules with double compatibility in mind, but it's not > > easy to contribute back to the core if there are no proper guidelines from > > Odoo to approach the migration process. Though "python" is still Python 2.7 in > > Ubuntu 16.04, it is not installed anymore by default, so it is necessary to > > download it to create Odoo's environment, making the installation process > > confusing for newcomers and more involved for sysadmins. Also, there are some > > tech savvy customers who happen to be worried about not having a roadmap for > > the Python upgrade, posing extra difficulty in the selling process. So, in my > > opinion, Odoo is overdue in the task of Python 3 migration and is a topic that > > should be taken into account as soon as possible. > > > > On Mon, May 2, 2016 at 8:03 AM, Andreas Becker <firstname.lastname@example.org > > <mailto:email@example.com>> wrote: > > > > Magento announced officially on January 20th, 2016, that CE and EE 2.0.1 > > officially support PHP 7.0.2. > > > > This also means that it is getting a whole lot faster > > > > Odoo is still Python 2.0 and until now there is no announcment or date set > > when Odoo will run on state of the art Python 3.* > > > > Python 2.* gets discontinued in Ubuntu 16.04 LTS Release > > > > in other words with state of the art common Ubuntu software Odoo won't run > > anymore without adding extras - i.e. Python 2.0. > > > > --- > > > > Beside features, speed etc customers usually are also focussing on how > > long their "investment" in an ecommerce solution will run in future and > > how long it will be maintained and how easy it will be to maintain it. > > > > Until now using Ubuntu 14.04 LTS and running Odoo on it was nice but > > Postgres was slow. In 16.04 LTS you will have a modern Postgres Version > > but no more support for Python 2.* which is the base for all Odoo modules. > > > > On the other hand Magento is already running on the very fast version of > > PHP 7.* like other modern state of the art Open Source Software like TYPO3 > > will do too. > > > > As long as there is no clear statement from the people behind Odoo itself, > > when Odoo will be available for Python 3.0 - Odoo will be an more and more > > outdated system even it would be the number one eCommerce solution IMHO if > > support for Python 3.* would be available in the next Odoo Community > > Version 10. > > > > > > > > > > > > With kind regards, > > Mit freundlichen Grüßen, > > Con un cordial saludo, > > Cordialement, > > с сердечным приветом, > > เรื่องที่เกี่ยวกับชนิด, > > 與親切的問候, > > > > *ANDI BECKER* > > > > CEO/General Manager LisAndi Co., Ltd. > > > > * > >about.me/andibecker > > -------------------------------------------------- > > * > > *LisAndi Co. Ltd.*, Phuket, Thailand (lisandi.com ) > > 15/21 M.2 Viset Road, Rawai, Muang, Phuket, Thailand 83130 > > > > Mobile: +66 (0)81 606 3378 > > VoIP: +49 (0)711 50 88788 50 > > Fax: +49 (0)711 50 88788 50 > > Skype: lisandi > > Facebook: andibecker > > Google Talk/Facetime/eMail:firstname.lastname@example.org <mailto:email@example.com> > > > > -------------------------------------------------- > > > > > > On Mon, May 2, 2016 at 7:14 PM, Fabien Pinckaers <firstname.lastname@example.org > > <mailto:email@example.com>> wrote: > > > > Magento is better than odoo ec module. > > > > > > I already heard that from some Magento integrators, and I think it's a > > misunderstanding of the end-users need and market. The same people > > probably think Magento is much better than shopify because shopify > > does not have a lot of features compared to Magento. But in reallity, > > the market (or users need) value a lot usability and cost of > > implementation as you can see in Google Trends: > >https://www.google.com/trends/explore#q=magento%2Cshopify > > > > It's not only about the features you have, it's about the quality of > > these features, the usability, the website builder, etc. Ask yourself > > why Magento's SaaS offer has been discontinued (Magento Go) after > > several years? Mostly because Magento is so complex that it does not > > work without a costly implementation service. > > > > In short, I would say that: > > 1/ Magento has more "pure eCommerce" features > > 2/ Odoo has more "management features" like marketing, inventory, > > invoicing, jobs, ... > > 3/ Odoo has a better usability and is usually cheaper to > > deploy/configure (try to play with taxes, variants & pricelists with > > Magento) > > 4/ Odoo produces beautiful products pages (website builder) > > 5/ Odoo scales better on high volumes > > > > Usually, it means that if Odoo has the features you need, it's > > probably much better than Magento for your need. But it's possible > > that Odoo does not have the features you need and Magento does. In > > such a case, you have to analyze into the details to check if it's > > better with Magento or Odoo. (develop the missing feature VS complex > > implementation and product) > > > > Also, Odoo is moving very fast in eCommerce. We are not far from > > having as much features as Magento, see: > >https://www.odoo.com/page/ecommerce-comparison