salure-helpers

Release 28.0.0

Files with helpful code, developed by Salure

Homepage Repository PyPI Python

License
curl
Install
pip install salure-helpers==28.0.0

Documentation

HOW TO USE THE PACKAGES

The packages repository contains all the helper files which are build for projects of Salure. Sometimes, code in a project could be useful for other projects and will be added to the packages repository. This readme describes the folder structure, the several packages and how to add new packages. The docs section contains a detailed description per package.

Directory structure

The directory structure in the packages is as follows:

  • The datasets directory contains some usefull datasets like countries with iso code, currencies, etc.;
  • The docs contain detailed documentation about server management, the packages itself, etc.;
  • The src folder contains the packages itself. The subdirectory connectors can be used for connectors between Profit and another system. The packages in the root of /src are usefull for a variety of tasks;

How to create an updated pip package

https://packaging.python.org/tutorials/packaging-projects/#uploading-your-project-to-pypi

How to ship changes

When you commit a change, take the following in mind. The versioning we use is called semantic versioning. More information can be found on https://semver.org/

Given a version number MAJOR.MINOR.PATCH, increment the:

    1. MAJOR version when you make incompatible API changes,
    2. MINOR version when you add functionality in a backwards-compatible manner, and
    3. PATCH version when you make backwards-compatible bug fixes.
  1. A normal version number MUST take the form X.Y.Z where X, Y, and Z are non-negative integers, and MUST NOT contain leading zeroes. X is the major version, Y is the minor version, and Z is the patch version. Each element MUST increase numerically. For instance: 1.9.0 -> 1.10.0 -> 1.11.0.
  2. Patch version Z (x.y.Z | x > 0) MUST be incremented if only backwards compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior.
  3. Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backwards compatible functionality is introduced to the public API. It MUST be incremented if any public API functionality is marked as deprecated. It MAY be incremented if substantial new functionality or improvements are introduced within the private code. It MAY include patch level changes. Patch version MUST be reset to 0 when minor version is incremented.
  4. Major version X (X.y.z | X > 0) MUST be incremented if any backwards incompatible changes are introduced to the public API. It MAY include minor and patch level changes. Patch and minor version MUST be reset to 0 when major version is incremented.

Changelog

See commit history

Stats

Dependencies
0
Dependent packages
0
Dependent repositories
0
Total releases
506
Latest release
First release
Forks
0
Watchers
2
Contributors
0
Repository size
1.24 MB
SourceRank
8

Development practices

Source repo 2FA enabled
TEXT!
Package manager 2FA enabled
TEXT!
Is security responsive
TEXT!
Dependencies are managed
TEXT!
Issue-free release available
TEXT!
Succession plan available
TEXT!
Package manager 2FA enabled
TEXT!

The Tidelift Subscription provides access to a continuously curated stream of human-researched and maintainer-verified data on open source packages and their licenses, releases, vulnerabilities, and development practices.

Learn more →

Releases

28.0.0
27.2.5
27.2.4
27.2.3
27.2.2
27.2.1
27.2.0
27.1.0
27.0.4
27.0.3
See all 506 releases

Something wrong with this page? Make a suggestion

Export .ABOUT file for this package

Last synced: 2023-09-25 12:36:00 UTC

Login to resync this project