semvec/pypi-packages huggingface dataset:
win32-scdump 0.1.0
Scylla Process Dumper is a lightweight and easy-to-use debugging tool designed to create dumps of running processes on Windows using Scylla
Requires Python: >=3.6

# Scylla process dumper

**Scylla Process Dumper** is a lightweight and easy-to-use debugging tool designed to create dumps of running processes on Windows using Scylla. It helps developers and analysts capture the state of a process for debugging, reverse engineering, or forensic analysis.

---

## Features

- Dump live Windows processes quickly and reliably
- Simple command-line interface
- Supports dumping by process executable name or path
- Returns process exit code for scripting and automation
- Includes necessary binaries bundled for ease of use

---

## Installation

```bash
python3 -m pip install win32-scdump
```

---

## Usage

Run the scdump command in your terminal or command prompt, specifying the target executable name or path and the desired output filename for the dump.

```bash
scdump target_name.exe output_name.exe
```

target_process.exe — the name or path of the target process you want to dump.

output_dump.exe — the filename where the dumped executable will be saved.


## Example

To create a dump of the Notepad process and save it as notepad_dump.exe, run:

```bash
scdump notepad.exe notepad_dump.exe
```
cdk-pug-platform 1.0.1
AWS CDK application for the PUG Platform
Requires Python: >=3.6

# CDK PUG PLATFORM

## This is a platform for the CDK PUG (Python User Group) to manage and deploy applications using AWS CDK

### Features

- Create and manage AWS CDK applications
- Deploy applications to AWS
- Manage application dependencies
- Manage application environments
- Manage application configurations
- Manage application secrets
- Manage application logs
- Manage application metrics
- Manage application alarms
- Manage application notifications
- Manage application events
- Manage application resources
- Manage application permissions
- Manage application policies
- Manage application roles
- Manage application users
- Manage application groups
- Manage application access control
- Manage application authentication
- Manage application authorization
- Manage application security
- Manage application compliance
- Manage application monitoring
- Manage application auditing
- Manage application reporting
- Manage application backups
- Manage application restores

### Requirements

- Python 3.8 or later
- AWS CDK installed
- AWS CLI configured with your credentials

### OPEN TO CONTRIBUTIONS

We welcome contributions to this project. If you have an idea for a new feature or a bug fix, please open an issue or a pull request. We will review it and merge it if it meets our standards.

### license

