semvec/pypi-packages huggingface dataset:
omniplate 3.0.24
For analysing and meta-analysing plate-reader data
License: MIT
Requires Python: <3.12,>=3.11
Keywords: omniplate, systems biology, bioinformatics, plate readers

# Omniplate
A Python package for analysing data from plate-reader studies of growing biological cells. Users can correct for autofluorescence, determine growth rates and the amount of fluorescence per cell, and simultaneously analyse multiple experiments.

## Documentation
A tutorial is [available](https://swainlab.bio.ed.ac.uk/software/omniplate/).

## Development history
+ `v3.0`: Consistent use of snake_case, but breaking backwards compatibility
+ `v3.0.2`: Only for python 3.11. Nunchaku updated.

## Citation
If you find the software useful, please consider citing:

Montaño-Gutierrez, L. F., Moreno, N. M., Farquhar, I. L., Huo, Y., Bandiera, L., & Swain, P. S. (2022). Analysing and meta-analysing time-series data of microbial growth and gene expression from plate readers. PLOS Computational Biology, 18(5), e1010138.
svix 1.85.0
Svix webhooks API client and webhook verification library
License: MIT
Requires Python: >=3.6
Keywords: svix, diahook, webhooks

<h1 align="center">
    <a style="text-decoration: none" href="https://www.svix.com">
      <img width="120" src="https://avatars.githubusercontent.com/u/80175132?s=200&v=4" />
      <p align="center">Svix - Webhooks as a service</p>
    </a>
</h1>
<h2 align="center">
  <a href="https://svix.com">Website</a> | <a href="https://docs.svix.com">Documentation</a> | <a href="https://svix.com/slack">Community Slack</a>
<h2>

Python library for interacting with the Svix API and verifying webhook signatures

![GitHub tag](https://img.shields.io/github/tag/svix/svix-webhooks.svg)
[![PyPI](https://img.shields.io/pypi/v/svix.svg)](https://pypi.python.org/pypi/svix/)

[![Join our slack](https://img.shields.io/badge/Slack-join%20the%20community-blue?logo=slack&style=social)](https://www.svix.com/slack/)

# Usage Documentation

You can find general usage documentation at <https://docs.svix.com>.  For complete API documentation with code examples for each endpoint in all of our official client libraries head over to our API documentation site at <https://api.svix.com>.

# Language Support

<table style="table-layout:fixed; white-space: nowrap;">
  <th colspan="2">⚡️ Features ⚡️</th>
  <tr>
    <th>Officially Supported</th>
    <th>✅</th>
  </tr>
  <tr>
    <th>API Support</th>
    <th>✅</th>
  </tr>
  <tr>
    <th>Signature Verification</th>
    <th>✅</th>
  </tr>
  <tr>
    <th>Caveats</th>
    <th>None! 🚀</th>
  </tr>
</table>

# Installation

```sh
pip install Svix
```

## Usage
Please refer to [the documentation](https://docs.svix.com/) or [the API reference](https://api.svix.com/docs) for more usage instructions.

### Async
```python
from svix.api import SvixAsync, ApplicationIn

svix = SvixAsync("AUTH_TOKEN")
app = await svix.application.create(ApplicationIn(name="Application name"))
```

### Sync

```python
from svix.api import Svix, ApplicationIn

svix = Svix("AUTH_TOKEN")
app = svix.application.create(ApplicationIn(name="Application name"))
```

# Development

First checkout the [core README](../README.md#development) for details on how to generate our API bindings, then follow the steps below.

## Requirements

 - python 3

## Installing dependencies

```sh
python -m venv .venv
pip install -r requirements.txt && pip install -r requirements-dev.txt
```

## Contributing

Before opening a PR be sure to format your code!

```sh
./scripts/format.sh
```

## Running Tests

Simply run:

```sh
pytest
```
jeeves-pr-stack 0.1.7
Manage GitHub Pull Request stacks.
License: MIT
Requires Python: <4.0,>=3.10

# `jeeves-pr-stack`

`jeeves-pr-stack` is a plugin for [jeeves](https://jeeves.sh) that helps manage stacks of GitHub pull requests. It aims to simplify the code review process by organizing pull requests that depend on each other.

## Installation

```shell
poetry add --group dev jeeves-pr-stack
```

## Motivation

While pull requests are a powerful tool for code review, they tend to become larger and larger, and thus more difficult for the reviewer to tackle.

One possible way to resolve that is to split implementation of a feature into two or more pull requests. For instance,

* PR `#42` **Backend for the Super Feature** directed from `super-feature-backend` branch to `main` branch,
* and PR `#43` **Frontend for the Super Feature** directed from `super-feature-frontend` branch to `super-feature-backend` branch.

The PRs are written in such a way that the first of them can be independently merged to `main` and deployed without breaking the system. This makes the process of code review faster and easier, and allows to deploy more often.

Let's call such structures **PR Stacks**.

### Caveats

Managing PR Stacks manually can be tedious; for instance, every time when changing `#42` you need to rebase `#43`. It becomes particularly annoying when the length of the stack is more than 2.

`jeeves-pr-stack` comes to the rescue.

## Commands

### `j stack`

View the current PR Stack.

### `j stack push`

* Create a new PR in current branch if none exists, or use the one that is there,
* And set the base branch of this PR to point to another open PR in the repository, stacking one PR on top of another.

### `j stack pop`

* Fetch the bottom-most PR of current stack,
* Merge it into the repository main branch,
* Redirect the follow-up PR to point to the main branch so as to make it mergeable,
* And delete the branch of the PR that was merged.