What is the use of Use of openerp.py file in openerp7.I understand the usage of init.py file.for my custom module how it is useful?
The __openerp__.py file is the OpenERP descriptor which contains a single Python dictionary with the actual declaration of Module. It is necessary file for an openerp module. All the details, dependencies, files used etc are specified here in the __openerp__.py file. Here is Python dictionary key description
name :- Name of Module like 'Sale'
version :- Version of Module like '1.0'
author :- Name of author like who develop this module
category :- Name of Module category like 'Accounting'
website :- Website of a Module
depends :- It's take a list of dependencies, when module install first install the depends modules
description :- Description of the module
summary :- summary of the module.
data :- Data file where we define .xml file path
demo :- Use for demonstration data, if database uses demo data, then it will load.
test :- test data(yaml testing, Unit testing) for this module,
active :- Where to install automatically at new Database creation.
installable :- Whether module is installable or not
auto_install :- When all the dependencies are installed, then this module will automatically install if its true.
Hope this will help you.
The openep.py file is like the setup.py file in Python modules. You need it in every module
Related
because its turn out like this
from printSoln import *
ModuleNotFoundError: No module named 'printSoln'
Im using printSoln how can i install that?
As I know there is not any module named printSoln. This may be some custom .py file that has the functions which are used here.
I found one of its types file on GitHub: https://github.com/mateuv/MetodosNumericos/blob/master/python/NumericalMethodsInEngineeringWithPython/printSoln.py
you can download and write that code and save it in the same folder in which your code file exists.
I am new to Odoo.sh.
When I use the editor to create a new module using the scaffold command
odoo-bin scaffold shelter
The module is named shelter, however, when I try to update current module,
it shows warning:
odoo.modules.loading: invalid module names, ignored: shelter
When i connect to the build, I was not able to see the new module I build under apps.
Anyone know where the problem is?
Question updated:
In odoo sh, under odoo folder, tried the update all module command
In terminal, the warning shown above went away.
However, still no module found named "shelter" after I activate the dev mode and update the apps list.
no module found
Value of conf file listed:
conf file list
well The user is answered in comments. so I am adding the answer for documentation purpose.
when scaffolding a new module make sure that it is added in addon path or listed in odoo configuration file.
I have written a ejabbed custom module but i am not able to install it
According to ejabbed module doc we have to put module files in $HOME/.ejabberd-modules then use ejabberdctl module_check to check the module but i am getting error
Error : not available
I guess your are following the instructions from https://docs.ejabberd.im/developer/extending-ejabberd/modules/#managing-your-own-modules
Did you create the spec file, as mentioned in this paragraph?
and creating a specification file in YAML format as
mod_mysupermodule.spec (see examples from ejabberd-contrib). From that
point you should see it as available module.
In recent days, it has become impossible to update the modules. I receive an error such as "this is not a valid module name".
Is it possible to manually update the modules by retrieving the latest files from Github? I tried to replace the files with those of the latest version but, it doesn't change anything at all.
I precise that I try to update official modules that are pre-installed in Prestashop.
Yes you can do this.
Grab the moduble from GitHub, wrap the whole module (the ps_xxxxxx directory) in a zip file then install the module from the admin interface.
Don't replace the files manually by using the filesystem (or at least try not to).
If you replace the modules in the modules directory you won't trigger the module "install" method, so if the new version needs some initialization it won't work properly.
EDIT:
Some modules have dependencies, for example ps_facetedsearch will require you to install composer and run 'composer install --no-dev' before you can pack it into a zip.
Alternatively you can get a json list of native prestashop modules here (replace [VERSION] with the version of prestashop you want, ex 1.7.6.4) :
https://api-addons.prestashop.com/?format=json&iso_lang=en&iso_code=all&version=[VERSION]&method=listing&action=native
Then you can download the module with its id with this URL (replace [VERSION] and [MODULE_ID] :
https://api-addons.prestashop.com/?format=json&iso_lang=en&iso_code=EN&version=[VERSION]&method=module&id_module=[MODULE_ID]
I am working on an existing python application inside of a virtualenv environment. It is already set up to use wheel within its deployment.
I have added another module which my application now needs, and this module only exists in egg format. It is currently installed among all the other modules within ./env/lib/python3.6/site-packages, and an egg-info directory exists for it.
My question is this: how do I convert this one egg-info directory to wheel format, so that it gets included in the application's deployment when I do the following? ...
python3 setup.py bdist_wheel upload -r XXXXXXXX
Assuming I have installed a module under ./env/lib/python3.6/site-packages/the-module-1.2.3.egg-info, what are the steps to convert that module to dist-info?
Note that I don't see any *.egg file for that module, only the egg-info directory.
Thank you.