You are here: Home

Modified items

All recently modified items, latest first.
RPMPackage python3-hatch-vcs-0.4.0-1.lbn36.noarch
This provides a plugin for Hatch that uses your preferred version control system (like Git) to determine project versions.
RPMPackage python3-hatch-requirements-txt-0.4.1-1.lbn36.noarch
Hatchling plugin to read project dependencies from requirements.txt Tests PyPI Anaconda Activity QA Other Installation hatch-requirements-txt can be installed from PyPI or Anaconda. To install with pip: $ python -m pip install hatch-requirements-txt To install with conda: First add the required channels $ conda config --add channels https:/conda.anaconda.org/conda-forge Then install $ conda install hatch-requirements-txt Usage In your pyproject.toml make the following changes: Append hatch-requirements-txt to build-system.requires. Append dependencies to project.dynamic. Add the following table: [tool.hatch.metadata.hooks.requirements_txt] files = ["requirements.txt"] Optionally, you can also define groups of optional dependencies (also known as “features”) by appending optional-dependencies to project.dynamic and adding a table like: [tool.hatch.metadata.hooks.requirements_txt.optional-dependencies] crypto = ["requirements-crypto.txt"] fast
RPMPackage python3-hatch-nodejs-version-0.3.2-1.lbn36.noarch
hatch-nodejs-version This package provides two Hatch plugins: version source plugin that reads/writes the package version from the version field of the Node.js package.json file. metadata hook plugin that reads PEP 621 metadata from the Node.js package.json file. Table of Contents Installation Global dependency Version source Metadata hook License Global dependency Ensure hatch-nodejs-version is defined within the build-system.requires field in your pyproject.toml file. [build-system] requires = ["hatchling", "hatch-nodejs-version"] build-backend = "hatchling.build" Version source The version source plugin name is nodejs. pyproject.toml [tool.hatch.version] source = "nodejs" hatch.toml [version] source = "nodejs" Semver The semver specification defines the following version sections: major minor patch pre-release build Meanwhile, PEP 440 defines: epoch major minor patch pre-release post-release dev-release In order to ensure round-trip support, and ensure semantic
RPMPackage python3-gremlinpython-3.6.1-1.lbn36.noarch
.. Licensed to the Apache Software Foundation (ASF) under one .. or more contributor license agreements. See the NOTICE file .. distributed with this work for additional information .. regarding copyright ownership. The ASF licenses this file .. to you under the Apache License, Version 2.0 (the .. "License"); you may not use this file except in compliance .. with the License. You may obtain a...
RPMPackage python3-gevent-websocket-0.10.1-1.lbn36.noarch
gevent-websocket gevent-websocket_ is a WebSocket library for the gevent_ networking library.Features include:- Integration on both socket level or using an abstract interface. - RPC and PubSub framework using WAMP_ (WebSocket Application Messaging Protocol). - Easily extendible using a simple WebSocket protocol plugin API from geventwebsocket import WebSocketServer, WebSocketApplication,...
RPMPackage python3-geomet-0.3.0-4.fc36.noarch
Convert GeoJSON to WKT/WKB (Well-Known Text/Binary), and vice versa.
RPMPackage python3-funcparserlib-1.0.0a0-2.prerelease.fc36.noarch
Parser combinators are just higher-order functions that take parsers as their arguments and return them as result values. Parser combinators are: * First-class values * Extremely composable * Tend to make the code quite compact * Resemble the readable notation of xBNF grammars Parsers made with funcparserlib are pure-Python LL(*) parsers. It means that it's very easy to write them without thinking about look-aheads and all that hardcore parsing stuff. But the recursive descent parsing is a rather slow method compared to LL(k) or LR(k) algorithms. So the primary domain for funcparserlib is parsing little languages or external DSLs (domain specific languages).
RPMPackage python3-flit-3.8.0-1.lbn36.noarch
Flit is a simple way to put Python packages and modules on PyPI. It tries to require less thought about packaging and help you avoid common mistakes. See Why use Flit? for more about how it compares to other Python packaging tools. Install $ python3 -m pip install flit Flit requires Python 3 and therefore needs to be installed using the Python 3 version of pip. Python 2 modules can be distributed using Flit, but need to be importable on Python 3 without errors. Usage Say you’re writing a module foobar — either as a single file foobar.py, or as a directory — and you want to distribute it. Make sure that foobar’s docstring starts with a one-line summary of what the module is, and that it has a __version__: """An amazing sample package!""" __version__ = "0.1" Install flit if you don’t already have it: python3 -m pip install flit Run flit init in the directory containing the module to create a pyproject.toml file. It will look something like this: [build-system] requires = ["flit_co
RPMPackage python3-flask-sockets-0.2.1-1.lbn36.noarch
Flask-Sockets -Elegant WebSockets for your Flask apps.
RPMPackage python3-jsonpointer-2.0-5.fc36.noarch
Library to resolve JSON Pointers according to RFC 6901.
RPMPackage python3-pystemd-0.13.2-1.lbn36.x86_64
This library allows you to talk to systemd over D-Bus from Python, without actually thinking that you are talking to systemd over D-Bus. This allows you to programmatically start/stop/restart/kill and verify service status from systemd point of view, avoiding subprocessing systemctl and then parsing the output to know the result.
RPMPackage rubygem-http-cookie-1.0.5-1.lbn36.noarch
HTTP::Cookie is a Ruby library to handle HTTP Cookies based on RFC 6265. It has with security, standards compliance and compatibility in mind, to behave just the same as today's major web browsers. It has builtin support for the legacy cookies.txt and the latest cookies.sqlite formats of Mozilla Firefox, and its modular API makes it easy to add support for a new backend store.
RPMPackage rubygem-http-accept-2.1.1-6.fc36.noarch
Parse Accept and Accept-Language HTTP headers.
RPMPackage python3-lbn-cloud-init-1.3.3-1.lbn36.noarch
Sets up DC based upon cloud account number; so service discovery can happen across your entire cloud infrastructure. Password reset tools for Marketplace/Products shipped with BastionLinux
RPMPackage rubygem-iniparse-doc-1.5.0-1.lbn36.noarch
Documentation for rubygem-iniparse.
RPMPackage rubygem-iniparse-1.5.0-1.lbn36.noarch
A pure Ruby library for parsing INI documents. Preserves the structure of the original document, including whitespace and comments.
RPMPackage rubygem-inifile-doc-3.0.0-2.lbn36.noarch
Documentation for rubygem-inifile.
RPMPackage rubygem-inifile-3.0.0-2.lbn36.noarch
Although made popular by Windows, INI files can be used on any system thanks to their flexibility. They allow a program to store configuration data, which can then be easily parsed and changed. Two notable systems that use the INI format are Samba and Trac. More information about INI files can be found on the [Wikipedia Page](http://en.wikipedia.org/wiki/INI_file). The basic element contained in an INI file is the property. Every property has a name and a value, delimited by an equals sign *=*. The name appears to the left of the equals sign and the value to the right. name=value Section declarations start with *[* and end with *]* as in `[section1]` and `[section2]` shown in the example below. The section declaration marks the beginning of a section. All properties after the section declaration will be associated with that section. All lines beginning with a semicolon *;* or a number sign *#* are considered to be comments. Comment lines are ignored when parsing INI files. A typical INI file might look like this: [section1] ; some comment on section1 var1 = foo var2 = doodle var3 = multiline values \ are also possible [section2] var1 = baz var2 = shoodle.
RPMPackage rubygem-httpclient-2.8.3-6.fc36.noarch
an interface to HTTP Client for the ruby language
RPMPackage rubygem-highline-doc-2.0.3-1.lbn36.noarch
Documentation for rubygem-highline.