You are here: Home

Modified items

All recently modified items, latest first.
RPMPackage python3-arcus-4.13.1-1.fc36.x86_64
Arcus Python 3 bindings for creating a socket in a thread and using this socket to send and receive messages based on the Protocol Buffers library. It is designed to facilitate the communication between Cura and its backend and similar code.
RPMPackage python3-appy-1.0.12-1.lbn36.noarch
Appy is the simpliest way to build complex webapps.
RPMPackage python3-appdirs-1.4.4-5.fc36.noarch
A small Python 3 module for determining appropriate " + " platform-specific directories, e.g. a "user data dir".
RPMPackage python3-ansicon-1.89.0-1.lbn36.noarch
.. start-badges| |appveyor| |codecov| | |pypi| |supported-versions| |supported- implementations|.. |appveyo .. |codeco .. |pyp :target:
RPMPackage python3-aniso8601-9.0.1-1.lbn36.noarch
aniso8601 Another ISO 8601 parser for Python -Features* Pure Python implementation * Logical behavior - Parse a time, get a datetime.time < - Parse a date, get a datetime.date < - Parse a datetime, get a datetime.datetime < - Parse a duration, get a datetime.timedelta < - Parse an interval, get a tuple of dates or datetimes
RPMPackage python3-alembic-1.13.2-5.lbn36.noarch
Alembic is a database migrations tool written by the author of SQLAlchemy. A migrations tool offers the following functionality: • Can emit ALTER statements to a database in order to change the structure of tables and other constructs • Provides a system whereby "migration scripts" may be constructed; each script indicates a particular series of steps that can "upgrade" a target database to a new version, and optionally a series of steps that can "downgrade" similarly, doing the same steps in reverse. • Allows the scripts to execute in some sequential manner. Documentation and status of Alembic is at https://alembic.sqlalchemy.org/
RPMPackage python3-alabaster-0.7.16-1.lbn36.noarch
What is Alabaster? Alabaster is a visually (c)lean, responsive, configurable theme for the Sphinx <>_ documentation system. It is Python 2+3 compatible.It began as a third-party theme, and is still maintained separately, but as of Sphinx 1.3, Alabaster is an install-time dependency of Sphinx and is selected as the default theme.Live examples of this theme can be seen on this project's own...
RPMPackage python3-aiosignal-1.2.0-3.fc36.noarch
A project to manage callbacks in asyncio projects.
RPMPackage python3-aiohttp-3.9.3-1.lbn36.x86_64
Python HTTP client/server for asyncio which supports both the client and the server side of the HTTP protocol, client and server websocket, and webservers with middlewares and pluggable routing.
RPMPackage python3-aiodns-3.2.0-1.lbn36.noarch
aiodns provides a simple way for doing asynchronous DNS resolutions with a synchronous looking interface by using pycares.
RPMPackage python3-abrt-container-addon-2.17.1-3.lbn36.noarch
This package contains python 3 hook and handling uncaught exception in python 3 programs in container.
RPMPackage python3-abrt-addon-2.17.1-3.lbn36.noarch
This package contains python 3 hook and python analyzer plugin for handling uncaught exception in python 3 programs.
RPMPackage python3-abrt-2.17.1-3.lbn36.x86_64
High-level API for querying, creating and manipulating problems handled by ABRT in Python 3.
RPMPackage python3-QtPy-2.0.0-2.fc36.noarch
QtPy (pronounced ‘cutie pie’) is a small abstraction layer that lets you write applications using a single API call to either PyQt or PySide. It provides support for PyQt5, PyQt4 and PySide using the PyQt5 layout (where the QtGui module has been split into QtGui and QtWidgets). Basically, you write your code as if you were using PyQt5 but import qt from qtpy instead of PyQt5.
RPMPackage python3-PyMySQL-1.0.3-2.lbn36.noarch
This package contains a pure-Python MySQL client library. The goal of PyMySQL is to be a drop-in replacement for MySQLdb and work on CPython, PyPy, IronPython and Jython.
RPMPackage python3-Cython-0.29.34-2.lbn36.x86_64
The Cython language makes writing C extensions for the Python language as easy as Python itself. Cython is a source code translator based on Pyrex, but supports more cutting edge functionality and optimizations. The Cython language is a superset of the Python language (almost all Python code is also valid Cython code), but Cython additionally supports optional static typing to natively call C functions, operate with C++ classes and declare fast C types on variables and class attributes. This allows the compiler to generate very efficient C code from Cython code. This makes Cython the ideal language for writing glue code for external C/C++ libraries, and for fast C modules that speed up the execution of Python code.
RPMPackage python3-CommonMark-0.9.1-8.fc36.noarch
Pure Python port of jgm’s stmd.js, a Markdown parser and renderer for the CommonMark specification, using only native modules. Once both this project and the CommonMark specification are stable we will release the first 1.0 version and attempt to keep up to date with changes in stmd.js. We are currently at the same development stage (actually a bit ahead because we have implemented HTML entity conversion and href URL escaping) as stmd.js. Since Python versions pre-3.4 use outdated (i.e. not HTML5 spec) entity conversion, I’ve converted the 3.4 implementation into a single file, entitytrans.py which so far seems to work (all tests pass on 2.7, 3.3, and 3.4).
RPMPackage python3-Bottleneck-1.3.7-3.lbn36.x86_64
python3-Bottleneck is a collection of fast NumPy array functions written in Cython.
RPMPackage python3-Authomatic-1.0.0-1.lbn36.noarch
.. |gae| replace:: Google App Engine .. _gae: |webapp2| replace:: Webapp2 .. _webapp2: |oauth2| replace:: OAuth 2.0 .. _oauth2: |oauth1| replace:: OAuth 1.0a .. _oauth1: |openid| replace:: OpenID .. _openid: |pyopenid| replace:: python- openid .. _pyopenid: Authomatic **Authomatic**
RPMPackage python3-APScheduler-3.9.1-1.lbn36.noarch
Advanced Python Scheduler (APScheduler) is a Python library that lets you schedule your Python code to be executed later, either just once or periodically. You can add new jobs or remove old ones on the fly as you please. If you store your jobs in a database, they will also survive scheduler restarts and maintain their state. When the scheduler is restarted, it will then run all the jobs it should have run while it was offline.