simpleweb-py-users — Mailing list for 'simpleweb'. A python wsgi compliant web framework.

[Simpleweb-py-users] [simpleweb-py commit] r5 - trunk/src/simpleweb/admin/plugins

[simpleweb-users <sim...@li...>]

Author: essiene
Date: Fri Jan 12 06:05:56 2007
New Revision: 5

Modified:
   trunk/src/simpleweb/admin/plugins/create_movable.py

Log:
admin/plugins/create_movable.py
	* Filter 'simpleweb.*' from packages. It appears running without simpleweb installed on target machine is still problematic
	* Setup hook to allow warning/messages when moving binary shared or static libraries

[Simpleweb-py-users] SVN Repo

[simpleweb-users <sim...@li...>]

I've setup the project on google code hosting.

http://code.google.com/p/simpleweb-py

Anonymous svn access is at http://simpleweb-py.googlecode.com/svn/trunk

I'll be hooking up the commit messages to show up on the mailing list.

Cheers,
Essien

[Simpleweb-py-users] simpleweb 0.7.2 in cheeseshop

[simpleweb-users <sim...@li...>]

Hi Everybody,

I'm please to annouce that I've just uploaded simpleweb-0.7.2 to cheeseshop.

What Is simpleweb
===================

simpleweb is simple python wsgi compliant web framework, inspired by 
Django, Turbo Gears and Web.py

simpleweb is a result of working closely with web.py, TurboGears, 
Django, and a very hefty dose of opinionation(tm) :)

Like TurboGears, it builds on existing python and wsgi components, to 
keep things simple, and just connects these components in a very easy 
transparent way.

Like web.py its dispatching mechanism is matched strictly to HTTP methods.

http://simpleweb.essienitaessien.com for details.

Major Changes In This Version
=============================

1. Dependencies reduction (simpleweb now has ONLY ONE non-optional 
dependency.

2. create-movable plugin. This will make the project folder self 
sufficient, and is able to be deployed WITHOUT installing any libraries 
on the target system. Not even simpleweb needs to be installed on the 
target machine!!!!

The website http://simpleweb.essienitaessien.com has been updated to 
reflect the changes.

With this new release, the recommended plot is:
	1 - Install simpleweb and its dependencies on development machine where 
developer probably controls python version, and library environment/site

	2 - When complete and ready for deployment, use simpleweb-admin 
create-movable, to create a self contained deployment folder. Deploy 
this self contained folder on the target hosting environment. This way, 
various versions of applications can be deployed with various versions 
of simpleweb.

	If you control the hosting environment, you can also choose to install 
simpleweb and dependencies system wide, and deploy normally. I'm now 
deploying the web app on http://simpleweb.essienitaessien.com this way.

I'll really appreciate tests and feedback. I'm not rushing to add more 
features for now, but will spend time to make these more robust.


ChangeLog 0.7.2 - Dependency Reduction Branch
======================================================
	* Add 'create-movable' plugin to simpleweb-admin
	* Initial work on dependency reduction
		* Introduced simpleweb.extlib [resolver, selector, yaro, memento, static]
		* All references to the above libraries are now internal
	* Made 'flup' an optional dependency
		* Dev server will warn of sessions not being available. If
		config.enable_sessions is set
		* FCGI deployment will send a msg to stderr, on non flup.servers.fcgi 
availability.
	* Made sqlobject, sqlalchemy and Cheetah optional dependencies 
attempting to enable
	them as plugins in config.py will cause an error alerting that they can't
	be used unless installed.
	* simpleweb.utils.optional_dependecies_err() -> to consistenly report
	issues
	* oh! modified the internal server banner again :)
	* utils.from_import() now properly raises exceptions instead of calling
	sys.exit()
	* simpleweb no more crashes if a controller specified in urls.py doesn't
	exist. It sends a warning to stderr instead. If an attempt is made to
	access that url, an HTTP 404 is raised.
	* unify error/info/warn reporting accross simpleweb with
	simpleweb.utils.msg_[err | warn | info]
	* Add SimpleErrorMiddleware, and use that to handle errors in
	SimplewebReloadingApp().
	* Correct the simpleweb-admin 'help' plugin to properly
		print help for create-movable plugin. Also, set
		ground-work for converting badly named plugins (e.g.
		createproject should be renamed to create-project, etc)

Re: [Simpleweb-py-users] simpleweb-admin createtables does not work

