semvec/pypi-packages huggingface dataset:
webauto-hj3415 0.1.2
Gathering the stock data
Requires Python: >=3.7

# webauto_hj3415 Package

This is a simple example package. You can use
[Github-flavored Markdown](https://guides.github.com/features/mastering-markdown/)
to write your content.

[Tutorials - How to packaging](https://packaging.python.org/en/latest/tutorials/packaging-projects/)
leetcode-cracker 0.0.5
package to assist in solving Leetcode Problems
Requires Python: >=3.10

# Leetcode Cracker Info
Leetcode Cracker is a Python package that allows you to get LeetCode question explanations and answers. LeetCode is a popular online platform for practicing coding skills and preparing for technical interviews. LeetCode offers hundreds of problems covering various topics, such as arrays, strings, trees, graphs, dynamic programming, etc. However, sometimes the official solutions and explanations are not clear enough or not available at all. Leetcode Cracker solves this problem by providing you with detailed and easy-to-understand explanations and answers for any LeetCode question. You can soon use Leetcode Cracker to:

- Search for a specific question by its title or ID
- Get a summary of the question, including its difficulty level, acceptance rate, tags, and company frequency
- Get a step-by-step explanation of the optimal solution, along with the time and space complexity analysis
- Get the Python code for the optimal solution, along with comments and test cases
- Compare your code with other solutions and learn from different approaches

Leetcode Cracker is designed to help you improve your coding skills and ace your technical interviews. It is easy to install and use.

# How to use the package

1. Import the package: `pip install leetcode-cracker`
2. Import package locally: `from leetcode_cracker import question_392`
3. Call for question: `question_392.print_question()`
4. Call for solution: `question_392.print_solution()`
5. Call for solution stats `question_392.solution_stats()`

# Question Database

# Easy

* Question 1 - Two Sum
* Question 9 - Palindrome Number
* Question 35 - Search Insert Position
* Question 58 - Length of last word
* Question 66 - Plus One
* Question 67 - Add Binary
* Question 70 - Climbing Stairs
* Question 118 - Pascal Triangle
* Question 119 - Pascal Triangle 2
* Question 121 - Best time to buy and sell stock
* Question 169 - Majority Element
* Question 217 - Comtains Duplicate
* Question 231 - Power of two
* Question 258 - Add Digits
* Question 263 - Ugly Number
* Question 268 - Missing Number
* Question 278 - First bad version
* Question 283 - Moving Zeros
* Question 326 - Power of three
* Question 342 - Power of Four
* Question 367 - Valid Perfect Square
* Question 392 - Is Subsequence
* Question 509 - Fibbinachi Numbers
* Question 728 - Self Dividing Numbers
* Question 1137 - Tribonacci Number
* Question 1480 - Running Sum of 1d array
* Question 2235 - Add Two Integers
* Question 2469 - Convert the Tempreture

# Medium

* Question 22 - Generate Parantheses
* Question 43 - Multiply Strings
* Question 46 - Permutations
* Question 47 - Permutations 2
* Question 50 - Pow(x, n)
* Question 371 - Sum of two integers
pymwr 0.1.0
Python package to interact with MWR data
Requires Python: >=3.6

# PyMWR

PyMWR is a Python package for interacting with microwave radiometer (MWR) data. It allows users to read, plot, and analyze MWR data from various sources.



## Installation

To install PyMWR, run the following command:

```python
pip install pymwr
```

Alternatively, you can install it from source:

```
pip install git+https://github.com/imsayyed/pymwr.git
```

Or, you can install it in --user mode:

```python
git clone https://github.com/imsayyed/pymwr.git
cd pymwr
python setup.py install --user
```
## Usage

Here is an [example](./examples/examples.ipynb) of how to read and plot MWR data using PyMWR.


## Contributing

If you would like to contribute to PyMWR, please read the Contributing Guidelines.


## License

PyMWR is licensed under the MIT License.


## Authors

- [Imran Sayyed](https://github.com/imsayyed) (sayyed950@gmail.com)
- [Hamid Ali Syed](https://github.com/syedhamidali) (hamidsyed37@gmail.com)
colorfultxt 0.0.1
A small example package
Requires Python: >=3.6


# Make sure you have upgraded version of pip
Windows
```
py -m pip install --upgrade pip
```

Linux/MAC OS
```
python3 -m pip install --upgrade pip
```

## Create a project with the following structure
```
packaging_tutorial/
├── LICENSE
├── pyproject.toml
├── README.md
├── setup.cfg
├── src/
│   └── example_package/
│       ├── __init__.py
│       └── example.py
└── tests/
touch LICENSE
touch pyproject.toml
touch setup.cfg
mkdir src/mypackage
touch src/mypackage/__init__.py
touch src/mypackage/main.py
mkdir tests
```

## pyproject.toml 

This file tells tools like pip and build how to create your project

```
[build-system]
requires = [
    "setuptools>=42",
    "wheel"
]
build-backend = "setuptools.build_meta"
```
build-system.requires gives a list of packages that are needed to build your package. Listing something here will only make it available during the build, not after it is installed.

build-system.build-backend is the name of Python object that will be used to perform the build. If you were to use a different build system, such as flit or poetry, those would go here, and the configuration details would be completely different than the setuptools configuration described below.


# Setup.cfg setup
Using setup.cfg is a best practice, but you could have a dynamic setup file using setup.py

```
[metadata]
name = example-pkg-YOUR-USERNAME-HERE
version = 0.0.1
author = Example Author
author_email = author@example.com
description = A small example package
long_description = file: README.md
long_description_content_type = text/markdown
url = https://github.com/pypa/sampleproject
project_urls =
    Bug Tracker = https://github.com/pypa/sampleproject/issues
classifiers =
    Programming Language :: Python :: 3
    License :: OSI Approved :: MIT License
    Operating System :: OS Independent

[options]
package_dir =
    = src
packages = find:
python_requires = >=3.6

[options.packages.find]
where = src

```
# Running the build
### Make sure your build tool is up to date
Windows
```
py -m pip install --upgrade build
```
Linux/MAC OS
```
python3 -m pip install --upgrade build
```


### Create the build
```
py -m build
```













### References
https://packaging.python.org/tutorials/packaging-projects/
colortxt 0.0.1
A small example package
Requires Python: >=3.6


# Make sure you have upgraded version of pip
Windows
```
py -m pip install --upgrade pip
```

Linux/MAC OS
```
python3 -m pip install --upgrade pip
```

## Create a project with the following structure
```
packaging_tutorial/
├── LICENSE
├── pyproject.toml
├── README.md
├── setup.cfg
├── src/
│   └── example_package/
│       ├── __init__.py
│       └── example.py
└── tests/
touch LICENSE
touch pyproject.toml
touch setup.cfg
mkdir src/mypackage
touch src/mypackage/__init__.py
touch src/mypackage/main.py
mkdir tests
```

## pyproject.toml 

This file tells tools like pip and build how to create your project

```
[build-system]
requires = [
    "setuptools>=42",
    "wheel"
]
build-backend = "setuptools.build_meta"
```
build-system.requires gives a list of packages that are needed to build your package. Listing something here will only make it available during the build, not after it is installed.

build-system.build-backend is the name of Python object that will be used to perform the build. If you were to use a different build system, such as flit or poetry, those would go here, and the configuration details would be completely different than the setuptools configuration described below.


# Setup.cfg setup
Using setup.cfg is a best practice, but you could have a dynamic setup file using setup.py

```
[metadata]
name = example-pkg-YOUR-USERNAME-HERE
version = 0.0.1
author = Example Author
author_email = author@example.com
description = A small example package
long_description = file: README.md
long_description_content_type = text/markdown
url = https://github.com/pypa/sampleproject
project_urls =
    Bug Tracker = https://github.com/pypa/sampleproject/issues
classifiers =
    Programming Language :: Python :: 3
    License :: OSI Approved :: MIT License
    Operating System :: OS Independent

[options]
package_dir =
    = src
packages = find:
python_requires = >=3.6

[options.packages.find]
where = src

```
# Running the build
### Make sure your build tool is up to date
Windows
```
py -m pip install --upgrade build
```
Linux/MAC OS
```
python3 -m pip install --upgrade build
```


### Create the build
```
py -m build
```













### References
https://packaging.python.org/tutorials/packaging-projects/
cpchecker 0.0.1
A small example package
Requires Python: >=3.6


# Make sure you have upgraded version of pip
Windows
```
py -m pip install --upgrade pip
```

Linux/MAC OS
```
python3 -m pip install --upgrade pip
```

## Create a project with the following structure
```
packaging_tutorial/
├── LICENSE
├── pyproject.toml
├── README.md
├── setup.cfg
├── src/
│   └── example_package/
│       ├── __init__.py
│       └── example.py
└── tests/
touch LICENSE
touch pyproject.toml
touch setup.cfg
mkdir src/mypackage
touch src/mypackage/__init__.py
touch src/mypackage/main.py
mkdir tests
```

## pyproject.toml 

This file tells tools like pip and build how to create your project

```
[build-system]
requires = [
    "setuptools>=42",
    "wheel"
]
build-backend = "setuptools.build_meta"
```
build-system.requires gives a list of packages that are needed to build your package. Listing something here will only make it available during the build, not after it is installed.

build-system.build-backend is the name of Python object that will be used to perform the build. If you were to use a different build system, such as flit or poetry, those would go here, and the configuration details would be completely different than the setuptools configuration described below.


# Setup.cfg setup
Using setup.cfg is a best practice, but you could have a dynamic setup file using setup.py

```
[metadata]
name = example-pkg-YOUR-USERNAME-HERE
version = 0.0.1
author = Example Author
author_email = author@example.com
description = A small example package
long_description = file: README.md
long_description_content_type = text/markdown
url = https://github.com/pypa/sampleproject
project_urls =
    Bug Tracker = https://github.com/pypa/sampleproject/issues
classifiers =
    Programming Language :: Python :: 3
    License :: OSI Approved :: MIT License
    Operating System :: OS Independent

[options]
package_dir =
    = src
packages = find:
python_requires = >=3.6

[options.packages.find]
where = src

```
# Running the build
### Make sure your build tool is up to date
Windows
```
py -m pip install --upgrade build
```
Linux/MAC OS
```
python3 -m pip install --upgrade build
```


### Create the build
```
py -m build
```













### References
https://packaging.python.org/tutorials/packaging-projects/