semvec/pypi-packages huggingface dataset:
gae-app-settings 1.1.1
Provides a key/value store in Google App Engine for sensitive data.
License: MIT License

# Google AppEngine App Settings

This package provies a straightforward way to store and access environment-specific and secret/private variables in the Google App Engine Datastore.


## Quick start

Install `gae_app_settings`:

```bash
$ pip install gae_app_settings
```

In your settings module or some other module that loads at startup:

```python
from gae_app_settings import AppSetting
value = AppSetting.get('MY_SETTING_KEY', DEFAULT_VALUE)
```



## Full documentation

AppSetting is a class that is used to persist/store sensitive values in your environment. It is designed to work just like a dictionary, but it is limited to just string values.

Settings cannot be set programmatically, they are only retrievable:

```python
value = AppSetting.get('MY_SETTING_KEY', DEFAULT_VALUE)
```

**NOTE:** regardless of the type of `DEFAULT_VALUE `, `value` will always be a string. This is to ensure that the return value is of the same type whether the setting is set or unset, as a set value will be a string.

You can also retrieve values without passing a default:

```python
value = AppSetting.get('MY_SETTING_KEY')
```

**Note:** If no default value is provided and the key has not been given a value in the datastore, the `get()` call will raise a `KeyError` and a placeholder entry will be created in the datastore. Once the placeholder has been replaced with a value future calls to `get()` will succeed.


## Best practices

The following best practices are recommended:

1. Settings should be loaded at program start and stored locally in a `settings.py` or similar module
1. Default values should be provided for every setting:
    1. these should be the values that make sense when running/testing locally
    1. placeholders will be inserted into the Datastore, and these only need to be overwritten if there are environment-specific settings that need to be set (in production, all values should be set)
1. Do not change the type of the `value` property in the datastore; coersion should happen on the result of the call to `get()`
digole 0.0.5
Digole LCD Drivers
License: MIT License

Digole LCD Driver

Tested with Digole 160x128 Color LCD 1.8" DSDM/Serial

Raspberry Pi 3 B using the i2c bus

Examples at www.github.com/jethornton/digole

Installing ```pip3 install digole```

Upgrade ```pip3 install digole --upgrade```

Or ```pip3 install --no-cache-dir digole --upgrade```

Importing ```from digole import lcd```

Create a new instance and use the default i2c address of 0x27 ```s = lcd()```

Create a new instance and use a different i2c address ```s = lcd(0x29)```

clear the screen ```s.clearScreen()```

write a line of text ```s.writeLine('Text to write')```

change X start position from the left edge in columns```s.changePosition(x)```

change XY start position of the text from the top left corner in columns, rows
```s.changePosition(x,y)```

```s.changePosition(0,2) # start the text on column 0 row 2```

Change Foreground Color color value 0-255 ```s.changeForeColor(color)```
color can be an int 0-255, a hex 0x0-0x255 or a color name from the chart.

	Black   =   0 = 0x0
	Navy    =   2 = 0x2
	Blue    =   3 = 0x3
	Green   =  24 = 0x18
	Teal    =  27 = 0x1B
	Lime    =  28 = 0x1C
	Aqua    =  31 = 0x1F
	Maroon  = 192 = 0xC0
	Purple  = 195 = 0xC3
	Olive   = 219 = 0xDB
	Red     = 224 = 0xE0
	Magenta = 227 = 0xE3
	Yellow  = 252 = 0xFC
	White   = 255 = 0xFF