Modified items

All recently modified items, latest first.

python3-jupyter-sphinx-0.3.2-3.fc36.noarch: Jupyter-Sphinx enables running code embedded in Sphinx documentation and embedding output of that code into the resulting document. It has support for rich output such as images and even Jupyter interactive widgets.

python3-jupyter-polymake-0.16-18.20180129.7049940.fc36.noarch: This package contains a Jupyter kernel for polymake.

python3-jupyter-kernel-singular-0.9.9-8.fc36.noarch: This package contains a Jupyter kernel for Singular, to enable using Jupyter as the front end for Singular.

python3-jupyter-console-6.6.3-1.lbn36.noarch: Jupyter Console A terminal-based console frontend for Jupyter kernels. This code is based on the single-process IPython terminal. Install with pip: pip install jupyter-console Install with conda: conda install -c conda-forge jupyter_console Start: jupyter console Help: jupyter console -h Jupyter Console allows for console-based interaction with non-python Jupyter kernels such as IJulia, IRKernel. To start the console with a particular kernel, ask for it by name:: jupyter console --kernel=julia-0.4 A list of available kernels can be seen with:: jupyter kernelspec list Release build: $ pip install pep517 $ python -m pep517.build . Resources Project Jupyter website Documentation for Jupyter Console [PDF] Documentation for Project Jupyter [PDF] Issues Technical support - Jupyter Google Group About the Jupyter Development Team The Jupyter Development Team is the set of all contributors to the Jupyter project. This includes all of the Jupyter subprojects. The core team that coordi

python3-jupyter-console-6.6.3-1.lbn36.noarch: Jupyter Console A terminal-based console frontend for Jupyter kernels. This code is based on the single-process IPython terminal. Install with pip: pip install jupyter-console Install with conda: conda install -c conda-forge jupyter_console Start: jupyter console Help: jupyter console -h Jupyter Console allows for console-based interaction with non-python Jupyter kernels such as IJulia, IRKernel. To start the console with a particular kernel, ask for it by name:: jupyter console --kernel=julia-0.4 A list of available kernels can be seen with:: jupyter kernelspec list Release build: $ pip install pep517 $ python -m pep517.build . Resources Project Jupyter website Documentation for Jupyter Console [PDF] Documentation for Project Jupyter [PDF] Issues Technical support - Jupyter Google Group About the Jupyter Development Team The Jupyter Development Team is the set of all contributors to the Jupyter project. This includes all of the Jupyter subprojects. The core team that coordi

python3-sqlalchemy-spanner-1.6.2-2.lbn36.noarch: Spanner dialect for SQLAlchemy represents an interface API designed to make it possible to control Cloud Spanner databases with SQLAlchemy API. The dialect is built on top of the Spanner DB API, which is designed in accordance with PEP-249. Known limitations are listed here. All supported features have been tested and verified to work with the test configurations. There may be configurations and/or data model variations that have not yet been covered by the tests and that show unexpected behavior. Please report any problems that you might encounter by creating a new issue. Cloud Spanner product documentation SQLAlchemy product documentation Quick Start In order to use this package, you first need to go through the following steps: Select or create a Cloud Platform project. Enable billing for your project. Enable the Google Cloud Spanner API. Setup Authentication. Installation Stable released version of the package is available on PyPi: pip install sqlalchemy-spanner To install a

python3-snowflake-connector-3.15.0-1.lbn36.x86_64: This package includes the Snowflake Connector for Python, which conforms to the Python DB API 2.0 specification: Documentation is available at: code is also available at: Release Notes- v2.8.2(November 18,2022) - Improved performance of OCSP response caching - During the execution of GET commands we no longer resolve target location on the local machine - Improved performance of regexes used...

python3-pgvector-0.3.6-1.lbn36.noarch: pgvector-python pgvector support for Python Supports Django, SQLAlchemy, SQLModel, Psycopg 3, Psycopg 2, asyncpg, and Peewee Installation Run: pip install pgvector And follow the instructions for your database library: Django SQLAlchemy SQLModel Psycopg 3 Psycopg 2 asyncpg Peewee Or check out some examples: Embeddings with OpenAI Sentence embeddings with SentenceTransformers Hybrid search with SentenceTransformers (Reciprocal Rank Fusion) Hybrid search with SentenceTransformers (cross-encoder) Sparse search with Transformers Image search with PyTorch Image search with perceptual hashing Implicit feedback recommendations with Implicit Explicit feedback recommendations with Surprise Recommendations with LightFM Horizontal scaling with Citus Bulk loading with COPY Django Create a migration to enable the extension from pgvector.django import VectorExtension class Migration(migrations.Migration): operations = [ VectorExtension() ] Add a vector field to your model fro

