semvec/pypi-packages huggingface dataset:
genpars 20.3
general python parameter handling
Keywords: python parameters

# genpars

*genpars* is a python package used for general script and function parameters handling. It will read and write a "parameter file" which is used to save values between python sessions.  It will get and set parameters associated with any number of "callers" (scripts, functions, applications).  *genpars* can also handle prompting and defining defaults values for parameters. It is implemented as a single class *GenPars*.

## Documentation

See xxx

## Installation

pip install genpars

or download the latest version from github: https://github.com/mplesser/genpars.git.
transparencyEpias 0.0.3
Package for EPIAS (Turkish Electricity Market Operating Company) Transparency API Service
Requires Python: >=3

# transparencyEpias

[![PyPI Latest Release](https://img.shields.io/pypi/v/transparencyEpias.svg)](https://pypi.org/project/transparencyEpias/)

transparencyEpias is a package which consumes Epias Transparency Rest Web Services, mainly scopes to provide easy access to users public Turkish Electricity Market data.

# Covers

  - Consumption Data Services
  - Natural Gas Data Services
  - Market Data Services<br/>
    -Dayahead Market Data <br/>
    -Intraday Market Data <br/>
    -Balancing Power Market Data<br/>
    -Ancillary Services Data<br/>
 - Production Data Services<br/>
 - Tools (Which includes useful functions like exporting excel, creating basic report etc. )

### Installation

transparencyEpias requires python3 or latest versions to run.
Also following packages need to be installed. 
- pandas
- requests
- datetime
- json
- xlsxwriter

Install the dependencies and install transparencyEpias.

```python
$ python -m pip install transparencyEpias
```

### Sample Usage

To be able to reach file user should follow instructions below.
- MCP Values Example:
 
```python
from transparency_epias.markets import dayaheadClient 
```
```python
mcp_list = dayaheadClient.dayahead.mcp(startDate='2020-05-10',endDate='2020-05-10')[1]
```
```python
>>>[249.99, 322.22, 321.82, 321.81, 310.01, 214, 79.96, 14.04, 1, 0, 0, 0, 0.87, 1, 4, 13.99, 97.45, 227.57,

 299.99, 323.23, 321.85, 308.56, 289.8, 284.99]
```
- MCP Excel Export Example:
```python
from transparency_epias.tools import reportClient
```
```python
reportClient.reports.mcp_excel_export(startDate='2020-05-10',endDate='2020-05-10')
```
```python
>>> User should get an xlsx document includes daily MCP price values to the path that python runs.
```
- Simple Price Comparison Report Example:
```python
from transparency_epias.tools import reportClient
```
```python
reportClient.reports.compare_price()
```
```python
>>> User should get a xlsx document includes MCP, SMP, and Weighted Avarage Price 

values to the path that python runs.
```

License
----

MIT

Soruce
----

https://seffaflik.epias.com.tr/transparency/

https://seffaflik.epias.com.tr/transparency/technical/en/
falconify 0.1.1
The Scaffolding tool for Falconify
Requires Python: >=3.5, <4
Keywords: falconify tooling development framework falcon

The Scaffolding tool for Falconify.

This scaffolding tool includes a set of commands that allows you to bootstrap your modules following the suggested structure for the Falconify template.

Scaffold usage:  
Start a project: `falconify bootstrap`  
Boot a module: `falconify create-module Pricing or Pricing_Tier`

This will create:    

**Bridging:**    
* The Command Handler: - this will create a new directory under Application/Features and it will place the handler there. You don't need to modify anything here.  
  
**Port:**  
* The Request Handler: - this will create a new directory under Application/Infrastructure/Port/Request and it will place the handler there. You don't need to modify anything here.  
* The Router: - this will create a new file and add it to the Application/Infrastructure/Port/Request/. You don't need to modify anything here for your general CRUD.  
* The Transformer: - this will create a new transformer under Application/Infrastructure/Port/Transformer. You will need to modify this file to implement your contract.  
  
**Adapter**:  
* The Repository: - this will create a new file on Adapters/Repository. You will need to modify the methods (create / update) in this file to fulfil your data requirements  
  
**Domain:**  
* The Model: - this will create a new file on Domain/Model. You will need to model your object in this file.  
* The Use Case: - this will create a new file on Domain/UseCases. You don't need to do much in this file, unless you're doing something out of the normal CRUD. But yes, your business logic should be implemented here.  
Once all of this is done, you can implement your route on Application/Main.py, by:  
  
Importing your new route - found on Application/Infrastructure/Port/Request/Routes.py  
To invoke the route by: Routes().define(self)  
  
**You're ready to consume.**    
This does not cater for migration. Falconify currently uses alembic to manage the migrations.