[simpleweb-users <sim...@li...>]

Hi All,

Just to keep you informed.

Edwin Nathaniel wrote:
> 
> PS: Minor complain: too many dependencies to be called "simpleweb". I'm 
> having a painful experience to install simpleweb and its dependencies 
> one by one behind company's firewall. It would be great if you could 
> write a tutorial on how to install simpleweb manually ^_^. Otherwise, 
> keep up the good job!

I have worked on the 'dependencies' problem. Currently, in my 
development source, for the next minor release (0.7.2), there is only 
ONE core dependency - wsgiref. All the others are optional, and their 
features only come alive as you install them. I'll have the docs updated 
and the release uploaded to pypi sometime tmrw lattest.

The idea is as follows:

1. Core dependencies that are part of simpleweb's core operation have 
been folded in (with permission from the Author(s)) - selector, 
resolver, static, memento, yaro, etc.

2. Other functionality are not so core:
	Sessions are provided via Flup. If not installed, simpleweb still 
works, just no sessions will be available.
	FCGI hosting is also provided via Flup. If not installed, hosting will 
fail, and error will be logged informing user to install flup first.

3. Plugin related dependencies are left to users choice.
	- sqlobject, sqlalchemy, cheetah are all used in the plugins only, 
attempting to configure them in config.py will fail if they are not 
properly installed.

I'll update the documentation on the site to reflect these changes.

Also, I'm trying to add a new simpleweb-admin plugin: 'movable'. The 
purpose of the plugin will be to analyse all the modules used by the 
application and pack them into a subfolder in the project, so the 
project can be run without doing any installations on say a shared host 
environment. The plugin status is:

1. Analyse all modules used - Done
2. Pack them into a local folder in the project (default is 
./site-packages) - Done
3. Filter out modules that already come with python - Not Done
4. Make the project use the ./site-packages as path of its sys.path - 
Not Done.

If I can get (4) above done by tonite, I'll also add this plugin in the 
upload for tmrw. Else, I'll skip it out, and do that for 0.7.3

Suggestions and or corrections are please welcome.

Cheers,
Essien

PS: Belated Merry Christmas and Happy New Year :)
> 
> 
> 

[Simpleweb-py-users] 0.7.1 - reloaded - API Break in config.py

[simpleweb-users <sim...@li...>]

Ok... you can tell i'm excited about this... I finally got Reloading 
working... had to really change some design around before 
memento.Assassin could help with the reloading.

Completed the 'config' object section of the Core Objects documentation 
on the site. http://simpleweb.essienitaessien.com/coreobjects

I'll have to put up the 'request' object section too.

0.7.1 is already on Cheeseshop.

I'll leave the code as it is for about a week to allow for stabilization 
and bug reports... there shouldn't be any bugs in deployment, but the 
reloading thing is quite a fragile thing in python, so there may be 
development stage bugs.

For the rest of the week, and most of next week, I'll be working on more 
documentation (and probably polishing the tutorial, so its a bit more 
structured and easier to follow? I saw comments on reddit that suggested 
that the tutorial wasn't very well written).

My next focus is goin to be on reducing the external dependencies needed 
to run install simpleweb. Its not going to be too easy, but I'm probably 
going to be shipping a distribution of simpleweb that comes with its 
core dependencies as part of it. This will be simple for things like 
selector, yaro, static, memento, resolver, but slightly difficult for 
things like SqlObject, SqlAlchemy, Cheetah. Anyways, I guess my work is 
cut out for me :)

ChangeLog 0.7.1 - API BREAK!!!
==============================
* API BREAK - config.py - host, port, user,
   group are now server_host, server_port,
   server_user, server_group

* Add default values for config.user and config.group
* Add some exception handling to make the
   user/group switching in the devserver more robust
* Add settings.Config.set_default_attr(), use this to clean up
   __init__.start(), default values are handled
   inside the object itself now.
* remove __init__.start() now redundant
* Change signature of plugins.runmethods functions. Now passing in
   urls and config for more loose-coupling.
* Default of config.host changed from '0.0.0.0'
   to '127.0.0.1' for security reasons.
* Corrected default value of config.user and
   config.guest (values where unquoted)
* Change internally used config.dirname to config.working_directory
* Use os.getcwd() to set config.working_directory, when   			 
settings.Config() is called. Formerlly was using
   config.__file__
