semvec/pypi-packages huggingface dataset:
django-response-helpers 3.0.1
A helper application for working with Django Responses

Django Response Helpers

Just a few helpers to shortcut
 - rendering to templates (with ResponseContext)
 - rendering data to csv
 - rendering html to pdf

 ** NOTE **
 As of v. 1.0.8 Django 1.5 will be required to take advantage of the new StreamingHttpResponse
 Object used in the CSVResponse.
django-forms-ext 1.2.1
Extensions for Django's Forms.



These are extensions for Django's forms.

Currently this contains the following:

Fields
=========

- ForeignKeyChoiceField

    When you have a formset that has a foreign key, Django will
    fire off a new (identical) query to build the choices for
    that field for each form in the formset by default. Using this
    field will allow you to run the query once for the choices and
    re-use that queryset for each form in the formset.

- CommaSeparatedField

    Django has a comma separated integer field, but not just strings.
    Stupid, I know... we created one for use with strings

- QuerysetChoiceField

    When you want to build a select box with a queryset but don't want
    a model instance when saving, use this thing.

- USSocialSecurityNumberField

    Check that a field conforms to the US Social Security number format.
    Includes evaluation of invalid number ranges, and invalid pattern rules.
    Permits Lexis Nexis test SSNs.

Views
=========
- FormSetView

    Django 1.3's generic views do not include a FormSet view. That's
    what this is.
moodylang 0.1.0
A polite emotional programming language interpreter
Requires Python: >=3.7

# Moody , beg to compile your code! (or don't and watch the compiler cry)

**Moody* is a playful, tone-sensitive programming language that only compiles your code if you’re polite enough. It supports basic control structures, recursion, and even enforces good manners through tone analysis.


## ✅ Features

- Custom syntax influenced by JavaScript and Python.
- Mood-based keywords: Good, Neutral, Bad — each affects your "tone score".
- Will **refuse to compile** if you're rude, impolite, or forget to say `thanks`.
- Supports:
  - Variable declarations (`let`, `const`)
  - Functions (`beg def myFunc() { ... }`)
  - Conditionals (`listen if`)
  - Loops (`plead while`)
  - Recursion
  - Polite `return` statements (`request`)
  - Tone-based printing (`humblyRequest`, `send`, `handover`)
- Interactive Interpreter: `python moody.py -i`

---

## 💬 Tone Keywords

### Good (Boosts score, required):
- `beg`
- `prettyPlease`
- `plead`
- `request` → becomes `return`
- `thanks`
- `humblyRequest` → use before calling functions

Limit: 2 uses per keyword.

### Neutral (No impact, but limited):
- `hey`
- `sup`
- `listen`
- `yo`
- `btw`
- `proceed`
- `send` → `return' but neutral

Limit: 1 use per keyword.

### Bad (Reduces tone score):
- `youBetter`
- `dare`
- `threaten`
- `submit`
- `now`
- `handover` → `return` return but aggressive

Limit: 5 uses per keyword.

---

## ❗ Tone Rules

Your MoodyLang code **must**:
- Use **at least 3 good keywords**.
- Maintain a **minimum tone score of 6**.
- Include a **`thanks`** before finishing (Sort of like a return 0 in C++, don't use a semicolon in a thanks statement).

Violating these will result in:
- `FixYourAttitudeError`
- `CompilerIsCryingError`
- `GratitudeException`

Multiple errors can occur simultaneously.

---

## 📄 Example: Polite Search

```moody
beg def linearSearch(n) {
    yo let i = 0;
    plead while (i < len(arr)) {
        listen if (arr[i] == n) {
            request i;
        }
        plead i = i + 1;
    }
    beg request -1;
}

hey const arr = [1, 2, 3, 4];
humblyRequest print(linearSearch(3));
thanks