This project is licensed under the MIT License. See the [MIT]([LICENSE](https://github.com/morales-corp/cdk-pug-platform/blob/master/LICENSE)) file for more.

### Installation

To install the CDK PUG Platform, you can use pip:

```bash
pip install cdk-pug-platform
```

### Contact

For any questions or issues, please contact us at [CESAR MORALES](me@cesarmoralesonya.es)
tpg366-ioc 0.1.1
Command-line client tools for EPICS-CA data processing
Requires Python: >=3.8

IOC for the Pfefiffer TPG-366 Pressure Gauge
============================================

This in an unofficial, as-simple-as-it-gets IOC for the Pfeiffer TPG-366
pressure gauge.

It does nothing else except reading out temperatrue and status
data, publishing them via PV suffixes `.VALUE` and `.STATUS` for
each gauge. The exact format of the PVs is `{prefix}G{cnt}:STATUS`,
respectively `{prefix}G{gauge}:VALUE` with `{prefix}` as the EPICS
prefix (e.g. "DOODLE:") and `{cnt}` as the gauge counter, starting
at 1. For instance:

 - `DOODLE:G1:VALUE`
 - `DOODLE:G1:STATUS`
 - `DOODLE:G2:VALUE`
 - `DOODLE:G2:STATUS` ...

Obtaining & Running
-------------------

Via Pip:
```
$ pip install tpg366-ioc
$ export PFEIFFER_EPICS_PREFIX=DOODLE:
$ export PFEIFFER_VISA_DEVICE=TCPIP::192.168.1.17::8000::SOCKET
$ tpg-366-ioc
```

Or via Podman:
```
$ podman run -ti --rm \
     -e PFEIFFER_EPICS_PREFIX=DOODLE: \
     -e PFEIFFER_VISA_DEVICE=TCPIP::192.168.1.17::8000::SOCKET
     registry.gitlab.com/kmc3-xpp/tpg366-ioc:latest
```

Or directly from source, via git clone:
```
$ git clone https://gitlab.com/kmc3-xpp/tpg366-ioc
$ pip install -e tpg366-ioc[all]
$ export PFEIFFER_EPICS_PREFIX=DOODLE:
$ export PFEIFFER_VISA_DEVICE=TCPIP::192.168.1.17::8000::SOCKET
$ tpg-366-ioc
```

Environment Variables
---------------------

TPG-IOC is controlled via environment variables:

- `PFEIFFER_EPICS_PREFIX` EPICS prefix including the trailing ":"
- `PFEIFFER_VISA_DEVICE` VISA device address specification. Note that
  anything other than TCPIP-schemes may cause problems currently.
  Typically, the default port for these devices is 8000, so your TCP/IP
  VISA device would be something like: "TCPIP::\<host\>::8000::SOCKET".
- `PFEIFFER_VISA_RMAN` VISA resource manager, defaults to "@py"
- `PREIFFER_NR_GAUGES` number of gauges to query / display, defaults
  to 6.


Bugs & Caveats
--------------

Async operation, which the EPICS PV part depends on, only seems
to work fine with TCP/IP VISA devices. This is owing to bugs
within the VISA framework. Could be worked around, but it isn't
a priority currently (contact us if you have a use case).

The IOC is very, *very* simple -- just reading pressure values.
No configuration, no advaced features.

Normally there would be unit tests and a sim-mode prior to building
the image -- this time there aren't. Eventually they'll get
retrofitted (there is a test harness in place). But for now,
be careful with upgrades.
slacktokens 0.2.6
Extract personal tokens and authentication cookie from the Slack app
Requires Python: <3.12,>=3.7

# SlackTokens
Extract personal tokens and authentication cookie from the Slack app, to use with the Slack API.

---

# Description

`slacktokens` is a tool for providing programmatic access to the [Slack](https://slack.com/) ecosystem.

***This project is not endorsed or authorised in any way by Slack Technologies LLC.***

The Slack API is how all Slack clients, including the official desktop app and third-party
bots, read and write data that constitutes the Slack user experience. All clients much
provide authorisation to access the API.

As of July 2021, individual user access to the Slack API (as opposed to bot access) is
granted by providing a personal token (beginning with `xoxc-`) and a cookie called `d`.
Each Slack Workspace has its own personal token, but the cookie is the same for all.

If you use the Slack desktop app, these details will be stored on your local machine.
This script extracts them from the app's local store so you can use them for purposes not
provided for by the app itself.

# Usage

Calling `get_tokens_and_cookie()` will return the necessary authorisation details as a
Python dictionary, in the following format:

```
{
  'tokens': [
    'Workspace name': { token: <personal-token>, url: <URL of Workspace> }
    ]
  'cookie': { 'name': 'd', 'value': <value-of-d-cookie> }
}
```

This data can be used for calls to the Slack API. For example:

```
curl 'https://slack.com/api/team.info?token=<personal-token>' --header 'Cookie: d=<value-of-d-cookie>'
```

# Details

Your personal tokens are extracted by querying the Slack app's HTML Web Storage database. The token for each Workspace is stored in a dictionary in the `localStorage` object, in a `LevelDB` database. The useful fields extracted from the dictionary, other than the token itself, are the human readable Workspace name, and the Workspace URL.

The cookie is extracted from the Slack app's cookie store. The cookie of interest is
stored encrypted, so a modified version of `pycookiecheat` is used to decrypt the
contents. The decryption process will prompt you for your user password, which is used
only to pull out the cookie store encryption secret from your keychain.

# Shortcomings
- macOS and Linux only.
	- Windows support contributions welcome.
- Slack Desktop App only.
	- Browser support contributions welcome. Preferred implementation: failover to looking through browsers if the app access method fails.
- Might require the app to be closed, because LevelDB is not a multi-user database and there are no read-only access options.
- No established method for persisting the token data. Thought long and hard about this, and decided to keep the interface flexible and to leave suitable persistance methods as an exercise for the user.
	- It turns out the script is fast and read-only, so if the user is another Python script, then perhaps no persistance is required.
abarna-calc07 0.1.2
A simple calculator package by Abarna
Requires Python: >=3.6

# simplecalc

A very simple calculator package in Python.

## Features

- add(a, b)
- subtract(a, b)
- multiply(a, b)
- divide(a, b)

## Usage

```python
from abarna_calc07 import add, subtract

print(add(2, 3))       # 5
print(subtract(5, 1))  # 4