semvec/pypi-packages huggingface dataset:
tango-shared-core 1.5.0
Tango shared/core functionality.
License: MIT

Tango Shared Core
=====

Provides shared and core functionality used by multiple Tango apps,
and will be installed by them as needed.

[![Build Status](https://travis-ci.org/tBaxter/tango-shared-core.svg?branch=master)](https://travis-ci.org/tBaxter/tango-shared-core)

## So what's in here, anyway?

### Base models
Abstract base models are included for common content objects, including images, so you can handle common fields and needs quickly, easily and consistently.

### Useful settings
A lot of them. Seriously, take a look at the settings file.

### Template tags and filters
* Formatting helpers
* Simple (and non-tracking) social media links.
* Additional time output helpers

### A robust base template
Based on HTML5 Boilerplate, but for Django, and battle-tested.

### A administrator how-to section in the admin
You already have developer documentation in the admin. This gives you hooks to include documentation aimed at administrators as well, just by including a `how_to.md` file in your app. See the other Tango apps for examples.

### Middleware and Context Processors
* StripEmptyLines: Strips HTML output of excessive newlines
* CompactHTMLMiddleware: Pseudo-minification for HTML output, good for a 30-40% reduction in file size. Not entirely safe with `pre` tags. Use with caution.
* The site_processor context processor adds a bunch of useful things in context.

### Utils
* Robust user submission sanitization
* Map tools to ease Google Map integration (Note: You'll need to set `GMAP_KEY` in your settings)

### JS
* A solid implementation of Markitup

## Installation
Installation should be automatic, from the application needing it.

You can also install from pip or github.

If you run into appRegistry issues, be sure  `INSTALLED_APPS` contains
`easy_thumbnails` and  `django.contrib.contenttypes`.
mapping 0.1.6
Mappings for generic and tradeable futures instruments
License: MIT


`mapping` provides functionality for mapping to and from generic exposures and
tradeable instruments for financial assets.

An example of this might be on 2016-12-01 we would have `CL1 -> CLZ16`, i.e.
the first generic for Crude oil on the above date corresponds to trading the
December 2016 contract.

The main features of `mapping` include:

- creating continuous return series for Futures instruments
- creating time series of percentage allocations to tradeable contracts
- creating instrument trade lists