python3-opensearch-py+kerberos-2.8.0-1.lbn36.noarch: This is a metapackage bringing in kerberos extras requires for python3-opensearch-py. It makes sure the dependencies are installed.

python3-opensearch-py+async-2.8.0-1.lbn36.noarch: This is a metapackage bringing in async extras requires for python3-opensearch-py. It makes sure the dependencies are installed.

python3-opensearch-py-2.8.0-1.lbn36.noarch: opensearch-py is a community-driven, open source OpenSearch client licensed under the Apache v2.0 License. For more information, see opensearch.org.

python3-openlineage-sql-1.24.2-1.lbn36.x86_64: Python interface for the Rust OpenLineage lineage extraction library

python3-openlineage-python-1.24.2-1.lbn36.noarch: OpenLineage-python To install from source, run: $ python -m pip install . Configuration Config file The most common way to configure the OpenLineage Client is by .yaml file, which contains all the details of how to connect to your OpenLineage backend. The config file is located by: looking at the OPENLINEAGE_CONFIG environment variable looking for the openlineage.yml file in the current working directory looking for the openlineage.yml file in the $HOME/.openlineage directory. Different ways of connecting to OpenLineage backend are supported by the standardized Transport interface. This is an example config for specifying http transport: transport: type: "http" url: "https:/backend:5000" auth: type: "api_key" api_key: "f048521b-dfe8-47cd-9c65-0cb07d57591e" The type property is required. It can be one of the built-in transports or a custom one. There are four built-in transports, http, kafka, console and file. Custom transports type is a fully qualified class name that

python3-openlineage-integration-common-1.24.2-1.lbn36.noarch: Common modules for OpenLineage integrations.

python3-mysqlclient-2.1.1-2.fc36.x86_64: MySQLdb is an interface to the popular MySQL database server that provides the Python database API.

python3-mysql-connector-python-9.0.0-1.lbn36.noarch: MySQL driver written in Python which does not depend on MySQL C client libraries and implements the DB API v2.0 specification (PEP-249).

python3-msgraph-core-1.1.0-1.lbn36.noarch: Microsoft Graph Core Python Client Library. The Microsoft Graph Core Python Client Library contains core classes used by Microsoft Graph Python Client Library to send native HTTP requests to Microsoft Graph API. NOTE: This is a new major version of the Python Core library for Microsoft Graph based on the Kiota project. We recommend to use this library with the full Python SDK. Upgrading to this version from the previous version of the Python Core library will introduce breaking changes into your application. Prerequisites Python 3.8+ This library doesn't support older versions of Python. Getting started 1. Register your application To call Microsoft Graph, your app must acquire an access token from the Microsoft identity platform. Learn more about this - Authentication and authorization basics for Microsoft Graph Register your app with the Microsoft identity platform 2. Install the required packages msgraph-core is available on PyPI. pip3 install msgraph-core pip3 install azure-id

python3-mergedeep-1.3.4-1.lbn36.noarch: [mergedeep]( release]( [![PyPi versions]( [![Downloads]( [![Conda Version]( [![Conda Downloads]( [![Documentation Status](

python3-impyla-0.18.0-1.lbn36.noarch: Python client for HiveServer2 implementations (e.g., Impala, Hive) for distributed query engines.For higher-level Impala functionality, including a Pandas-like interface over distributed data sets, see the [Ibis project][ibis]. Features* HiveServer2 compliant; works with Impala and Hive, including nested data* Fully [DB API 2.0 (PEP 249)][pep249]-compliant Python client (similar to sqlite or...

python3-types-termcolor-1.1.6.2-2.lbn36.noarch: Typing stubs for termcolor This is a PEP 561 type stub package for the termcolor package. It can be used by type-checking tools like mypy, pyright, pytype, PyCharm, etc. to check code that uses termcolor. The source for this package can be found at https:/github.com/python/typeshed/tree/main/stubs/termcolor. All fixes for types and metadata should be contributed there. Note: The termcolor package includes type annotations or type stubs since version 2.0.0. Please uninstall the types-termcolor package if you use this or a newer version. See https:/github.com/python/typeshed/blob/main/README.md for more details. This package was generated from typeshed commit 72456da2a3546044508828dc9075fa25cbdb3645.

« Previous 20 items Next 20 items » 1 ... 6 7 8 9 10 11 12 ... 2434


	Copyright © 2000-2025 Corporation of Balclutha Inc. All rights reserved.

Sections

Modified items