semvec/pypi-packages huggingface dataset:
segy2seg2 0.0.1
segy2seg2
Keywords: segy,seismic,seg2,segy to seg2 converter,segy to dat file converter,segy to dat file converter using python

# segy2seg2 - a Python package to convert segy seismic file to seg2 file.
Workable but not completely done yet!

## Getting Started
Its working example is shown in the "test.ipynb" file.
### Prerequisites
```
pip install obspy
```
### Installation 

```
pip install segy2seg2
```
cis-checks-6 0.0.7
Provides AWS compliance details
Requires Python: >=3.7

# OBP_security_pillar

OBP_security_Pillar package can be used to get the compliance details of Operational Best Practices for AWS Well Architected Security Pillar.

Release Notes:
# v0.0.1
1. Added following compliance checks:
   - RdsAutomaticMinorVersionUpgradeEnabled
   - RdsInstancePublicAccessCheck
   - RdsSnapshotEncrypted
   - RdsSnapshotsPublicProhibited
   - RdsStorageEncrypted
   - S3BucketLoggingEnabled
   - S3BucketVersioningEnabled
cis-checks-5 0.0.6
Provides AWS compliance details
Requires Python: >=3.7

# OBP_security_pillar

OBP_security_Pillar package can be used to get the compliance details of Operational Best Practices for AWS Well Architected Security Pillar.

Release Notes:
# v0.0.1
1. Added following compliance checks:
   - RdsAutomaticMinorVersionUpgradeEnabled
   - RdsInstancePublicAccessCheck
   - RdsSnapshotEncrypted
   - RdsSnapshotsPublicProhibited
   - RdsStorageEncrypted
   - S3BucketLoggingEnabled
   - S3BucketVersioningEnabled
disl 0.0.4
A super lightweight (only 35 lines) dependency injection (ioc) support for Python.
Requires Python: >=3.6

# disl: super lightweight (only 35 lines) dependency injection (ioc) support for Python

A super simple and risk-free way to do dependency injection (ioc) in Python.
The entire code base is only 35 lines (empty lines included). No need to
use a complex 3rd-party framework or be concerned about the long-term viability
of the library.

## How to use
Suppose you have a module to read some products' info from a DB file, so the
path to the DB file should be injected:

    from disl import Inject

    class ProductDb:
      def __init__(self):
        self.db_path=Inject()  # this variable will be set automatically
      
      def get_products(self):
        print(f"getting products from {self.db_path}")

In your main program, you link up the ProductDb object and the db_path:

    from disl import Disl

    di=Disl()  # this is the container
    di.add_raw_bean("pdb", ProductDb()) # add the bean under the name "pdb"
    di.add_raw_bean("db_path", "c:/Users/kent/test.db") # another bean
    pdb=di.get_wired_bean("pdb")  # the db_path field in the pdb bean will be set
    pdb.get_products()  # this pdb object is just the plain object you created

If the path to the DB is named "database_path" but your variable name is
just "db_path", you can do it like this:

    from disl import Inject

    class ProductDb:
      def __init__(self):
        self.db_path=Inject("database_path") # specify the bean name
      
      def get_products(self):
        print(f"getting products from {self.db_path}")

    from disl import Disl

    di=Disl()
    di.add_raw_bean("pdb", ProductDb())
    di.add_raw_bean("database_path", "c:/Users/kent/test.db")
    pdb=di.get_wired_bean("pdb")
    pdb.get_products()
scriptum 1.0.1
A command line utility for storing, documenting, and executing your project's scripts
Requires Python: >=3.6

# Scriptum
A command line utility for storing, documenting, and executing your project's scripts. 

## Documentation
See documentation [here](http://gadhagod.github.io/scriptum).

## A simple use case
With `scriptum`, you can easily configure scripts into a repo or directory, by placing defining them in a configuration file. Here is an example of a configuration file:
```jsonc
/*
  Scripts for my project!
*/
{
    "serve": "python3 server.py",           // runs the server
    "test": {                               // tests my project
        "permissions": {                    // configures the permissions
            "set": "chmod 777 main.py",     // makes the executable public
        },
        "run": "./main.py $1",              // runs the executable
        "checks": ["mypy **/*.py", "python3 tests/main.py"]       // runs the tests
    },
    "package": {                                                  // distribution
        "build": "python3 setup.py sdist bdist_wheel",            // prepares for release
        "publish": "twine upload --repository pypi dist/*"        // publishes the package
    },
    "deps": {                                                     // dependency management
        "install": ["pip3 install reqs.txt", "brew install pkg"], // installs dependencies
        "list": "cat reqs.txt",                                   // lists dependencies
        "resolve": "python3 -m pip freeze > main/reqs.txt"        // updates the dependency list
    },
    "docs": {                               // manage documentation
        "install": "npm i -g docsify",      // installs docs dependencies
        "serve": "docsify serve",           // runs the server
        "open": "open http://localhost:3000"// opens the preview
    }
}
```
You can now execute any of these scripts conviniently with the scriptum CLI (`scr`):
```bash
scr <script category> <script> <args>
```

So if you wanted to run the scripts, you can enter the them into the command line like so:

```bash
scr help                    # open index.html
scr deps install            # python3 -m pip install requirements.txt
scr deps resolve            # python3 -m pip freeze > requirements.txt
scr test permissions set    # chmod 777 main.py
scr test run [[production]] # ./main.py 'production'
scr test checks             # mypy **/*.py and ./tests/main.py
```

If you check the configuration file into you repo, your team can now run these scripts with ease.

## Features
* Highly configurable
* Cross-platform support
* Supports dependency management from multiple sources (NPM, pip, etc.)
* Script categories
* JSON configuration support for comments and documentation
* Supports command lists that stop on fail