* Filter out attributes special attributes
   (__file__, __cmd__, etc) from settings.Config() object
* Cleanup plugins/template.py to use config.working_directory
   as the Cheetah template base directory. Formerly guessing it with 
os.getcwd()
* Refactor out webserver.py from plugins.runmethods.development
* Add SimplewebReloadingApp()
* use memento.Assassin to call SimplewebReloadingApp(),
   now we can have internal server reloading if enabled
* Add new config key 'server_reload' to control internal server 
reloading default is True

Cheers,
Essien

[Simpleweb-py-users] website update

[simpleweb-users <sim...@li...>]

I've added some more docs on the website.

Teh beginning of the coreobjects tutorial: 
http://simpleweb.essienitaessien.com/coreobjects

A new howto showing how to use the new Controller Classes features:
http://simpleweb.essienitaessien.com/howtos/Classes_As_Controllers_Howto

questions, improvements, spelling errors (especially!!! i really s0k at 
spellings :P) are welcome.

I would have pushed out 0.7.1 today, lots of more refactorings, but I'm 
still having numberous issues trying to get reloading working :(

At any rate, solved or not, 0.7.1 will be out by Friday.

cheers,
Essien

[Simpleweb-py-users] simpleweb-0.7.0 released

[simpleweb-users <sim...@li...>]

simpleweb-0.7.0 has been released, and that marks the start of the 
0.7.XX branch.

At the end of this branch, we'll be more stable and robust. A lot of 
internal refactorings and cleanups have been done at 0.7.0, but more 
will follow. I started adding memento support, but due to how simpleweb 
works, I had to back out of it, and do the refactorings first. Reloading 
support will be added in the next few iterations of 0.7.XX.


ChangeLog 0.7.0
===============
* Refactorings -
	* add app.py in a bid to cleanup __init__.py
	* app.SimplewebApp
	* change the way deployment methods are handled. Now using 
plugins.runmethods
* Change the default value for __init__.run(method=None) to 
__init__.run(method='development')
* add optional config.setuid and config.setgid support in development 
server. Only affects POSIX operating systems. Modify default config.py 
template to reflect this. [Thanks to Sam Montgomery-Blinn]

* Oh... changed the dev-server prompt ;-)

* Added support for using classes as controllers. Now we can easily 
migrate old web.py apps over ;-)

cheers,
Essien

Re: [Simpleweb-py-users] simpleweb-0.6.11

[simpleweb-users <sim...@li...>]

On 12/11/06, Samuel Montgomery-Blinn <sa...@ca...> wrote:
>
> simpleweb-users wrote:
> > Version 0.6.11 uploaded to Cheeseshop.
> >
> > This version handles exceptions a bit better... especially ImportError
> > exceptions, so the user can see what happened better than previously.
> >
> > The idea behind the 0.6.XX series of updates, has been to fix bugs and
> > suggestions without adding new features as they come in, while working
> > on more documentation/features for the website.
> >
> > 0.7.XX branch will start soon with a bit more features (nothing drastic,
> > just things like addign support for dev server auto-restart, etc).
> >
> > Cheers,
> > Essien
> >
> >
> >
> -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> > opinions on IT & business topics through brief surveys - and earn cash
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>
> > _______________________________________________
> > Simpleweb-py-users mailing list
> > Sim...@li...
> > https://lists.sourceforge.net/lists/listinfo/simpleweb-py-users
> >
>
> I was wondering if for 0.7.XX, a tiny small thing would be useful to do:
>
> In simpleweb/__init__.py:
>
> make_server(config.host, config.port, app).serve_forever()
>
> I would suggest a small change here to allow the server to start on port
> 80 (requires root) and yet continue running as a non-root user:
>
> httpd = make_server(config.host, config.port, app)
>
> if (hasattr(config,'setgid')):
>   os.setgid(config.setgid)
> if (hasattr(config,'setuid')):
>   os.setuid(config.setuid)
>
> httpd.server_forever()
>
> (You have to setgid before calling setuid, or else you've already given
> up authority to call setgid.)
>
> But, in the end, it might not be worth putting any of that into the
> code, as I suppose it is expected that the user will not run the app in
> "production" using the wsgiref http server.


Actually... its not a bad idea to add. I have intentions of running some
small config type apps (think webmin type stuff) purely with the internal
server, so it won't be a bad idea to get the internal server to be more
robust. I'll definitely add this in. Want to work on the 'Core Objects' part
of the site today, so prolly won't do this till latter in the week. Also,
trying to get svn properly setup for the project, so we can start sending
and applying patches easily. :)

