pkstruct 0.1.1__tar.gz → 0.1.2__tar.gz

pkstruct-0.1.2/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,46 @@
+---
+name: Bug Report
+about: Create a report to help us improve pkstruct
+title: '[BUG] '
+labels: bug
+assignees: ''
+---
+
+## Description
+
+A clear and concise description of what the bug is.
+
+## Reproduction
+
+```python
+# Minimal, runnable code that reproduces the issue
+```
+
+## Expected Behavior
+
+```python
+# What you expected to happen
+```
+
+## Actual Behavior
+
+```python
+# What actually happened (include full error output)
+```
+
+## Environment
+
+- Python version:
+- OS:
+- pkstruct version (pip show pkstruct):
+- Installed via: (pip / pipx / from source)
+
+## Additional Context
+
+Add any other context, screenshots, or ASCII visualizations here.
+
+## Checklist
+
+- [ ] I searched existing issues before filing this report
+- [ ] I am running the latest pkstruct version
+- [ ] This is a pkstruct bug, not a usage question

pkstruct-0.1.2/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Questions & Discussions
+    url: https://github.com/prnvvv/pkstruct/discussions
+    about: Ask usage questions and discuss ideas here
+  - name: Security Issues
+    url: https://github.com/prnvvv/pkstruct/security/policy
+    about: Report security vulnerabilities here (do not open a public issue)

pkstruct-0.1.2/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,37 @@
+---
+name: Feature Request
+about: Suggest an idea for pkstruct
+title: '[FEATURE] '
+labels: enhancement
+assignees: ''
+---
+
+## Problem
+
+A clear description of what problem this feature would solve.
+Ex: I'm always frustrated when [...]
+
+## Proposed Solution
+
+A clear description of what you want to happen, including API design if applicable.
+
+```python
+# Optional: sketch of the API you envision
+```
+
+## Alternatives
+
+Any alternative solutions or workarounds you've considered.
+
+## Scope
+
+- [ ] New data structure
+- [ ] New algorithm / method
+- [ ] Performance improvement
+- [ ] Documentation
+- [ ] Testing
+- [ ] Other (describe below)
+
+## Additional Context
+
+Any other context, references, or examples.

pkstruct-0.1.2/.github/pull_request_template.md

@@ -0,0 +1,29 @@
+## Description
+
+Please include a summary of the changes and which issue is fixed.
+
+Fixes #(issue)
+
+## Type of Change
+
+- [ ] Bug fix (non-breaking change)
+- [ ] New feature (non-breaking change)
+- [ ] Breaking change (fix or feature that changes existing API)
+- [ ] Documentation update
+- [ ] Performance improvement
+- [ ] Test addition/improvement
+- [ ] CI/infrastructure change
+
+## Checklist
+
+- [ ] Code follows project style (ruff passes)
+- [ ] Type hints added/updated (mypy passes)
+- [ ] Tests added/updated for new code
+- [ ] All existing tests pass (`python -m pytest`)
+- [ ] CHANGELOG.md updated for user-facing changes
+- [ ] Documentation updated if API changed
+- [ ] I have read the CONTRIBUTING.md guide
+
+## Additional Notes
+
+Any additional context, benchmark results, or design decisions.

{pkstruct-0.1.1 → pkstruct-0.1.2}/.gitignore

@@ -212,6 +212,7 @@ PKSTRUCT-INFO
 # Development artifacts
 # ==========================================
 *.history
+AGENTS.md
+requirements-dev.txt
 
-.github/
 .gitlab-ci.yml

{pkstruct-0.1.1 → pkstruct-0.1.2}/CHANGELOG.md

@@ -5,6 +5,22 @@ All notable changes to pkstruct will be documented in this file.
 The format follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.1.2] - 2026-06-16
+
+### Added
+- CONTRIBUTING.md, CODE_OF_CONDUCT.md, MAINTAINERS.md with project governance
+- Issue templates (bug report, feature request) and PR template
+- `py.typed` marker already present for PEP 561 compliance
+
+### Changed
+- README restructured: added "Why pkstruct?" section, removed maintainer-only publishing docs
+- pyproject.toml: updated author list with founders, expanded keywords, added classifiers
+- Badge URLs fixed to match `prnvvv/pkstruct` repository
+
+### Removed
+- AGENTS.md and requirements-dev.txt removed from repository (gitignored)
+- .github/ removed from .gitignore so templates are tracked
+
 ## [0.1.1] - 2026-06-02
 
 ### Added

