semvec/pypi-packages huggingface dataset:
mehak 0.0.1
A small example package
Requires Python: >=3.6


# Make sure you have upgraded version of pip
Windows
```
py -m pip install --upgrade pip
```

Linux/MAC OS
```
python3 -m pip install --upgrade pip
```

## Create a project with the following structure
```
packaging_tutorial/
├── LICENSE
├── pyproject.toml
├── README.md
├── setup.cfg
├── src/
│   └── example_package/
│       ├── __init__.py
│       └── example.py
└── tests/
touch LICENSE
touch pyproject.toml
touch setup.cfg
mkdir src/mypackage
touch src/mypackage/__init__.py
touch src/mypackage/main.py
mkdir tests
```

## pyproject.toml 

This file tells tools like pip and build how to create your project

```
[build-system]
requires = [
    "setuptools>=42",
    "wheel"
]
build-backend = "setuptools.build_meta"
```
build-system.requires gives a list of packages that are needed to build your package. Listing something here will only make it available during the build, not after it is installed.

build-system.build-backend is the name of Python object that will be used to perform the build. If you were to use a different build system, such as flit or poetry, those would go here, and the configuration details would be completely different than the setuptools configuration described below.


# Setup.cfg setup
Using setup.cfg is a best practice, but you could have a dynamic setup file using setup.py

```
[metadata]
name = example-pkg-YOUR-USERNAME-HERE
version = 0.0.1
author = Example Author
author_email = author@example.com
description = A small example package
long_description = file: README.md
long_description_content_type = text/markdown
url = https://github.com/pypa/sampleproject
project_urls =
    Bug Tracker = https://github.com/pypa/sampleproject/issues
classifiers =
    Programming Language :: Python :: 3
    License :: OSI Approved :: MIT License
    Operating System :: OS Independent

[options]
package_dir =
    = src
packages = find:
python_requires = >=3.6

[options.packages.find]
where = src

```
# Running the build
### Make sure your build tool is up to date
Windows
```
py -m pip install --upgrade build
```
Linux/MAC OS
```
python3 -m pip install --upgrade build
```


### Create the build
```
py -m build
```













### References
https://packaging.python.org/tutorials/packaging-projects/
fixkit 0.0.1
PyRep is a collection of automatic program repair approaches in and for Python.
Requires Python: >=3.11

# FixKit

[![Python Version](https://img.shields.io/pypi/pyversions/fixkit)](https://pypi.org/project/fixkit/)
[![GitHub release](https://img.shields.io/github/v/release/smythi93/fixkit)](https://img.shields.io/github/v/release/smythi93/fixkit)
[![PyPI](https://img.shields.io/pypi/v/fixkit)](https://pypi.org/project/fixkit/)
[![Build Status](https://img.shields.io/github/actions/workflow/status/smythi93/fixkit/test-fixkit.yml?branch=main)](https://img.shields.io/github/actions/workflow/status/smythi93/fixkit/test-fixkit.yml?branch=main)
[![Coverage Status](https://coveralls.io/repos/github/smythi93/fixkit/badge.svg?branch=main)](https://coveralls.io/github/smythi93/fixkit?branch=main)
[![Licence](https://img.shields.io/github/license/smythi93/fixkit)](https://img.shields.io/github/license/smythi93/fixkit)
[![Code style: black](https://img.shields.io/badge/code%20style-black-000000.svg)](https://github.com/psf/black)

FixKit is a collection of various automated program repair approaches and techniques. 
It is designed to be a flexible and extensible framework for experimenting with different repair strategies. 
The framework is written in Python for Python and is designed to be easy to use and extend.

## Installation

To install FixKit, simply get the package from PyPI:

```bash
pip install fixkit
```

To install the latest version from the repository, use:

```bash
pip install git+https://github.com/smythi93/fixkit.git
```

## Usage

FixKit is a library and can be used directly in your Python code.

```python
from fixkit.repair.pygenprog import PyGenProg
from fixkit.localization.coverage import CoverageLocalization

repair = PyGenProg.from_source(
  src= "subjects/middle",
  excludes=["tests.py"],
  localization=CoverageLocalization(
    "subjects/middle",
    cov="middle",
    metric="Ochiai",
    tests=["tests.py"],
  ),
  population_size=40,
  max_generations=10,
)
patches = repair.repair()
```

## Components

Individual components can be swapped out and replaced with custom implementations.
The following components are currently available:

- **Fault Localization**: Determines the location of the fault in the source code.
- **Repair Approach**: Generates patches to fix the fault in the source code.
- **Search Strategy**: Searches for patches in the search space.
- **Fitness Function**: Evaluates the fitness of patches based on a given metric.
- **Selection Strategy**: Selects patches for the next generation based on their fitness.
- **Crossover Strategy**: Combines patches to create new patches.
- **Mutation Operators**: Mutates patches to create new patches.
- **Minimization Strategy**: Minimizes patches to reduce their size.