semvec/pypi-packages huggingface dataset:
quick-scraping 1.0.1
Toolkit para web scraping combinando Selenium e BeautifulSoup
Requires Python: >=3.7
Keywords: web scraping, selenium, beautifulsoup, automation, html, parsing, extraction

# Quick Scraping

Uma biblioteca Python completa para web scraping e automação, combinando o poder do Selenium e BeautifulSoup.

## Características

- **Módulo Selenium**: Automação completa de navegadores web
- **Módulo BeautifulSoup**: Análise e extração avançada de HTML
- **Integração**: Funções para trabalhar com ambas as bibliotecas de forma integrada
- **Ferramentas de Utilidade**: Processamento de texto, CSV, JSON e mais
- **Logging**: Sistema de registro completo para todas as operações

## Instalação

```bash
pip install quick-Scraping
```

Para instalar com dependências opcionais:

```bash
# Para desenvolvimento
pip install quick-Scraping[dev]

# Para documentação
pip install quick-Scraping[docs]
```

## Uso Básico

### Exemplo com Selenium

```python
from quick_Scraping.selenium_functions import SeleniumHelper

# Inicializa o Selenium Helper
with SeleniumHelper(browser_type="chrome", headless=True) as selenium:
    # Navega para uma URL
    selenium.navigate.to("https://www.exemplo.com")
    
    # Espera por um elemento e clica nele
    selenium.element.wait_for_element("id", "meu-botao", timeout=10)
    selenium.interact.click("id", "meu-botao")
    
    # Obtém o HTML da página
    html = selenium.driver.page_source
```

### Exemplo com BeautifulSoup

```python
from quick_Scraping.beautifulsoup_functions import HTMLParser, DataExtractor

# Inicializa o parser HTML e o extrator de dados
parser = HTMLParser()
extractor = DataExtractor()

# Carrega HTML de um arquivo ou URL
soup = parser.load_from_url("https://www.exemplo.com")

# Extrai dados estruturados
links = extractor.extract_links(soup)
table_headers, table_data = extractor.extract_table(soup, table_selector="table.dados")

# Extrai artigo completo
article = extractor.extract_article_content(soup)
```

### Exemplo de Integração

```python
from quick_Scraping.common import ScrapingHelper

# Inicializa o helper integrado
scraper = ScrapingHelper()

# Configura extração de dados
extraction_config = {
    "title": {"type": "text", "selector": "h1.title"},
    "products": {"type": "table", "selector": "table.products"},
    "links": {"type": "links", "selector": "a.product-link"}
}

# Navega e extrai dados
results = scraper.extract_data_with_selenium(
    url="https://www.exemplo.com/produtos",
    extraction_config=extraction_config,
    wait_time=3
)

# Salva os resultados
scraper.save_results(results, "produtos.json", format="json")
```
bluefin-v2-client-sui 1.2.0
Library to interact with Bluefin exchange protocol including its off-chain api-gateway and on-chain contracts
Requires Python: >=3.8
Keywords: bluefin, exchange, decentralized, perpetuals, blockchain

<div align="center">
  <img height="100x" src="https://bluefin.io/images/bluefin-logo.svg" />

  <h1 style="margin-top:20px;">Bluefin Python Client Library</h1>

</div>

Python Client for the Bluefin Exchange API and SUI Contracts.

## 📘 Bluefin RFQ Client Documentation
🔹 Learn how to use the RFQ Client by following the guide below

[![Read RFQ Client Docs](https://img.shields.io/badge/Read%20Docs-bluefin%20RFQ%20Client-blue?style=for-the-badge)](https://github.com/fireflyprotocol/bluefin-v2-client-python/blob/main/docs/README.rfq.md)

## 📘 Bluefin Perps Exchange V2 Client Documentation
🔹 Learn how to use the Bluefin V2 Perps Client by following the guide below 

[![Read Perps v2 Client Docs](https://img.shields.io/badge/Read%20Docs-bluefin%20perps%20(v2)%20Client-blue?style=for-the-badge)](https://github.com/fireflyprotocol/bluefin-v2-client-python/blob/main/docs/README.perps.md)
​
tc-prometheus 4.0.0
Thumbor Prometheus metrics extension

# Thumbor Prometheus Metrics Plugin [![Build Status](https://travis-ci.org/thumbor-community/prometheus.svg?branch=master)](https://travis-ci.org/thumbor-community/prometheus)

Collecting Thumbor runtime metrics using the prometheus\_client and exposes them
via an HTTP endpoint on a configurable port.

## Installation

```bash
# latest stable
pip install tc_prometheus

# master branch
pip install -e git+https://github.com/thumbor-community/prometheus.git@master#egg=tc_prometheus
```

## Configuration

```python
# thumbor.conf
METRICS = 'tc_prometheus.metrics.prometheus_metrics'

# optional with defaults
PROMETHEUS_SCRAPE_PORT = 8000 # Port the prometheus client should listen on
```

## Multiprocess support

In case thumbor is to be started with multiple processes using the `--processes` argument, the prometheus
client can handle that by the administrator setting the environment variable `PROMETHEUS_MULTIPROC_DIR`.
Please read the corresponding [documentation](https://prometheus.github.io/client_python/multiprocess/) to
understand the implications of that.

Basic example:

```sh
set -e
export PROMETHEUS_MULTIPROC_DIR=/tmp/thumbor/proc_dir
mkdir -p "$PROMETHEUS_MULTIPROC_DIR"
rm -rf "$PROMETHEUS_MULTIPROC_DIR"/* # this is crucial on the 2nd and following runs, but check the documentation
thumbor --processes `nproc` -c /path/to/thumbor.conf
```

## Upgrade notes

### from 3.x to 4.x
The metric with the name `original_image.fetch` was renamed to two different ones with the names
`original_image.fetch.count` and `original_image.fetch.latency`.

**This requires at least thumbor in version [7.7.5](https://github.com/thumbor/thumbor/releases/tag/7.7.5)**

**Please make sure to adjust all recording rules, alerting rules and dashboards which are relying on these metrics.**

### from 2.x to 3.x
All metrics of type `counter` have had before an enforced postfix of `_incr` which is now gone. Therefore
all metrics of type `counter` are renamed and will not match with previously recorded metrics anymore.

**Please make sure to adjust all recording rules, alerting rules and dashboards which are relying on these counters.**

### from 1.x to 2.x
The switch from 1.x to 2.x is not requiring any change within thumbors configuration or the plugin itself.
The crucial difference is, that some metrics will be renamed, so that you might need to update your monitoring/alarming.
Also be aware that you will get a lot more metrics until the old ones cease to exit which can be okay but on big
installation it might create issues by itself.