pkstruct-0.1.2/CODE_OF_CONDUCT.md

@@ -0,0 +1,113 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes
+* Focusing on what is best for the overall community
+
+Examples of unacceptable behavior:
+
+* The use of sexualized language or imagery, and sexual attention or advances
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information without explicit permission
+* Other conduct which could reasonably be considered inappropriate
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards.
+They have the right and responsibility to remove, edit, or reject comments,
+commits, code, wiki edits, issues, and other contributions that are not
+aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies
+when an individual is representing the community in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+**conduct@pkstruct.dev**. All complaints will be reviewed and investigated
+promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of
+the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation, sustained
+harassment, or aggression toward individuals or classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

pkstruct-0.1.2/CONTRIBUTING.md

@@ -0,0 +1,133 @@
+# Contributing to pkstruct
+
+Thank you for your interest in contributing to pkstruct! This document provides guidelines and instructions for contributing.
+
+## Code of Conduct
+
+By participating, you agree to abide by our [Code of Conduct](CODE_OF_CONDUCT.md). Please report unacceptable behavior.
+
+## How to Contribute
+
+### Reporting Bugs
+
+1. Search [existing issues](https://github.com/prnvvv/pkstruct/issues) to avoid duplicates.
+2. Use the **Bug Report** issue template.
+3. Include:
+   - Python version and OS
+   - Minimal reproduction code
+   - Expected vs actual behavior
+   - Full error output if applicable
+
+### Suggesting Features
+
+1. Search [existing issues](https://github.com/prnvvv/pkstruct/issues) first.
+2. Use the **Feature Request** issue template.
+3. Explain the use case and why it belongs in pkstruct.
+
+### Questions
+
+Use the **Question** issue template or start a [Discussion](https://github.com/prnvvv/pkstruct/discussions).
+
+## Development Setup
+
+```bash
+git clone https://github.com/prnvvv/pkstruct.git
+cd pkstruct
+pip install -e ".[dev]"
+```
+
+## Coding Standards
+
+- **Python**: >= 3.10
+- **Type hints**: Required for all public APIs. Run `mypy src/pkstruct` — no errors allowed.
+- **Style**: Run `ruff check src/pkstruct` — no violations allowed.
+- **Line length**: 100 characters.
+- **Imports**: Use Ruff's import ordering (`I` rule set).
+
+### Rules
+
+- No `eval()` or `exec()`.
+- All mutable state must be protected by `threading.RLock`.
+- Public API methods must have type annotations and docstrings.
+- Internal/private methods prefixed with `_`.
+
+## Testing
+
+```bash
+# Run all tests
+python -m pytest
+
+# Run with coverage
+python -m pytest --cov=src/pkstruct
+
+# Run specific test file
+python -m pytest src/pkstruct/linear/tests/test_linked_list.py
+```
+
+- All new code must include tests.
+- Tests should cover normal paths, edge cases, and error conditions.
+- Test files go in the corresponding `tests/` directory.
+
+## Pull Request Process
+
+1. **Create an issue** first for bugs or feature requests (unless trivial).
+2. **Fork the repository** and create a branch from `main`:
+   ```
+   git checkout -b fix/issue-42-description
+   ```
+3. **Make your changes** following the coding standards.
+4. **Run tests** locally to ensure nothing is broken.
+5. **Run type checks** with `mypy src/pkstruct`.
+6. **Run linter** with `ruff check src/pkstruct`.
+7. **Commit** with a clear message:
+   ```
+   feat: add range_update to SegmentTree
+   fix: handle empty list in SinglyLinkedList.sort
+   docs: update README examples
+   ```
+8. **Push** and open a Pull Request.
+9. **Address review feedback** promptly.
+
+## Pull Request Checklist
+
+- [ ] Code follows style guidelines
+- [ ] Type hints added/updated
+- [ ] Tests added/updated
+- [ ] All tests pass
+- [ ] mypy passes with no errors
+- [ ] ruff passes with no violations
+- [ ] CHANGELOG.md updated (if user-facing change)
+- [ ] Documentation updated (if API change)
+
+## Review Expectations
+
+- Maintainers review within 5 business days.
+- Changes may be requested — this is normal.
+- Two approving reviews required for significant changes.
+
+## Project Structure
+
+```
+src/pkstruct/
+├── __init__.py          # Package root, registry, help()
+├── linear/             # Linked lists, stacks, queues, deques
+│   ├── linked_lists/
+│   ├── stacks/
+│   ├── queues/
+│   ├── deques/
+│   ├── tests/
+│   ├── utils/
+│   └── visualization/
+├── trees/              # BST, AVL, Red-Black, B-Tree, Fenwick, Segment, Interval
+│   ├── tests/
+│   └── visualization/
+├── graphs/             # Graph, DirectedGraph, algorithms
+│   └── tests/
+└── shared/             # Validators, serializers, threading, benchmarking
+```
+
+## Getting Help
+
+- Open a [Discussion](https://github.com/prnvvv/pkstruct/discussions)
+- Ask in issue comments
+- Tag `@prnvvv` for maintainer attention

pkstruct-0.1.2/MAINTAINERS.md

@@ -0,0 +1,62 @@
+# Maintainer Guide
+
+This document is for maintainers and release managers of pkstruct.
+
+## Project Leadership
+
+- **Founder & Maintainer**: [Prannavakhanth](https://github.com/prnvvv) — prannavakhanth12@gmail.com
+- **Co-Founder & Maintainer**: [Priyanka Kaliraj](https://github.com/pri-23-k) — pri2303k@gmail.com
+
+## Publishing a Release
+
+```bash
+# 1. Clean any previous builds
+rm -rf dist/
+
+# 2. Build distribution packages
+python -m build
+
+# 3. Verify distribution
+twine check dist/*
+
+# 4. Upload to PyPI
+twine upload dist/*
+
+# 5. Tag the release
+git tag v$(python -c "import tomllib; print(tomllib.load(open('pyproject.toml','rb'))['project']['version'])")
+git push origin --tags
+```
+
+## Before a Release
+
+- [ ] All tests pass: `python -m pytest`
+- [ ] Type check passes: `mypy src/pkstruct`
+- [ ] Lint passes: `ruff check src/pkstruct`
+- [ ] CHANGELOG.md is up to date
+- [ ] Version is bumped in `pyproject.toml`
+- [ ] README example code is verified against release
+
+## Versioning
+
+pkstruct follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html):
+
+- **Patch** (`0.1.0` → `0.1.1`): Bug fixes, minor improvements, no breaking API changes.
+- **Minor** (`0.1.0` → `0.2.0`): New features, deprecations, no breaking API changes (once stable).
+- **Major** (`1.0.0`): Breaking API changes.
+
+## Managing Issues
+
+- Apply appropriate labels: `bug`, `enhancement`, `question`, `good first issue`.
+- Respond to new issues within 48 hours.
+- Close resolved issues with a comment linking to the PR.
+
+## Managing Pull Requests
+
+- Review within 5 business days.
+- Ensure all CI checks pass before merging.
+- Use **Squash and Merge** for feature branches.
+- Update CHANGELOG.md when merging user-facing changes.
+
+## Security Vulnerabilities
+
+See [SECURITY.md](SECURITY.md) for the reporting process.

{pkstruct-0.1.1 → pkstruct-0.1.2}/MANIFEST.in

@@ -2,6 +2,8 @@ include README.md
 include LICENSE
 include CHANGELOG.md
 include SECURITY.md
+include CODE_OF_CONDUCT.md
+include CONTRIBUTING.md
 recursive-include src/pkstruct *.py *.pyi
 global-exclude __pycache__
 global-exclude *.py[co]

{pkstruct-0.1.1 → pkstruct-0.1.2}/PKG-INFO

@@ -1,12 +1,13 @@
 Metadata-Version: 2.4
 Name: pkstruct
-Version: 0.1.1
-Summary: Industrial-grade data structures and algorithms toolkit for Python
-Project-URL: Homepage, https://github.com/pkstruct/pkstruct
-Project-URL: Repository, https://github.com/pkstruct/pkstruct
-Project-URL: Documentation, https://pkstruct.readthedocs.io
-Project-URL: Bug Tracker, https://github.com/pkstruct/pkstruct/issues
+Version: 0.1.2
+Summary: A production-grade, open-source Python library providing comprehensive data structures and algorithms with type hints, thread safety, and extensive testing
+Project-URL: Homepage, https://github.com/prnvvv/pkstruct
+Project-URL: Repository, https://github.com/prnvvv/pkstruct
+Project-URL: Documentation, https://github.com/prnvvv/pkstruct#readme
+Project-URL: Bug Tracker, https://github.com/prnvvv/pkstruct/issues
 Author: pkstruct Contributors
+Author-email: Prannavakhanth <prannavakhanth12@gmail.com>, Priyanka Kaliraj <pri2303k@gmail.com>
 License: MIT License
         
         Copyright (c) 2026 Prannavakhanth
@@ -29,11 +30,13 @@ License: MIT License
         OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
         SOFTWARE.
 License-File: LICENSE
-Keywords: algorithms,collections,data-structures,dsa,linked-list
+Keywords: algorithms,avl-tree,b-tree,binary-search-tree,bplus-tree,collections,competitive-programming,data-structures,deque,dsa,fenwick-tree,graph,graph-algorithms,interval-tree,interview,linked-list,queue,red-black-tree,segment-tree,stack,tree
 Classifier: Development Status :: 5 - Production/Stable
 Classifier: Intended Audience :: Developers
 Classifier: Intended Audience :: Education
 Classifier: License :: OSI Approved :: MIT License
+Classifier: Natural Language :: English
+Classifier: Operating System :: OS Independent
 Classifier: Programming Language :: Python :: 3
 Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
@@ -60,12 +63,12 @@ Description-Content-Type: text/markdown
 
 # pkstruct
 
-**Industrial-grade data structures and algorithms for Python ≥ 3.10**
+**A production-grade, open-source Python library providing comprehensive data structures and algorithms with type hints, thread safety, and extensive testing.**
 
 [![PyPI](https://img.shields.io/pypi/v/pkstruct)](https://pypi.org/project/pkstruct/)
 [![Python](https://img.shields.io/pypi/pyversions/pkstruct)](https://pypi.org/project/pkstruct/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
-[![Tests](https://img.shields.io/badge/tests-898_✔️-success)](https://github.com/anomalyco/pkstruct)
+[![Tests](https://img.shields.io/badge/tests-899_✔️-success)](https://github.com/prnvvv/pkstruct)
 [![Type Checked](https://img.shields.io/badge/mypy-strict-blue)](https://github.com/python/mypy)
 [![Code Style](https://img.shields.io/badge/code%20style-ruff-000000)](https://github.com/astral-sh/ruff)
 
@@ -73,6 +76,15 @@ Description-Content-Type: text/markdown
 
 ---
 
+## Why pkstruct?
+
+| Need | pkstruct gives you |
+|------|-------------------|
+| **Interview prep** | Linked lists, trees, graphs with LeetCode-style helpers (palindrome, cycle detection, LCA, topological sort, etc.) |
+| **Production code** | Thread-safe structures (`threading.RLock`), strict type hints, 898+ tests |
+| **Learning DSA** | Consistent API across all structures, built-in ASCII visualization, runtime help system |
+| **Competitive programming** | Drop-in collection of trees (BST, AVL, Red-Black, Fenwick, Segment, Interval) and graph algorithms (Dijkstra, Kruskal, Tarjan, etc.) |
+
 ## 📦 Installation
 
 ```bash
@@ -734,15 +746,25 @@ run_full_benchmark()
 
 ---
 
+## 🤝 Contributing
+
+We welcome contributions! See [CONTRIBUTING.md](CONTRIBUTING.md) to get started.
+
+- [Code of Conduct](CODE_OF_CONDUCT.md)
+- [Issue Tracker](https://github.com/prnvvv/pkstruct/issues)
+- [Feature Requests](https://github.com/prnvvv/pkstruct/issues/new?template=feature_request.md)
+
+---
+
 ## 🔧 Development
 
 ```bash
 # Clone and install
-git clone https://github.com/anomalyco/pkstruct.git
+git clone https://github.com/prnvvv/pkstruct.git
 cd pkstruct
 pip install -e ".[dev]"
 
-# Run tests (898 tests)
+# Run tests (899 tests)
 pytest -v
 
 # Type check
@@ -752,14 +774,15 @@ mypy src/pkstruct
 ruff check src/pkstruct
 ```
 
-## 📦 Publishing
-
-```bash
-python -m build
-twine check dist/*
-twine upload dist/*
-```
+---
 
 ## 📄 License
 
 MIT © pkstruct Contributors
+
+## 🙌 Credits
+
+pkstruct is created and maintained by:
+
+- **Prannavakhanth** ([@prnvvv](https://github.com/prnvvv)) — Founder & Lead Maintainer
+- **Priyanka Kaliraj** ([@pri-23-k](https://github.com/pri-23-k)) — Co-Founder & Maintainer

{pkstruct-0.1.1 → pkstruct-0.1.2}/README.md

@@ -2,12 +2,12 @@
 
 # pkstruct
 
-**Industrial-grade data structures and algorithms for Python ≥ 3.10**
+**A production-grade, open-source Python library providing comprehensive data structures and algorithms with type hints, thread safety, and extensive testing.**
 
 [![PyPI](https://img.shields.io/pypi/v/pkstruct)](https://pypi.org/project/pkstruct/)
 [![Python](https://img.shields.io/pypi/pyversions/pkstruct)](https://pypi.org/project/pkstruct/)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE)
-[![Tests](https://img.shields.io/badge/tests-898_✔️-success)](https://github.com/anomalyco/pkstruct)
+[![Tests](https://img.shields.io/badge/tests-899_✔️-success)](https://github.com/prnvvv/pkstruct)
 [![Type Checked](https://img.shields.io/badge/mypy-strict-blue)](https://github.com/python/mypy)
 [![Code Style](https://img.shields.io/badge/code%20style-ruff-000000)](https://github.com/astral-sh/ruff)
 
@@ -15,6 +15,15 @@
 
 ---
 
+## Why pkstruct?
+
+| Need | pkstruct gives you |
+|------|-------------------|
+| **Interview prep** | Linked lists, trees, graphs with LeetCode-style helpers (palindrome, cycle detection, LCA, topological sort, etc.) |
+| **Production code** | Thread-safe structures (`threading.RLock`), strict type hints, 898+ tests |
+| **Learning DSA** | Consistent API across all structures, built-in ASCII visualization, runtime help system |
+| **Competitive programming** | Drop-in collection of trees (BST, AVL, Red-Black, Fenwick, Segment, Interval) and graph algorithms (Dijkstra, Kruskal, Tarjan, etc.) |
+
 ## 📦 Installation
 
 ```bash
@@ -676,15 +685,25 @@ run_full_benchmark()
 
 ---
 
+## 🤝 Contributing
+
+We welcome contributions! See [CONTRIBUTING.md](CONTRIBUTING.md) to get started.
+
+- [Code of Conduct](CODE_OF_CONDUCT.md)
+- [Issue Tracker](https://github.com/prnvvv/pkstruct/issues)
+- [Feature Requests](https://github.com/prnvvv/pkstruct/issues/new?template=feature_request.md)
+
+---
+
 ## 🔧 Development
 
 ```bash
 # Clone and install
-git clone https://github.com/anomalyco/pkstruct.git
+git clone https://github.com/prnvvv/pkstruct.git
 cd pkstruct
 pip install -e ".[dev]"
 
-# Run tests (898 tests)
+# Run tests (899 tests)
 pytest -v
 
 # Type check
@@ -694,14 +713,15 @@ mypy src/pkstruct
 ruff check src/pkstruct
 ```
 
-## 📦 Publishing
-
-```bash
-python -m build
-twine check dist/*
-twine upload dist/*
-```
+---
 
 ## 📄 License
 
 MIT © pkstruct Contributors
+
+## 🙌 Credits
+
+pkstruct is created and maintained by:
+
+- **Prannavakhanth** ([@prnvvv](https://github.com/prnvvv)) — Founder & Lead Maintainer
+- **Priyanka Kaliraj** ([@pri-23-k](https://github.com/pri-23-k)) — Co-Founder & Maintainer

{pkstruct-0.1.1 → pkstruct-0.1.2}/pyproject.toml

@@ -4,13 +4,25 @@ build-backend = "hatchling.build"
 
 [project]
 name = "pkstruct"
-version = "0.1.1"
-description = "Industrial-grade data structures and algorithms toolkit for Python"
+version = "0.1.2"
+description = "A production-grade, open-source Python library providing comprehensive data structures and algorithms with type hints, thread safety, and extensive testing"
 readme = "README.md"
 license = { file = "LICENSE" }
-authors = [{ name = "pkstruct Contributors" }]
+authors = [
+    { name = "Prannavakhanth", email = "prannavakhanth12@gmail.com" },
+    { name = "Priyanka Kaliraj", email = "pri2303k@gmail.com" },
+    { name = "pkstruct Contributors" },
+]
 requires-python = ">=3.10"
-keywords = ["data-structures", "algorithms", "linked-list", "dsa", "collections"]
+keywords = [
+    "data-structures", "algorithms", "dsa",
+    "linked-list", "stack", "queue", "deque",
+    "tree", "binary-search-tree", "avl-tree", "red-black-tree",
+    "b-tree", "bplus-tree", "segment-tree", "fenwick-tree", "interval-tree",
+    "graph", "graph-algorithms",
+    "competitive-programming", "interview",
+    "collections",
+]
 classifiers = [
     "Development Status :: 5 - Production/Stable",
     "Intended Audience :: Developers",
@@ -21,6 +33,8 @@ classifiers = [
     "Programming Language :: Python :: 3.11",
     "Programming Language :: Python :: 3.12",
     "Programming Language :: Python :: 3.13",
+    "Natural Language :: English",
+    "Operating System :: OS Independent",
     "Topic :: Software Development :: Libraries :: Python Modules",
     "Topic :: Education",
     "Topic :: Scientific/Engineering :: Information Analysis",
@@ -42,10 +56,10 @@ dev = [
 ]
 
 [project.urls]
-Homepage = "https://github.com/pkstruct/pkstruct"
-Repository = "https://github.com/pkstruct/pkstruct"
-Documentation = "https://pkstruct.readthedocs.io"
-"Bug Tracker" = "https://github.com/pkstruct/pkstruct/issues"
+Homepage = "https://github.com/prnvvv/pkstruct"
+Repository = "https://github.com/prnvvv/pkstruct"
+Documentation = "https://github.com/prnvvv/pkstruct#readme"
+"Bug Tracker" = "https://github.com/prnvvv/pkstruct/issues"
 
 [tool.hatch.build.targets.wheel]
 packages = ["src/pkstruct"]

pkstruct-0.1.1/AGENTS.md

@@ -1,38 +0,0 @@
-# pkstruct - Agent Guide
-
-## Test Suite
-Run all tests:
-```bash
-python -m pytest
-```
-Tests are in `src/pkstruct/{linear,trees,graphs}/tests/` (898 tests).
-
-## Architecture
-- **src-layout**: `src/pkstruct/`
-- **Build**: hatchling via `pyproject.toml`
-- **Python**: >= 3.10
-- **Python path**: `PYTHONPATH=src` (handled by pyproject.toml pytest config)
-
-## Key Files
-| File | Purpose |
-|------|---------|
-| `_str.py` | `StrMixin` - `__str__()`, `display(sep)`, `visualize()` |
-| `_help.py` | `HelpMixin` - dynamic help system |
-| `_linear_shortcuts.py` | `LinearShortcutsMixin` - `next()`, `prev()` |
-| `_tree_shortcuts.py` | `TreeShortcutsMixin` - `root()`, `parent()`, `children()`, `left()`, `right()`, `sibling()`, `visualize()` |
-| `linear/linked_lists/_base.py` | `_LinkedListBase` - shared LL logic |
-| `linear/linked_lists/nodes.py` | `SinglyNode`, `DoublyNode`, `CircularNode` |
-| `trees/node.py` | `TreeNode`, `AVLNode`, `RBNode`, `BTreeNode`, `BPlusNode` |
-| `graphs/graph.py` | `Graph` class |
-
-## Help System
-- `pkstruct.help()` → lists all structures
-- `pkstruct.help(ClassName)` → details + methods
-- `pkstruct.help("method_name")` → method docs across all classes
-- `instance.help()` / `instance.help("method")` / `instance.help(ClassName)`
-
-## Validating Changes
-Before/after editing, run: `python -m pytest --tb=short -q`
-
-## Git
-- No automated commits; use `git add -p` + `git commit` manually

pkstruct-0.1.1/requirements-dev.txt

@@ -1,9 +0,0 @@
-pytest>=7.4
-pytest-cov>=4.1
-pytest-xdist>=3.3
-pytest-benchmark>=4.0
-mypy>=1.7
-ruff>=0.1.6
-black>=23.11
-twine>=4.0
-build>=1.0