semvec/pypi-packages huggingface dataset:
just-prompt-sdk 0.1.1
A Python SDK for fetching and rendering prompts from Prompt Studio API
Requires Python: >=3.8.1
Keywords: prompt, template, api, sdk, jinja2

# Prompt Studio SDK

A Python SDK for fetching and rendering prompts from Prompt Studio API.

## Installation

```bash
pip install just-prompt-sdk
```

## Usage

### Standalone rendering
```python
from prompt_studio import render

rendered = render("Hello, {{name}}!", {"name": "World"})
print(rendered)  # Output: Hello, World!
```

### With API integration
```python
from prompt_studio import PromptStudio, render

studio = PromptStudio(api_key="your-api-key")
prompt = studio.get_prompt("my-project", "my-prompt")
rendered = render(prompt, {"name": "World"})
```

## License

MIT License
new-logger 0.1.0
Loguru-based logger utilities with file and tracker handlers
Requires Python: >=3.8
Keywords: logging, loguru, logger

# new_logger

A small utility package that wraps Loguru with two pre-configured loggers and file handlers:

- `logger`: console-bound logger (INFO+ to stderr by default) with optional rotating file handlers per level.
- `tracker_logger`: silent console, writes tracker lines to a dedicated rotating file.

## Installation

Build the wheel and install it into your environment:

```bash
python -m pip install --upgrade build wheel
python -m build
python -m pip install dist/new_logger-0.1.0-py3-none-any.whl
```

## Usage

```python
from new_logger import (
    logger,
    tracker_logger,
    add_file_handler_to_logger,
    add_track_handler,
)

# Add rotating file handlers (daily rotation, 7 days retention)
add_file_handler_to_logger(name="app", dir_path="./logs", level="DEBUG")
add_file_handler_to_logger(name="app", dir_path="./logs", level="ERROR")

# Add tracker handler (plain message lines)
add_track_handler(dir_path="./logs")

logger.info("Hello from new_logger")
tracker_logger.info("user_id=123 action=click item_id=42")
```

## Requirements

- Python >= 3.8
- `loguru>=0.7`

## Notes

- Console output filters to `INFO` and above.
- File handlers rotate daily and keep 7 days.
- `tracker_logger` writes only to its tracker sink, not console.
smartmetertx2mongo 1.3.0
Implementation of SmartMeter Texas to store reads in MongoDB and serve a simple UI/API.
Requires Python: >=3.9

# Original Class Object
https://github.com/cmulk/python_smartmetertx

# python-smartmetertx
SmartMeterTX/SmartMeter Texas Python class provides a JSON interface to the electricity usage data available at https://www.smartmetertexas.com.
You must have an account established at the site.

Additions done by [@Markizano](http://github.com/markizano) to support updates since JAN 2024.
API seems to be the same.

More details can be found: https://github.com/mrand/smart_meter_texas

Depends on a MongoDB server to be running in the environment of sorts.

Will have to later build support for sqlite3 for local DB setup installs
that require no further software than this package.

More documentation in [doc](./doc).

I created this as a means to collect and store data longer than the two years SMTX stores data.
In this way, you can have this in your local database and render charts and graphs no matter who your electric provider is.
If you live in Texas, you know how challenging it can be searching for a new provider every couple of months to annually
and not having clear access to your electric usage history.

This is a project used to help piece together some of that together so I have a single interface when dealing with my electric usage.

I, Markizano, will support this project as long as I live in Texas.

# Prerequisites
- [Setting up an unprivileged script account](./doc/unprivileged-setup.md)

Notable files below:

# bin/fetchMeterReads.cron.py
Full documentation: [fetchMeterReads.cron.py.md](./doc/fetchMeterReads.cron.py.md)

# bin/meterReadsReport.py
Full documentation: [meterReadsReport.py.md](./doc/meterReadsReport.py.md)

# bin/smtx-server.py
Full documentation: [smtx-server.py.md](./doc/smtx-server.py.md)

Extend as you please from here :)

**Update FEB 2024**
SmartMeterTX has changed their API endpoints and now requires you to have your address whitelisted with them and to setup an SSL certificate with them.

You can email `support-at-smartmetertexas-dot-com` (I redacted the @ and . to derail the bots) to get your address
whitelisted and coordinate with them on a public-facing SSL certificate for the HTTP/2.0 connection.

# Screenshots
![smtx-sample-page](https://markizano.net/assets/images/smtx-home-page.png)

# References
- SMTX API Documentation: https://www.smartmetertexas.com/commonapi/gethelpguide/help-guides/Smart_Meter_Texas_Data_Access_Interface_Guide.pdf
todds-timer 2025.9.12
A custom timer utility for Python
Requires Python: >=3.10

# Todd's Timer

[![PyPI version](https://badge.fury.io/py/todds_timer.svg)](https://badge.fury.io/py/todds_timer)
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

A versatile and easy-to-use Python timer utility for measuring code execution time and analyzing performance.

## Features

- Use as a decorator or context manager
- Nested timing support with proper indentation
- Detailed logging of start and end times
- Statistical analysis of execution times across multiple runs
- Customizable task names with support for dynamic formatting
- Lightweight and easy to integrate into existing projects

## Installation

Install Todd's Timer using pip:

```bash
pip install todds_timer
```

## Usage

At the top of your python file, import the Timer class and configure logging.
Standard timing messages are logged at the DEBUG level, however the summary table
produced by `print_average_times()` is at the INFO level.

```python
from todds_timer import Timer
import logging

logging.basicConfig(level=logging.DEBUG, format="%(levelname)s %(message)s")
```

### As a Context Manager

```python
with Timer("Calculating sum"):
    result = sum([1,2,3,4])
```
Output:
```
DEBUG ----STARTED Calculating sum
DEBUG ----COMPLETED (in 0.000 seconds) Calculating sum
```

### As a Decorator

```python
@Timer("Calculate sum of {0} and {1}")
def add_numbers(a, b):
    return a + b

result = add_numbers(5, 7)
```
Output:
```
DEBUG ----STARTED Calculate sum of 5 and 7
DEBUG ----COMPLETED (in 0.000 seconds) Calculate sum of 5 and 7
```

### Nested Timers

```python
with Timer("Outer operation"):
    # Some code here
    with Timer("Inner operation"):
        # More code here
        pass
```
Output:
```
DEBUG ----STARTED Outer operation
DEBUG --------STARTED Inner operation
DEBUG --------COMPLETED (in 0.000 seconds) Inner operation
DEBUG ----COMPLETED (in 0.000 seconds) Outer operation
```

### Analyzing Timing Results

```python
# After running some timed operations
Timer.print_average_times(sort="name")
```
Output:
```
INFO  Average | Minimum | Maximum | Count | Task name
INFO    0.000 |   0.000 |   0.000 |     1 | Calculate sum of 5 and 7
INFO    0.000 |   0.000 |   0.000 |     1 | Calculating sum
INFO    0.000 |   0.000 |   0.000 |     1 | Inner operation
INFO    0.000 |   0.000 |   0.000 |     1 | Outer operation
```

## Configuration

Todd's Timer uses Python's built-in `logging` module. To see the timing output, ensure that your logging is configured to show DEBUG level messages:

```python
import logging
logging.basicConfig(level=logging.DEBUG)
```

## Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

## License

This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.