thanks for the excellent suggestion.

-Sam
>
>

[Simpleweb-py-users] simpleweb-0.6.11

[simpleweb-users <sim...@li...>]

Version 0.6.11 uploaded to Cheeseshop.

This version handles exceptions a bit better... especially ImportError 
exceptions, so the user can see what happened better than previously.

The idea behind the 0.6.XX series of updates, has been to fix bugs and 
suggestions without adding new features as they come in, while working 
on more documentation/features for the website.

0.7.XX branch will start soon with a bit more features (nothing drastic, 
just things like addign support for dev server auto-restart, etc).

Cheers,
Essien

Re: [Simpleweb-py-users] simpleweb-admin createtables does not work

[simpleweb-users <sim...@li...>]

Edwin Nathaniel wrote:
> Actually I have solved the problem. It as 100% careless on my part, I 
> did not install pysqlite module.
> 
> Thanks for your attention :-)

Oh cool. I've actually modified the way the exceptions where being 
handled and uploaded a newer version to cheeseshop, you can get that 
with easy_install -U simpleweb.

Cheers,
Essien
> 
> On 12/11/06, *Essien Ita Essien * <me...@es... 
> <mailto:me...@es...>> wrote:
> 
>     The problem here seems to be that simpleweb is swallowing the *real*
>     error and throwing up a misleading one. Another user Sam Montgomery had
>     this same problem and tracked it down to bad installation of sqlite on
>     windows.
> 
>     We'll probably need to put a nice SQlite Win32 howto on the Howto's
>     Section.
> 
>     cheers,
>     Essien
> 
>     Edwin Nathaniel wrote:
>      > Hi Essien,
>      >
>      > I've come to realize the problem lies in the line of:
>      >
>      > db_plugin = dblayer.SqlObjectDB('sqlite:%s' % (db_path))
>      >
>      > the db_path variable I got it from the code on your website from
>     Mervin
>      > Beng.
>      >
>      > I put 3 SQLite3 files on C:\WINNT\System32 (which are the
>     sqlite3.def,
>      > sqlite3.dll and sqlite3.exe)
>      >
>      >
>      > On 12/7/06, *Edwin Nathaniel* < xan...@gm...
>     <mailto:xan...@gm...>
>      > <mailto: xan...@gm... <mailto:xan...@gm...>>> wrote:
>      >
>      >     Hi Essien,
>      >
>      >     I'm testing on this simpleweb of yours. Here's what I've done
>     so far:
>      >
>      >     My project directory is: H:\works\python\www
>      >     I executed: simpleweb-admin createproject todolist
>      >     I went to: H:\works\python\www\todolist directory and all
>     files are
>      >     there including config.py
>      >     I modified config.py and models.py
>      >     I ran : simpleweb-admin createtables and it spits out the
>     "Can not
>      >     find config.py. Is this a valid simpleweb project directory?"
>     error
>      >
>      >     My platform is Windows XP SP2 running Python 2.4 with all
>     paths setup.
>      >
>      >
>      >     Thanks
>      >
>      >     PS: Minor complain: too many dependencies to be called
>     "simpleweb".
>      >     I'm having a painful experience to install simpleweb and its
>      >     dependencies one by one behind company's firewall. It would
>     be great
>      >     if you could write a tutorial on how to install simpleweb
>     manually
>      >     ^_^. Otherwise, keep up the good job!
>      >
>      >
>      >
>      >
> 
> 

Re: [Simpleweb-py-users] simpleweb-admin createtables does not work

[simpleweb-users <sim...@li...>]

Edwin Nathaniel wrote:
> Hi Essien,
> 
> Thanks
> 
> PS: Minor complain: too many dependencies to be called "simpleweb". I'm 
> having a painful experience to install simpleweb and its dependencies 
> one by one behind company's firewall. It would be great if you could 
> write a tutorial on how to install simpleweb manually ^_^. Otherwise, 
> keep up the good job!

Ok, I'll try to come up with a 'Installing Manually Howto' latter this week.
> 
> 
> 

Re: [Simpleweb-py-users] simpleweb-admin createtables does not work

[simpleweb-users <sim...@li...>]

