semvec/pypi-packages huggingface dataset:
dbt-bigquery 1.11.0
The BigQuery adapter plugin for dbt
Requires Python: >=3.10.0
Keywords: adapter, adapters, bigquery, database, dbt, dbt Cloud, dbt Core, dbt Labs, dbt-core, elt, google

<p align="center">
    <img
        src="https://raw.githubusercontent.com/dbt-labs/dbt/ec7dee39f793aa4f7dd3dae37282cc87664813e4/etc/dbt-logo-full.svg"
        alt="dbt logo"
        width="500"
    />
</p>

<p align="center">
    <a href="https://pypi.org/project/dbt-bigquery/">
        <img src="https://badge.fury.io/py/dbt-bigquery.svg" />
    </a>
    <a target="_blank" href="https://pypi.org/project/dbt-bigquery/" style="background:none">
        <img src="https://img.shields.io/pypi/pyversions/dbt-bigquery">
    </a>
    <a href="https://github.com/psf/black">
        <img src="https://img.shields.io/badge/code%20style-black-000000.svg" />
    </a>
    <a href="https://github.com/python/mypy">
        <img src="https://www.mypy-lang.org/static/mypy_badge.svg" />
    </a>
    <a href="https://pepy.tech/project/dbt-bigquery">
        <img src="https://static.pepy.tech/badge/dbt-bigquery/month" />
    </a>
</p>

# dbt

