{ "info": { "author": "Cl\u00e9ber Zavadniak", "author_email": "cleberman@gmail.com", "bugtrack_url": null, "classifiers": [ "Development Status :: 3 - Alpha", "Intended Audience :: Developers", "Programming Language :: Python :: 3", "Programming Language :: Python :: 3.5", "Topic :: Software Development :: Libraries" ], "description": "#lazywf\n\nThe laziest web framework ever.\n\n[![CircleCI](https://circleci.com/gh/cleberzavadniak/lazywf/tree/master.svg?style=svg)](https://circleci.com/gh/cleberzavadniak/lazywf/tree/master)\n\n## Why I started this project\n\nI really enjoy working with **Django**. It's a very nice\nframework if you want to do some serious business without\nworrying too much about little details that won't help you\nat all to make your deliveries in time. It's opinionated\nand I think it's good. Except when I don't want to do\nanything \"serious\".\n\nReally, it's too difficult to get a Django project up and\nrunning. You have to deal with your \"settings.py\",\nconfigure where your templates are, enable static files\nserving, write your models upfront, create migrations,\nmigrate, write the views, then write the templates then\nrun the server and finally see nothing really happening\nbecause all you did was simply the skeleton of your\napplication and **now** you can start really making the\nthings happen as you wanted at first.\n\nWhat was that, again?\n\nMan, I don't have the patience to deal with so much only\nto put into life something very simple I want to play with.\n\n**I am too lazy!**\n\n## Django REST -ANYTHING- make everything even worse!\n\nAdd to all that the decision to have a REST API. Now I have\nto write serializers or specialized views, too.\n\n**Oh, no, God!, no!**\n\nI can't do that anymore. Really. Maybe when I was 20 years\nold, but not on my age...\n\n## Save your laziness on a DBMS\n\nSo, I decided to create a project using Bottle. But, where\nshould I save my data? Planning to run the app on Heroku, I\ncouldn't save things on the filesystem. So I found the\n\"dataset\" project and loved it. That was **exactly** what I\nneeded.\n\n## Models are still nice\n\nI like to design models. What I don't like is to write the\nmodels as code. Yes, you heard it. There should be a better\nway.\nSince \"dataset\" is very loose about data and I wanted some\nway of validating what was coming from the REST API, I\nfound it suitable to validate data using \"cerberus\". So I\nneeded some place to save the validation schemata, and\ndecided to use **YAML** for that, since JSON is too verbose\nand I am too lazy to comply with JSON strict rules (and\ntype all that innumerous '{' and '}' and ','...).\n\nAlso, model defining should be very simple. Your project\nmust have a \"models.yaml\" file on the root directory, from\nwhere models definition, some constraints and validation\nrules are going to be loaded.\n\nAnd that is it.\n\n## Example project using lazywf\n\nThere is an example project included on this repository.\nYou can copy it to use in your own project. It's as simple\nas it seems. ;-)", "description_content_type": null, "docs_url": null, "download_url": null, "downloads": { "last_day": -1, "last_month": -1, "last_week": -1 }, "home_page": "https://github.com/cleberzavadniak/lazywf", "keywords": "lazy web framework simple microframework", "license": "MIT", "maintainer": null, "maintainer_email": null, "name": "lazywf", "package_url": "https://pypi.org/project/lazywf/", "platform": "UNKNOWN", "project_url": "https://pypi.org/project/lazywf/", "project_urls": { "Homepage": "https://github.com/cleberzavadniak/lazywf" }, "release_url": "https://pypi.org/project/lazywf/0.1.0/", "requires_dist": null, "requires_python": null, "summary": "The laziest web framework ever", "version": "0.1.0" }, "last_serial": 2510796, "releases": { "0.1.0": [] }, "urls": [] }