The problem here seems to be that simpleweb is swallowing the *real* 
error and throwing up a misleading one. Another user Sam Montgomery had 
this same problem and tracked it down to bad installation of sqlite on 
windows.

We'll probably need to put a nice SQlite Win32 howto on the Howto's Section.

cheers,
Essien

Edwin Nathaniel wrote:
> Hi Essien,
> 
> I've come to realize the problem lies in the line of:
> 
> db_plugin = dblayer.SqlObjectDB('sqlite:%s' % (db_path))
> 
> the db_path variable I got it from the code on your website from Mervin 
> Beng.
> 
> I put 3 SQLite3 files on C:\WINNT\System32 (which are the sqlite3.def, 
> sqlite3.dll and sqlite3.exe)
> 
> 
> On 12/7/06, *Edwin Nathaniel* < xan...@gm... 
> <mailto:xan...@gm...>> wrote:
> 
>     Hi Essien,
> 
>     I'm testing on this simpleweb of yours. Here's what I've done so far:
> 
>     My project directory is: H:\works\python\www
>     I executed: simpleweb-admin createproject todolist
>     I went to: H:\works\python\www\todolist directory and all files are
>     there including config.py
>     I modified config.py and models.py
>     I ran : simpleweb-admin createtables and it spits out the "Can not
>     find config.py. Is this a valid simpleweb project directory?" error
> 
>     My platform is Windows XP SP2 running Python 2.4 with all paths setup.
> 
> 
>     Thanks
> 
>     PS: Minor complain: too many dependencies to be called "simpleweb".
>     I'm having a painful experience to install simpleweb and its
>     dependencies one by one behind company's firewall. It would be great
>     if you could write a tutorial on how to install simpleweb manually
>     ^_^. Otherwise, keep up the good job!
> 
> 
> 
> 

Re: [Simpleweb-py-users] simpleweb: mailing list and source code repository

[simpleweb-users <sim...@li...>]

Juan Manuel Caicedo wrote:
> Hi
> 
> I just found today simpleweb and I think it's really interesting. I
> just had a few problems with the dependencies but I could solve them
> easily.

Good you could solve them. Is this something I could help by adding some 
more info on the site or via easy_install? Any more info will be 
appreciated.

> 
> Is there a mailing list for the users? 

There is now.

It would be nice to have also a
> repository for the source code; btw,
> http://code.google.com/p/simpleweb/ is available.

When I tried registering that last week, it conflicted with a 
sourceforge project also named simpleweb (google hosting works closely 
with sourceforge and doesn't allow you to create projects on Ghosting 
that will cause name conflicts with sourceforge).

I'll be importing into svn in a little while, either on sourceforge or 
on google hosting. Not sure which one yet. Any ideas?
> 
> I also had problems finding your email address, that's why I think
> having a mailing list is important.

done now. thnx :)

> 
> Regards
> 
> Juan Manuel Caicedo
> 

Re: [Simpleweb-py-users] simpleweb: example typo

[simpleweb-users <sim...@li...>]

> 
> On 12/9/06, *Samuel Montgomery-Blinn* <sa...@ca... 
> <mailto:sa...@ca...>> wrote:
> 
> 
>     Not a very great first contribution from me, but:
> 
>     http://simpleweb.essienitaessien.com/example
> 
>      > There is currently only *intergrated* support for Cheetah, but you
>     don't even need to have another system integrated to use it.
> 
>     The second spelling of integrated is the correct one, the first one
>     (inte*r*grated) has an extra "r".

Thanks. correction applied now.

> 
>     Thanks for making Simpleweb available, it is quite interesting so far.
>     I'm so very happy to have a simple, clean framework that includes a
>     basic role-based authentication in it -- I'm hoping to simply use OpenId
>     for user/password, have you tried to set this up with Simpleweb yet?
> 
>     -Sam

No. I've not tried this, but I don't think it should be difficult. The 
trick will be to authenticate with OpenID before calling 
config.auth_plugin.set_session_user(). Also, does open ID allow 
transparent support for roles? If not, you'll probably have to still 
maintain an OpenID_User to Your_App_Roles mapping, then after the 
open-id auth step is successfull, you grab the role from your mapping 
table, and call set_session_user.
> 
> 

[Simpleweb-py-users] test2

[simpleweb-users <sim...@li...>]

test2

[Simpleweb-py-users] test

[Mailing l. f. u. of 's. <sim...@li...>]

test :)