pulse-framework 0.1.0__tar.gz

pulse_framework-0.1.0/.claude/settings.local.json

@@ -0,0 +1,9 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(mkdir:*)"
+    ],
+    "deny": [],
+    "ask": []
+  }
+}

pulse_framework-0.1.0/.gitignore

@@ -0,0 +1,173 @@
+node_modules/
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# PyPI configuration file
+.pypirc

pulse_framework-0.1.0/.python-version

@@ -0,0 +1 @@
+3.13

pulse_framework-0.1.0/.vscode/settings.json

@@ -0,0 +1,11 @@
+{
+  "files.associations": {
+    "*.css": "tailwindcss"
+  },
+  "editor.quickSuggestions": {
+    "strings": "on"
+  },
+  "tailwindCSS.includeLanguages": {
+    "python": "javascript"
+  }
+}

pulse_framework-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Erwin Kuhn
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

pulse_framework-0.1.0/PKG-INFO

@@ -0,0 +1,38 @@
+Metadata-Version: 2.4
+Name: pulse-framework
+Version: 0.1.0
+Summary: Pulse - Full-stack framework for building real-time React applications in Python
+License-File: LICENSE
+Requires-Python: >=3.11
+Requires-Dist: fastapi>=0.104.0
+Requires-Dist: mako>=1.3.10
+Requires-Dist: python-socketio>=5.13.0
+Requires-Dist: rich>=13.7.1
+Requires-Dist: textual>=5.2.0
+Requires-Dist: typer>=0.16.0
+Requires-Dist: uvicorn>=0.24.0
+Requires-Dist: websockets>=12.0
+Description-Content-Type: text/markdown
+
+# Pulse
+
+
+> [!WARNING]
+> Pulse is currently very early and absolutely not production-ready. I am currently piloting it for internal usage. I do not recommend it using it for an application at this stage, as project support in the CLI is non-existent and you will likely encounter problems.
+
+Pulse is a full-stack Python framework to build React applications. It aims to be the best way to build complex web applications from Python.
+
+Pulse's guiding principles are:
+- Straightforward code, it's "just Python". Pulse tries really hard to avoid surprises and magic.
+- Performance. Your app should respond to user interactions as fast as the speed of light allows. Your dev workflow should be the same: fast starts and instant reloads.
+- Extremely easy integration with the JavaScript and React ecosystems. Want to install a library and use its React components from Python? Want to add your own custom React components to your project? You got it. 
+
+## Project structure
+
+A Pulse project has two parts:
+- The Pulse Python server, where most of your application is defined.
+- The React application, using [Vite](https://vite.dev/) and [React Router](https://reactrouter.com/home). Pulse generates routes and runs the app for you, but you are free to modify and extend the project as you wish.
+
+You can see an example in the `pulse-demo/` folder. Typically, a Pulse project contains the Python server at the top-level and the React application in a subfolder, named `pulse-web/` by default. This is not a prescription however, you can configure Pulse to have the React application anywhere you want it.
+
+Pulse's CLI is currently limited to running the Pulse application, or just generating the Pulse routes in the React application. There are no utilities to help with project setup. If you want to use Pulse, you will need to install the `pulse-ui-client` package from NPM and the `pulse` Python package from Git, and imitate the setup in `pulse-demo/` yourself.

pulse_framework-0.1.0/README.md

@@ -0,0 +1,22 @@
+# Pulse
+
+
+> [!WARNING]
+> Pulse is currently very early and absolutely not production-ready. I am currently piloting it for internal usage. I do not recommend it using it for an application at this stage, as project support in the CLI is non-existent and you will likely encounter problems.
+
+Pulse is a full-stack Python framework to build React applications. It aims to be the best way to build complex web applications from Python.
+
+Pulse's guiding principles are:
+- Straightforward code, it's "just Python". Pulse tries really hard to avoid surprises and magic.
+- Performance. Your app should respond to user interactions as fast as the speed of light allows. Your dev workflow should be the same: fast starts and instant reloads.
+- Extremely easy integration with the JavaScript and React ecosystems. Want to install a library and use its React components from Python? Want to add your own custom React components to your project? You got it. 
+
+## Project structure
+
+A Pulse project has two parts:
+- The Pulse Python server, where most of your application is defined.
+- The React application, using [Vite](https://vite.dev/) and [React Router](https://reactrouter.com/home). Pulse generates routes and runs the app for you, but you are free to modify and extend the project as you wish.
+
+You can see an example in the `pulse-demo/` folder. Typically, a Pulse project contains the Python server at the top-level and the React application in a subfolder, named `pulse-web/` by default. This is not a prescription however, you can configure Pulse to have the React application anywhere you want it.
+
+Pulse's CLI is currently limited to running the Pulse application, or just generating the Pulse routes in the React application. There are no utilities to help with project setup. If you want to use Pulse, you will need to install the `pulse-ui-client` package from NPM and the `pulse` Python package from Git, and imitate the setup in `pulse-demo/` yourself.