**[dbt](https://www.getdbt.com/)** enables data analysts and engineers to transform their data using the same practices that software engineers use to build applications.

dbt is the T in ELT. Organize, cleanse, denormalize, filter, rename, and pre-aggregate the raw data in your warehouse so that it's ready for analysis.

## dbt-bigquery

`dbt-bigquery` enables dbt to work with Google BigQuery.
For more information on using dbt with BigQuery, consult [the docs](https://docs.getdbt.com/docs/profile-bigquery).

# Getting started

Review the repository [README.md](/README.md) as most of that information pertains to `dbt-bigquery`.

## Contribute

- Want to help us build `dbt-bigquery`? Check out the [Contributing Guide](CONTRIBUTING.md).
ezpi 0.5.1
A simple library to write content to public-inbox repositories
Requires Python: >=3.9
Keywords: git, lore.kernel.org, public-inbox

EZPI: a simple library to write to public-inbox repos
=====================================================
This is a very simple library that allows writing to public-inbox v2
repositories. Note, that this is not a suitable replacement for
public-inbox in itself -- the goal is merely to provide a way to write
public-inbox repositories that can be cloned, indexed and served from an
actual public-inbox server running elsewhere.

What it does:

- adds RFC2822 messages to git repositories compatible with public-inbox
- supports public-inbox v2 format with automatic epoch management

What it doesn't do:

- anything else

For the public-inbox v2 format, see:

- https://public-inbox.org/public-inbox-v2-format.html

Requirements
------------
The ``git`` command must exist and be in your path.

Installing
----------
For CLI usage, install with pipx::

  pipx install ezpi

For library usage, install with pip::

  pip install ezpi

Library usage
-------------
This is the simplest usage example:

.. code-block:: python

  from email.message import EmailMessage
  from ezpi import add_rfc822_v2

  msg = EmailMessage()
  msg.set_content('Hello world!')
  # We must have a Subject: and From: headers at least, in order
  # to make a useful git commit with that data
  msg['Subject'] = 'My excellent subject'
  msg['From'] = 'E.X. Ample <example@example.com'>
  # The v2 inbox will be created automatically if it doesn't exist
  add_rfc822_v2('/path/to/inbox', msg)

You can also pass bytes instead of an EmailMessage object, but we must
be able to run message_from_bytes() on it.

ezpi command
------------
We also provide an ezpi command. Example::

  ezpi --v2-path /path/to/inbox --rfc822 < valid.eml

Run ``ezpi --help`` for full usage information.

How to delete messages?
-----------------------
Since every message is a separate commit to the git repository, deleting
requires a git history rewrite. You will need to find the commit with
the message you want to delete and perform operations directly on the
git repository in order to delete that commit and rebase the ones that
follow. Once it's done, you will need to force-push the repository to
wherever it is hosted.

Caution: if anyone is replicating your repository without --mirror, the
history rewrite will result in an error the next time they do "git
remote update". Needless to say, they will be very interested in finding
out what it is you just tried to delete, so use this as the last resort
solution.

Problems? Patches?
------------------
Email ~monsieuricon/public-inbox@lists.sr.ht

(That's a different kind of public-inbox. Unfortunately, there's a name
collision, but I believe public-inbox.org had that claimed earlier.)
enthusiast-model-azureopenai 1.2.0
A plugin for Enthusiast that provides an OpenAI connector.
Requires Python: <4.0,>=3.10

Following variables must be set in order to make this plugin work:

```
AZURE_OPENAI_API_KEY: Azure OpenAI key
OPENAI_API_VERSION: OpenAI API version
AZURE_OPENAI_ENDPOINT: Your Azure endpoint, including the resource, e.g. `https://example-resource.azure.openai.com/`
```
senzing 4.1.0
Python SDK method definitions
Requires Python: >=3.10

# sz-sdk-python

If you are beginning your journey with [Senzing],
please start with [Senzing Quick Start guides].

You are in the [Senzing Garage] where projects are "tinkered" on.
Although this GitHub repository may help you understand an approach to using Senzing,
it's not considered to be "production ready" and is not considered to be part of the Senzing product.
Heck, it may not even be appropriate for your application of Senzing!

## :warning: WARNING: sz-sdk-python is still in development :warning: \_

At the moment, this is "work-in-progress" with Semantic Versions of `0.n.x`.
Although it can be reviewed and commented on,
the recommendation is not to use it yet.

## Synopsis

The Senzing `sz-sdk-python` package contains the abstract base class from which
implementations of the Senzing Python SDK are derived.

[![Python 3.13 Badge]][Python 3.13]
[![PEP8 Badge]][PEP8]
[![PyPI version Badge]][PyPi version]
[![Downloads Badge]][Downloads]
[![License Badge]][License]
[![Coverage Badge]][Coverage]

## Overview

## Use

## References

1. [Development]
1. [Errors]
1. [Examples]
1. [sz-sdk-python package reference]

[Coverage badge]: https://img.shields.io/badge/dynamic/json?color=brightgreen&label=coverage&query=%24.message&url=https%3A%2F%2Fraw.githubusercontent.com%2Fsenzing-garage%2Fsz-sdk-python%2Fpython-coverage-comment-action-data%2Fendpoint.json
[Coverage]: https://htmlpreview.github.io/?https://github.com/senzing-garage/sz-sdk-python/blob/python-coverage-comment-action-data/htmlcov/index.html
[Development]: docs/development.md
[Downloads Badge]: https://static.pepy.tech/badge/senzing
[Downloads]: https://pepy.tech/project/senzing
[Errors]: docs/errors.md
[Examples]: docs/examples.md
[License Badge]: https://img.shields.io/badge/License-Apache2-brightgreen.svg
[License]: https://github.com/senzing-garage/sz-sdk-python/blob/main/LICENSE
[PEP8 Badge]: https://img.shields.io/badge/code%20style-pep8-orange.svg
[PEP8]: https://www.python.org/dev/peps/pep-0008/
[PyPI version Badge]: https://badge.fury.io/py/senzing.svg
[PyPi version]: https://badge.fury.io/py/senzing
[Python 3.13 Badge]: https://img.shields.io/badge/python-3.13-blue.svg
[Python 3.13]: https://www.python.org/downloads/release/python-3130/
[Senzing Garage]: https://github.com/senzing-garage
[Senzing Quick Start guides]: https://docs.senzing.com/quickstart/
[Senzing]: https://senzing.com/
[sz-sdk-python package reference]: https://hub.senzing.com/sz-sdk-python/