Saravanan666/pypi-org huggingface dataset:
Package: openerp-point-of-sale
This module allows you to manage your shop sales very easily with a fully web based touchscreen interface.
It is compatible with all PC tablets and the iPad, offering multiple payment methods.Product selection can be done in several ways:Using a barcode readerBrowsing through categories of products or via a text search.Main FeaturesFast encoding of the saleChoose one payment method (the quick way) or split the payment between several payment methodsComputation of the amount of money to returnCreate and confirm the picking list automaticallyAllows the user to create an invoice automaticallyRefund previous sales
Package: openerp-portal
A portal defines a specific user menu and access rights for its members.  This
menu can ben seen by portal members, anonymous users and any other user that
have the access to technical features (e.g. the administrator).
Also, each portal member is linked to a specific partner.The module also associates user groups to the portal users (adding a group in
the portal automatically adds it to the portal users, etc).  That feature is
very handy when used in combination with the module ‘share’.
Package: openerp-portal-sale
After installing this module, portal users will be able to access their own documents
via the following menus:QuotationsSale OrdersDelivery OrdersProducts (public ones)InvoicesPayments/RefundsIf online payment acquirers are configured, portal users will also be given the opportunity to
pay online on their Sale Orders and Invoices that are not paid yet. Paypal is included
by default, you simply need to configure a Paypal account in the Accounting/Invoicing settings.
Package: openerp-procurement
In the MRP process, procurements orders are created to launch manufacturing
orders, purchase orders, stock allocations. Procurement orders are
generated automatically by the system and unless there is a problem, the
user will not be notified. In case of problems, the system will raise some
procurement exceptions to inform the user about blocking problems that need
to be resolved manually (like, missing BoM structure or missing supplier).The procurement order will schedule a proposal for automatic procurement
for the product which needs replenishment. This procurement will start a
task, either a purchase order form for the supplier, or a production order
depending on the product’s configuration.
Package: openerp-product-visible-discount
To this end, a new check box named ‘Visible Discount’ is added to the pricelist form.Example:For the product PC1 and the partner “Asustek”: if listprice=450, and the price
calculated using Asustek’s pricelist is 225. If the check box is checked, we
will have on the sale order line: Unit price=450, Discount=50,00, Net price=225.
If the check box is unchecked, we will have on Sale Order and Invoice lines:
Unit price=225, Discount=0,00, Net price=225.
Package: openerp-project-gtd
This module implements a simple personal to-do list based on tasks. It adds an editable list of tasks simplified to the minimum required fields in the project application.The to-do list is based on the GTD methodology. This world-wide used methodology is used for personal time management improvement.Getting Things Done (commonly abbreviated as GTD) is an action management method created by David Allen, and described in a book of the same name.GTD rests on the principle that a person needs to move tasks out of the mind by recording them externally. That way, the mind is freed from the job of remembering everything that needs to be done, and can concentrate on actually performing those tasks.
Package: openerp-project-long-term
Manage Big projectDefine various Phases of ProjectCompute Phase Scheduling: Compute start date and end date of the phases
which are in draft, open and pending state of the project given. If no
project given then all the draft, open and pending state phases will be taken.Compute Task Scheduling: This works same as the scheduler button on
project.phase. It takes the project as argument and computes all the open,
draft and pending tasks.Schedule Tasks: All the tasks which are in draft, pending and open state
are scheduled with taking the phase’s start date.
Package: openerp-project-mrp
This module will automatically create a new task for each procurement order line
(e.g. for sale order lines), if the corresponding product meets the following
characteristics:Product Type = ServiceProcurement Method (Order fulfillment) = MTO (Make to Order)Supply/Procurement Method = ManufactureIf on top of that a projet is specified on the product form (in the Procurement
tab), then the new task will be created in that specific project. Otherwise, the
new task will not belong to any project, and may be added to a project manually
later.When the project task is completed or cancelled, the workflow of the corresponding
procurement line is updated accordingly. For example, if this procurement corresponds
to a sale order line, the sale order line will be considered delivered when the
task is completed.
Package: openerp-purchase
Purchase management enables you to track your suppliers’ price quotations and convert them into purchase orders if necessary.
OpenERP has several methods of monitoring invoices and tracking the receipt of ordered goods. You can handle partial deliveries in OpenERP, so you can keep track of items that are still to be delivered in your orders, and you can issue reminders automatically.OpenERP’s replenishment management rules enable the system to generate draft purchase orders automatically, or you can configure it to run a lean process driven entirely by current production needs.Dashboard / Reports for Purchase Management will include:Request for QuotationsPurchase Orders Waiting ApprovalMonthly Purchases by CategoryReceptions AnalysisPurchase Analysis
Package: openerp-report-webkit
The module structure and some code is inspired by the report_openoffice module.The module allows:HTML report definitionMulti header supportMulti logoMulti company supportHTML and CSS-3 support (In the limit of the actual WebKIT version)JavaScript supportRaw HTML debuggerBook printing capabilitiesMargins definitionPaper size definitionMultiple headers and logos can be defined per company. CSS style, header and
footer body are defined per company.For a sample report see also the webkit_report_sample module, and this video:http://files.me.com/nbessi/06n92k.movRequirements and Installation:This module requires thewkthtmltopdflibrary to render HTML documents as
PDF. Version 0.9.9 or later is necessary, and can be found athttp://code.google.com/p/wkhtmltopdf/for Linux, Mac OS X (i386) and Windows (32bits).After installing the library on the OpenERP Server machine, you may need to set
the path to thewkthtmltopdfexecutable file in a system parameter namedwebkit_pathin Settings -> Customization -> Parameters -> System ParametersIf you are experiencing missing header/footer problems on Linux, be sure to
install a ‘static’ version of the library. The defaultwkhtmltopdfon
Ubuntu is known to have this issue.TODO:JavaScript support activation deactivationCollated and book format supportZip return for separated PDFWeb client WYSIWYG
Package: openerp-sale
This application allows you to manage your sales goals in an effective and efficient manner by keeping track of all sales orders and history.It handles the full sales workflow:Quotation->Sales order->InvoicePreferences (only with Warehouse Management installed)If you also installed the Warehouse Management, you can deal with the following preferences:Shipping: Choice of delivery at once or partial deliveryInvoicing: choose how invoices will be paidIncoterms: International Commercial termsYou can choose flexible invoicing methods:On Demand: Invoices are created manually from Sales Orders when neededOn Delivery Order: Invoices are generated from picking (delivery)Before Delivery: A Draft invoice is created and must be paid before deliveryThe Dashboard for the Sales Manager will includeMy QuotationsMonthly Turnover (Graph)
Package: openerp-sale-journal
This module is very helpful for bigger companies that works by departments.You can use journal for different purposes, some examples:isolate sales of different departmentsjournals for deliveries by truck or by UPSJournals have a responsible and evolves between different status:draft, open, cancel, done.Batch operations can be processed on the different journals to confirm all sales
at once, to validate or invoice packing.It also supports batch invoicing methods that can be configured by partners and sales orders, examples:daily invoicingmonthly invoicingSome statistics by journals are provided.
Package: openerp-sale-stock
This module makes the link between the sales and warehouses management applications.PreferencesShipping: Choice of delivery at once or partial deliveryInvoicing: choose how invoices will be paidIncoterms: International Commercial termsYou can choose flexible invoicing methods:On Demand: Invoices are created manually from Sales Orders when neededOn Delivery Order: Invoices are generated from picking (delivery)Before Delivery: A Draft invoice is created and must be paid before delivery
Package: openerp-sane
openerp-sane is a collection of small utilities, making OpenERP development seem less like ancient
warfare with blood and guts everywhere, and more like Python.For now, there’s two utilities:@oemethands2d/d2s(date conversion). The@oemethmethod decorator which straightens out our we manage the famousidsargument in our model
methods. Example:defmyaction(self,cr,uid,ids,context=None):passNormally,idsis supposed to be a list ofint, butsometimes, just,sometimes, we get
a nakedint, then our method crashes. We have to add code like:ifisinstance(ids,(int,long)):ids=[ids]On top of that, there’s another annoyance: why, ohwhydo all my methods have to handle cases
with multipleids? When I have an action for some button in a form, Iknowit’s only ever
going to handle one id at a time. I can doids[0]easily enough, but if I really want to be
on the safe side, I’ll make sure thatidsis a list first. Aren’t you tired of that ridiculous
dance? Well, that’s why we have@oemethInstallYou can’t wait to start using it in your modules, right? openerp-sane can be installed from PyPI:$ pip install openerp-saneWhen you use it in a module, you can document its dependency to it in your__openerp__.py:{# [...]'external_dependencies':{'python':['openerp_sane'],},# [...]}@oemeth@oemethis a method decorator that takes 2 (optional, default toFalse) arguments:singleandbrowse. By default, it simply makes sure thatidsis a list:fromopenerp_saneimportoemeth# [...]@oemethdefmyaction(self,cr,uid,ids,context=None):# Write code that assumes ids is a listWithsingletoTrue, we enforce a singleintid:@oemeth(single=True)defmyaction(self,cr,uid,objid,context=None):# objid is an ``int``.# WARNING: Use this only when you're sure that you'll only ever have single arguments.# If the input is a list with a len() != 1, an exception is raised.WithbrowsetoTrue, we wrap our id(s) in aself.browse()call:@oemeth(browse=True)defmyaction(self,cr,uid,objs,context=None):# objs is a list of browse recordss2d/d2ss2d()andd2s()(meaning “string-to-date” and “date-to-string”) are there to alleviate the
horrible problem we face when we actually have to process and compare dates. Without these helpers,
we have to manually convert those with the right date format, which can get heavy quick.s2d(string_date)takes the string value from a date field and returns adatetime.date. If
it can’t parse it, it returnsFalse.d2s(date)takes adatetime.dateand returns a string which can be written to a date field.
Ifdateisn’t a date, we returnFalse(which can also be written to a date field).In both those functions, we use OE’sDEFAULT_SERVER_DATE_FORMATconstant.Bits of wisdomDon’t usesingle(which requires to always have exactly one id all the time) onon_changemethods. Sure, most of the time you get a single id, but if your call is made on a record that
isn’t committed yet, you will get zero ids, which will raise an exception. In the future, maybe thesinglemode will support zero ids situations.
Package: openerp-share
It specifically adds a ‘share’ button that is available in the Web client to
share any kind of OpenERP data with colleagues, customers, friends.The system will work by creating new users and groups on the fly, and by
combining the appropriate access rights and ir.rules to ensure that the shared
users only have access to the data that has been shared with them.This is extremely useful for collaborative work, knowledge sharing,
synchronization with other companies.
Package: openerp-stock
The warehouse and inventory management is based on a hierarchical location structure, from warehouses to storage bins.
The double entry inventory system allows you to manage customers, suppliers as well as manufacturing inventories.OpenERP has the capacity to manage lots and serial numbers ensuring compliance with the traceability requirements imposed by the majority of industries.Key FeaturesMoves history and planning,Stock valuation (standard or average price, …)Robustness faced with Inventory differencesAutomatic reordering rulesSupport for barcodesRapid detection of mistakes through double entry systemTraceability (Upstream / Downstream, Serial numbers, …)Dashboard / Reports for Warehouse Management will include:Incoming Products (Graph)Outgoing Products (Graph)Procurement in ExceptionInventory AnalysisLast Product InventoriesMoves Analysis
Package: openerp-stock-location
Typically this could be used to:Manage product manufacturing chainsManage default locations per productDefine routes within your warehouse according to business needs, such as:Quality ControlAfter Sales ServicesSupplier ReturnsHelp rental management, by generating automated return moves for rented productsOnce this module is installed, an additional tab appear on the product form,
where you can add Push and Pull flow specifications. The demo data of CPU1
product for that push/pull :Push flows:Push flows are useful when the arrival of certain products in a given location
should always be followed by a corresponding move to another location, optionally
after a certain delay. The original Warehouse application already supports such
Push flow specifications on the Locations themselves, but these cannot be
refined per-product.A push flow specification indicates which location is chained with which location,
and with what parameters. As soon as a given quantity of products is moved in the
source location, a chained move is automatically foreseen according to the
parameters set on the flow specification (destination location, delay, type of
move, journal). The new move can be automatically processed, or require a manual
confirmation, depending on the parameters.Pull flows:Pull flows are a bit different from Push flows, in the sense that they are not
related to the processing of product moves, but rather to the processing of
procurement orders. What is being pulled is a need, not directly products. A
classical example of Pull flow is when you have an Outlet company, with a parent
Company that is responsible for the supplies of the Outlet.[ Customer ] <- A - [ Outlet ]  <- B -  [ Holding ] <~ C ~ [ Supplier ]When a new procurement order (A, coming from the confirmation of a Sale Order
for example) arrives in the Outlet, it is converted into another procurement
(B, via a Pull flow of type ‘move’) requested from the Holding. When procurement
order B is processed by the Holding company, and if the product is out of stock,
it can be converted into a Purchase Order (C) from the Supplier (Pull flow of
type Purchase). The result is that the procurement order, the need, is pushed
all the way between the Customer and Supplier.Technically, Pull flows allow to process procurement orders differently, not
only depending on the product being considered, but also depending on which
location holds the ‘need’ for that product (i.e. the destination location of
that procurement order).Use-Case:You can use the demo data as follow:CPU1:Sell some CPU1 from Chicago Shop and run the schedulerWarehouse: delivery order, Chicago Shop: receptionCPU3:When receiving the product, it goes to Quality Control location then
stored to shelf 2.When delivering the customer: Pick List -> Packing -> Delivery Order from Gate A
Package: openerz-api
OpenERZ Python APIThis wrapper allows you to interact with the OpenERZ API using Python code.For more information about the API itself see:http://openerz.metaodi.ch/documentationandhttps://github.com/metaodi/openerzUsage exampleA ready-to-run example can also be found in theexamplesdirectory.from openerz_api.main import OpenERZConnector

ZIP = 8001
WASTE = "paper"

# initialize the connector given zip code and waste type
connector = OpenERZConnector(zip_code=ZIP, waste_type=WASTE)

# retrieve the next pick-up date within a period of choice
next_pickup = connector.find_next_pickup(day_offset=15)
Package: openet
This repository provides core functions used by the OpenET models.Core ComponentsCommonThe OpenET common module provides functions that are common across many of the OpenET models.  Currently these are limited to cloud masking functions but additional functions will be added as they are identified.Examples of the cloud masking functions are provided in the “examples” folder.Landsat Collection 1 TOA cloud maskLandsat Collection 1 SR cloud maskSentinel 2 TOA cloud maskInterpolationThe OpenET “interp” module provides functions for interpolating the image based ET estimates from the models (primarily from Landsat images) to a daily time step then aggregating to custom time periods (such as monthly or annual).InstallationThe OpenET core python module can be installed via pip:pip install openetDependenciesModules needed to run the model:earthengine-apiOpenET Namespace PackageEach OpenET model will be stored in subfolders of the “openet” folder (namespace).  The benefit of the namespace package is that each ET model can be tracked in separate repositories but called as a “dot” submodule of the main openet module,importopenet.core.commonimportopenet.core.interpimportopenet.ssebopDevelopment and TestingPlease see theCONTRIBUTING.rst.
Package: openet-client
See README athttps://github.com/water3d/openet/for more details. Make sure to install package extras (e.g. pip install ‘openet-client[spatial]’) for spatial data support in the geodatabase API. It depends on Geopandas, which depends on fiona - this can be challenging to get set up correctly, so it’s worth checking the documentation for those projects to install on your system, or use a conda environment and install the conda geopandas package.
Package: openet-core
WARNING: This code is in development, is being provided without support, and is subject to change at any time without notificationThis repository provides core functions used by the OpenET models.Core ComponentsCommonThe OpenET “common” module provides functions that are common across many of the OpenET models.  Currently these are limited to operations like cloud masking, but additional functions will be added as they are identified.Examples of the cloud masking functions are provided in the “examples” folder.Landsat Collection 2 SR cloud maskSentinel 2 TOA cloud maskInterpolationThe OpenET “interpolate” module provides functions for interpolating the image based ET estimates from the models (primarily from Landsat images) to a daily time step then aggregating to custom time periods (such as monthly or annual).EnsembleThe OpenET “ensemble” module provides the function used to calculate the OpenET ensemble median absolute deviation (mad).InstallationThe OpenET core python module can be installed via pip:pip install openet-coreDependenciesModules needed to run the model:earthengine-apiOpenET Namespace PackageEach OpenET model will be stored in sub-folders of the “openet” folder (namespace).  The benefit of the namespace package is that each ET model can be tracked in separate repositories but called as a “dot” submodule of the main openet module,importopenet.core.commonimportopenet.core.interpolateimportopenet.ssebopDevelopment and TestingPlease see theCONTRIBUTING.rst.
Package: openet-disalexi
This repository provides an Earth Engine Python API based implementation of the DisALEXI ET model.ExamplesJupyter notebooks are provided in the “examples” folder that show various approaches for calling the OpenET DisALEXI model.InstallationThe OpenET DisALEXI python module can be installed via pip:pip install openet-disalexiDependenciesModules needed to run the model:earthengine-apiopenetModules needed to run the test suite:pytestOpenET Namespace PackageEach OpenET model should be stored in the “openet” folder (namespace).  The benefit of the namespace package is that each ET model can be tracked in separate repositories but called as a “dot” submodule of the main openet module,import openet.disalexi as disalexiReferences[Anderson2007JGR]Anderson, M. C., J. M. Norman, J. R. Mecikalski, J. A. Otkin, and W. P. Kustas (2007), A climatological study of evapotranspiration and moisture stress across the continental United States based on thermal remote sensing: 1. Model formulation, J. Geophys. Res., 112, D10117, doi:10.1029/2006JD007506.
Package: openevsewifi
python-openevse-wifiA python library for communicating with the ESP8266- and ESP32-based wifi module from OpenEVSE.
This library uses RAPI commands over http to query the OpenEVSE charger.Currently only supports read-only functionality.InstallationThe easiest way of installing the latest stable version is with pip:pip install openevsewifiThis project uses poetry for dependency management and package publishing.  To install from source using poetry:poetry installIf you're not planning on doing any development on python-openevse-wifi itself, and you don't want to install poetry,
you can also use pip as of version 10.0.  From the root of this repo, run:pip install .DevelopmentTo set up a development environment, first install Poetry according to thedirections.
Then install the dependencies for this project:poetry installBefore opening a pull request, make sure all tests pass by runningpytest.
Package: openexchangerates
This is a simple python client implementation ofhttps://openexchangerates.orgweb services.Installopenexchangerates is avaiable on pypi repositories. Just simply install
by usingeasy_installorpip:$ pip install openexchangeratesUsageFirst of all, you have to sign up the service for an API key by visitinghttps://openexchangerates.orgThen it is a matter of cake to start using the service:>>> from openexchangerates import OpenExchangeRatesClient
>>> client = OpenExchangeRatesClient('<YOUR_API_KEY>')
>>> client.currencies()
{'AED': 'United Arab Emirates Dirham',
'AFN': 'Afghan Afghani',
'ALL': 'Albanian Lek',
'AMD': 'Armenian Dram',
'ANG': 'Netherlands Antillean Guilder',
'AOA': 'Angolan Kwanza',
'ARS': 'Argentine Peso',
'AUD': 'Australian Dollar',
...

>>> client.latest()
{'base': 'USD',
'disclaimer': '<disclaimer>',
'license': '<license>',
'rates': {'AED': 3.672701,
    'AFN': 51.621833,
    'ALL': 104.032,
    'AMD': 406.489997,
    'ANG': 1.7888,
    'AOA': 95.936967,
    'ARS': 4.995484,
    'AUD': 0.966637,
    ...You are also free to select base currency (Supported by non-free licenses):>>> client.latest(base='GBP')
{'base': 'GBP',
'disclaimer': '<disclaimer>',
'license': '<license>',
'rates': {'AED': 3.672701,
    'AFN': 51.621833,
    'ALL': 104.032,
    'AMD': 406.489997,
    'ANG': 1.7888,
    'AOA': 95.936967,
    'ARS': 4.995484,
    'AUD': 0.966637,
    ...