semvec/pypi-packages huggingface dataset:
backbuilder 0.1.1
A Python CLI application that effortlessly facilitates the creation of backend projects via the command line.

BackBuilder.py 
=============


Description
-----------

I have developed a Python CLI application that effortlessly facilitates the creation of backend projects via the command line. This solution addresses the inherent complexities associated with building backend projects from scratch, providing users with an unparalleled level of ease and efficiency.

Features
--------

-   Easy and quick creation of Flask projects
-   Automatic project structure setup
-   Simplified setup for common Flask configurations

More information soon.
uiclasses 3.0.0
Data-Modeling for User Interfaces
Requires Python: >=3.6

UIClasses - Data-Modeling for User Interfaces
##############################################


.. image:: https://img.shields.io/pypi/dm/uiclasses
   :target: https://pypi.org/project/uiclasses

.. image:: https://img.shields.io/codecov/c/github/gabrielfalcao/uiclasses
   :target: https://codecov.io/gh/gabrielfalcao/uiclasses

.. image:: https://github.com/gabrielfalcao/uiclasses/actions/workflows/main.yml/badge.svg
   :target: https://github.com/gabrielfalcao/uiclasses/actions/workflows/main.yml

.. image:: https://img.shields.io/readthedocs/uiclasses
   :target: https://uiclasses.readthedocs.io/

.. image:: https://img.shields.io/github/license/gabrielfalcao/uiclasses?label=Github%20License
   :target: https://github.com/gabrielfalcao/uiclasses/blob/master/LICENSE

.. image:: https://img.shields.io/pypi/v/uiclasses
   :target: https://pypi.org/project/uiclasses

.. image:: https://img.shields.io/pypi/l/uiclasses?label=PyPi%20License
   :target: https://pypi.org/project/uiclasses

.. image:: https://img.shields.io/pypi/format/uiclasses
   :target: https://pypi.org/project/uiclasses

.. image:: https://img.shields.io/pypi/status/uiclasses
   :target: https://pypi.org/project/uiclasses

.. image:: https://img.shields.io/pypi/pyversions/uiclasses
   :target: https://pypi.org/project/uiclasses

.. image:: https://img.shields.io/pypi/implementation/uiclasses
   :target: https://pypi.org/project/uiclasses

.. image:: https://img.shields.io/snyk/vulnerabilities/github/gabrielfalcao/uiclasses
   :target: https://github.com/gabrielfalcao/uiclasses/network/alerts

.. image:: https://img.shields.io/github/v/tag/gabrielfalcao/uiclasses
   :target: https://github.com/gabrielfalcao/uiclasses/releases

- Powered by `Python 3 Data Classes <https://docs.python.org/3/library/dataclasses.html>`_.
- Objects optimized for user interfaces.
- Methods to traverse nested dicts, convert to and from json
- ModelList and ModelSet collections for robust manipulation of collections of models.
- No I/O happens in models.
- Collections can be easily cached to leverage responsive user interfaces.



Installation
============


.. code:: bash

   pip install uiclasses


Basic Usage
===========

.. code:: python

   from uiclasses import Model


   class BlogPost(Model):
       id: int
       title: str
       body: str


   post1 = BlogPost({"id": 1, "title": "title 1", "body": "body 1", "wimsical_extra_field": "lala land"})
   post2 = BlogPost(id=2, title="title 2", body="body 2", extradata='stored but invisible')

   published = BlogPost.List([post1, post2])

   print(published.format_pretty_table())


.. image:: https://github.com/gabrielfalcao/uiclasses/raw/master/docs/source/_static/screenshot-blog-list-pretty-table.png


.. code:: python

   print(published.format_robust_table())

.. image:: https://github.com/gabrielfalcao/uiclasses/raw/master/docs/source/_static/screenshot-blog-list-robust-table.png



Notes:
======


- This is not designed to be fast, when adding data to models their
  types might cast and validated, which is costly.
  - filtering collections by string values cause glob match
polyglot-piranha-playground 0.0.3
A playground for Piranha
Requires Python: >=3.9

# PiranhaAgent

PiranhaAgent uses a static inference algorithm and OpenAI's GPT-4 model to generate human-like piranha rules from code examples.
It generates these rules in TOML format, which can be applied to refactor other parts of the codebase.


## Install

To get started with PiranhaAgent, follow these instructions:

```
pip install polyglot-piranha-playground
```

## Usage (Playground UI)

To run the playground:

```
piranha-playground
```

To define your transformation rules, you will need to provide pairs of code snippets: 'before' and 'after' transformation. Each piece of code that needs transformation should be marked by unique identifiers surrounded by comments (like `// 1`, `// 2`, etc.). These identifiers serve two purposes:

1. They denote which part of the code should be transformed.
2. They define the transformation sequence, or cascading, i.e., which transformations should follow which.

### Example

Consider the following code snippet:

#### Code before refactoring:

```java
class SomeClass {
  // 1 -> 2

  // 1
  void someMethod(String arg) {

  }
  // end

  void otherMethod() {
    String x;
    // 2
   	someMethod(x);
    // end
  }
}
```

#### Code after refactoring:

```java
class SomeClass {
  // 1 -> 2

  // 1
  public String someMethod() {

  }
  // end

  void otherMethod() {
    String x;
    // 2
    x = someMethod();
    // end
  }
}
```

In this example, there are two transformation points, marked by the identifiers `// 1` and `// 2`.

- `// 1` shows the transformation from `void someMethod(String arg)` to `public String someMethod()`.
- `// 2` shows the transformation from `someMethod(x)` to `x = someMethod()`.

The arrow notation `// 1 -> 2` indicates the transformation cascade, i.e., transformation `// 2` should be applied after transformation `// 1`.

Each transformation snippet begins with the identifier (like `// 1`) and ends with a `// end` comment.

This way of representing transformations helps to create clear, concise, and human-friendly refactoring rules, making it easier to manage and understand your transformations.

Make sure to follow these conventions when inputting your code for refactoring. Happy coding!

**Note: The code before and after must be syntactically correct, and it should parse. Moreover, after applying the rules to code before, the refactored code should match the code after. (spaces are ignored).**