semvec/pypi-packages huggingface dataset:
coscmd 1.9.0.6
simple command for cos
License: MIT
Requires Python: >=2.7

COSCMD
#######################

.. image:: https://img.shields.io/pypi/v/coscmd.svg
      :target: https://pypi.org/search/?q=coscmd
   :alt: Pypi
.. image:: https://travis-ci.org/tencentyun/coscmd.svg?branch=master
      :target: https://travis-ci.org/tencentyun/coscmd
   :alt: Travis CI 

介绍
_______

腾讯云COS命令行工具, 最新版本支持Python3.x, 1.8.x版本支持Python2.6/Python2.7。

安装指南
__________

使用pip安装 ::

    pip install -U coscmd

手动安装::

    python setup.py install

使用方法
__________

使用coscmd，参照 https://cloud.tencent.com/document/product/436/10976
drf-madprops 1.2.0
DRF library to operate resource's properties as a dictionary
License: MIT

# drf-madprops [![Build Status](https://travis-ci.com/yola/drf-madprops.svg?branch=master)](https://travis-ci.com/yola/drf-madprops)

DRF library of helpers to operate on lists of resource properties as dicts

Written and used by the folks at Yola to support our [free website builder][1].

## Overview

It's a typical case for relational DBs when some table (e.g. User) is
extended via subordinate key-value table (e.g. UserPreference). This allows
to dynamically add/delete fields to User (stored in UserPreference).
Usually those property models have very simple structures, e.g:

```python
class UserPreference(models.Model):
    id = models.AutoField()
    user = models.ForeignKey(User, related_name='preferences')
    name = models.CharField()
    value = models.CharField)
```

But it's not very convenient to expose/operate on them via standard DRF
serializers.  We'll get something like:

```json
[
    {"id": "id1", "user": "user1", "name": "property1", "value": "value1"},
    {"id": "id2", "user": "user1", "name": "property2", "value": "value2"}
    ...
]
```

This library contains two base classes for property's serializers (for cases
when properties are exposed as separate resource and as nested resource) which
allows to retrieve/operate on parent resource properties as dicts. For example,
instead of representation listed above, we'll get something like:

```json
{
    "property1": "value1",
    "property2": "value2",
    ...
}
```

## Usage

### Additional meta options

- `read_only_props`: list of property names, which values cannot be changed
  via serializer.
- `json_props`: list of property names, which values are stored as JSON.
  Serializer will `json.loads()` those values when converting to representation
  and will `json.dumps()` them before saving.

### As a nested serializer

```python
from madprops.serializers import NestedPropertySerializer, PropertiesOwnerSerializer


class PreferenceSerializer(NestedPropertySerializer):
    class Meta:
        model = Preference
        read_only_props = ('user_token', 'tutorial_email_sent')
        json_props = ('packages',)


class UserSerializer(PropertiesOwnerSerializer):
    preferences = PreferenceSerializer(many=True, required=False)
```

### As a serializer used for properties endpoint
```python
from madprops.serializers import PropertySerializer


class PreferenceSerializer(PropertySerializer):
    class Meta:
        model = Preference
        read_only_props = ('user_token', 'tutorial_email_sent')


class PreferencePrivateViewSet(ModelViewSet):
    serializer_class = PreferenceSerializer
    paginate_by = None
```

## Testing

Run the tests with:

    tox

Or install development requirements and run tests with:

    pip install -r requirements.txt
    pytest tests


[1]:https://www.yola.com/