semvec/pypi-packages huggingface dataset:
vereqsyn 1.1
Bi-directional version.cfg <–> requirements.txt synchronization
Requires Python: >=3.11

# vereqsyn

[![Test](https://github.com/minddistrict/vereqsyn/actions/workflows/tests.yml/badge.svg)](https://github.com/minddistrict/vereqsyn/actions/workflows/tests.yml)
[![PyPI - Version](https://img.shields.io/pypi/v/vereqsyn.svg)](https://pypi.org/project/vereqsyn)
[![PyPI - Python Version](https://img.shields.io/pypi/pyversions/vereqsyn.svg)](https://pypi.org/project/vereqsyn)

Bi-directional versions.cfg <–> requirements.txt synchronization

The name ``vereqsyn`` stands for **ve**rsion.cfg **req**irements.txt **syn**chronization.

This program can be used to synchronize a `versions.cfg` used by
[zc.buildout](https://pypi.org/project/zc.buildout/) with a `requirements.txt`
as used by [pip](https://pypi.org/project/pip/).

This is be helpful to keep using `zc.buildout` but get version updates via
GitHub's Dependabot.

-----

**Table of Contents**

- [Installation](#installation)
- [Usage](#usage)
- [Constraints](#constraints)
- [Hacking](#hacking)
- [License](#license)

## Installation

```console
pip install vereqsyn
```

## Usage

```console
vereqsyn --help
vereqsyn versions.cfg requirements.txt
```

## Constraints

* `versions.cfg` is the source of truth. `requirements.txt` can get recreated.
* So `versions.cfg` can contain comments, the ones in `requirements.txt` are
  lost when running recreate.

## Hacking

### Run the tests

```console
hatch run cov
```

### Run the code formatter

To lint the code:

```console
hatch fmt
```

To format the code:

```console
hatch fmt -f
```

### Cut a release

* Update release date in `Changes.md`.

* `hatch build`

* ```console
  cd dist
  twine upload -r pypi
  rm vereqsyn-*
  ```
* `hatch version <new version number>`

* Update `Changes.md`: Enter new version as unreleased.

## License

`vereqsyn` is distributed under the terms of the [MIT](https://spdx.org/licenses/MIT.html) license.
moz-fluent-linter 0.4.9
Linter package used to check Fluent files
Requires Python: >=3.7

# Fluent Linter

[![PyPI version](https://badge.fury.io/py/moz-fluent-linter.svg)](https://badge.fury.io/py/moz-fluent-linter)

[![Unit Tests](https://github.com/mozilla-l10n/moz-fluent-linter/actions/workflows/tests.yml/badge.svg)](https://github.com/mozilla-l10n/moz-fluent-linter/actions/workflows/tests.yml)

This script is largely based on the Fluent Linter [used in mozilla-central](https://firefox-source-docs.mozilla.org/code-quality/lint/linters/fluent-lint.html) for Firefox localization.

It allows to check reference FTL files for common issues:
* Identifiers too short
* Invalid characters available used in identifiers
* Use of incorrect characters (e.g. `'` instead of `’`)

It also allows to limit the range of features supported, for example disabling attributes or variants.

## Version control integration

Using [pre-commit](https://pre-commit.com/), add this to the `.pre-commit-config.yaml` in your repository:

```yaml
repos:
  - repo: https://github.com/mozilla-l10n/moz-fluent-linter
    rev: v0.4.9
    hooks:
      - id: fluent_linter
        files: \.ftl$
        args: [--config, l10n/linter_config.yml, l10n/en/]
```

This is just an example to get you started, you may need to update the `rev` and `args` depending on your specific needs and configuration.