I am Pharaoh
I am Pharaoh is scaffold create to Django users which are starting with Pyramid.
Install:
pip install iampharaoh
After, verify your scaffold’s:
pcreate -l
Result:
Available scaffolds:
alchemy: Pyramid SQLAlchemy project using url dispatch
pharaohapps: Create an 'app' in project. - Like startapp Django
pharaohproject: Scaffold created for Django users initiate with Pyramid more comfortably
starter: Pyramid starter project
zodb: Pyramid ZODB project using traversal
Only pharaohapps and pharaohproject are created by I am Pharaoh, others are default in Pyramid
How to:
After install I am Pharaoh, start a new project
pcreate -s pharaohproject nameOfProject
The result in nameOfProeject folder is:
├── LICENSE ├── MANIFEST.in ├── README ├── nameOfProject │ ├── __init__.py │ ├── nameOfProject │ │ ├── __init__.py │ │ ├── base_model.py │ │ └── urls.py │ ├── scripts │ │ ├── __init__.py │ │ ├── destroydb.py │ │ └── initializedb.py │ └── static ├── development.ini ├── production.ini ├── setup.cfg └── setup.py
So, run in you project:
python setup.py develop
This command will download some packages, but the most significant for Django users are:
SQLAlchemy: The Python SQL Toolkit and Object Relational Mapper.
Alembic: Migrations.
WTForms-Alchemy: Forms and ModelForm.
pyramid_jinja2: Template Engine.
Create App
Whitin your project (Like Django):
pcreate -s pharaohapps nameOfApp
The result in nameOfProeject folder now is:
├── LICENSE ├── MANIFEST.in ├── README ├── nameOfProject │ ├── __init__.py │ ├── nameOfProject │ │ ├── __init__.py │ │ ├── base_model.py │ │ └── urls.py │ ├── nameOfApp -> add after run last command │ │ ├── __init__.py │ │ ├── models.py │ │ ├── templates │ │ │ └── index.html │ │ ├── urls.py │ │ └── views.py │ ├── scripts │ │ ├── __init__.py │ │ ├── destroydb.py │ │ └── initializedb.py │ └── static ├── development.ini ├── production.ini ├── setup.cfg └── setup.py
To connect app in project:
# nameOfProject/urls.py
config.include("nameOfProject.nameOfApp.urls")
Metadata
Release files for iampharaoh 0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iampharaoh-0.0.2.tar.gz | 7.7 kB | Without provenance | Details for iampharaoh-0.0.2.tar.gz |
Release files / iampharaoh-0.0.2.tar.gz
| Download URL | iampharaoh-0.0.2.tar.gz |
|---|---|
| Size | 7.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4a076ec1f0419d559d109dac21a4cb2c840da5783c7bd4722ba1f367342be5be
|
|
BLAKE2b-256 checksum How to use checksums |
421f76ce6fbebaf1d53a74beabc6765f653e9b15705e2fe720a5ea32b2b529c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for iampharaoh 0.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.