semvec/pypi-packages huggingface dataset:
jamz 1.2.1
Renames music files based on their tags
License: MIT
Requires Python: >=3.9,<4.0

# Jamz

Jamz is a small command-line utility for renaming music files based on their tags.

For example, if you run:

`jamz ~/Music/Nirvana/Nevermind/ '{jamz_padded_tracknumber} - {title}.flac'`

Your Nevermind songs will now be named:

```txt
01 - Smells Like Teen Spirit.flac
02 - In Bloom.flac
03 - Come as You Are.flac
...
12 - Something in the Way / Endless, Nameless.flac
```

## Installation

`pip install jamz`

## Usage

Jamz takes two positional arguments, the directory to rename files in, and the template with which to rename them.
For the template, Jamz passes all the tags from each file as formatting arguments, so you can use any tag in your template that the filetype supports.
For example, when working with files that use the Vorbis comment format (FLAC, Ogg, etc.), you can use TITLE, ALBUM, DATE, etc. in your template.

`jamz /mymusic/ '{ARTIST} - {TITLE} - {TRACKNUMBER}.ogg'`

(Note: for this format specifically, jamz also supports using the lowercase version of each tag, e.g. "title")

### Special Tags

Jamz also adds a few special tags of its own. Every Jamz special tag starts with `jamz`.

`jamz_padded_tracknumber`: The tracknumber (if found) padded to two digits (e.g. `2` -> `02`)

`jamz_original_suffix`: The original suffix of the file, e.g. `.flac` if the file is named `song.flac`.

### Flags

```txt
-r, --recursive      Recursively descend the file tree
-d, --dry-run        Print the new names of the files, but don't actually rename them
-i, --ignore-errors  Skip over files that lead to errors
-v, --verbose        Enable verbose logging
```

## Technical Details

Jamz uses [Mutagen](https://mutagen.readthedocs.io/en/latest/) to read tags.
All non-special tags available for use in templates come from the Mutagen tags object.
Because Mutagen supports multiple tags per key, Jamz assumes the first value is canonical, and passes only that one to the template.
django-frontend-settings 2.0.0
Expose feature flags and settings from django waffle and django constance in an endpoint.
License: MIT
Requires Python: >=3.6

Frontend Settings
=================

Abstract
--------

This project provides an API that expose settings and feature flags for the frontend.

It uses `django-drf` to create an endpoint to expose flags and settings configured in `django-waffle` and `django-constance`



Usage
-----

Requirements
Python (3.6, 3.7, 3.8, 3.9)
Django (2.2, 3.0, 3.1, 3.2)

Installation
~~~~~~~~~~~~
Install using pip:

.. code::

    pip install django-frontend-settings

Add 'frontend-settings' to your INSTALLED_APPS setting.

.. code:: python

    INSTALLED_APPS = [
        ...
        'frontend_settings',
    ]

Expose the view in your urls:

.. code:: python

    from frontend_settings.views import settings as frontend_settings_view

    url(r"^frontend-settings/", frontend_settings_view, name="frontend-settings"),


Then your flags from waffle and setting from constance should be returned on a get in this route:


.. code::

    $ curl 'http://localhost:8000/frontend-settings/'
    {"data":{"flags":{"MY_FEATURE_FLAG":true},"settings":{}}}


In that case I had `FRONTEND_MY_FEATURE_FLAG` flag in waffle.
The default prefix for flags is `FRONTEND_`, if you like to change it you can do by changing the following config on settings.py:

.. code:: python

    FRONTEND_SETTINGS = {
        "WAFFLE_FLAG_PREFIX": "FRONTEND_", # Prefix used to filter out the flag that should be exposed in the endpoint
        "CONSTANCE_KEY_PREFIX": "FRONTEND_", # Prefix used to filter out the settings in constance
    }