I'm reluctantly giving up on turbogears / python for web stuff for the
time being :(

There are just too many missing functionalities that I need to
accomplish certain tasks - and perl has them already built into CPAN
modules or frameworks that are mature.

I'm way behind on a time sensitive deadline, and I don't have any more
time to extend and patch framework level functionality, so I need to
cut my losses with python and just give up and get this project back on
track.

That said, i was working on 2 functions/libraries that I planned on
finalizing for public release, and I believe some people on here were
already using them from my svn repo.  Obviously, i won't have the
ablity to finalize them now, so perhaps someone wants to take over?

Here are the items:

TurboGears Email Wrapper
       http://dev.2xlp.com/svn/turbogears_extensions/turboemail/
       pros:
         works with sendmail + smtp
         wraps a stdlib email object
         sends plaintext , html or plain+html multipart
         input can be raw string or templates piped to tg.view.render()

      cons:
         the wrapping doesn't handle headers, and the email object is
inaccesible.

      needed for public release:
         make the email a private object and fully expose the stdlib
features.  have defaults/sending/rendering/etc based on tg
         make a plugin or integrate into TG


TurboGears Captcha
      http://dev.2xlp.com/svn/another_python_captcha/

      pros:
         session based , time expired cookies using a mathmatical
function to provide authentication / solve
         can be used independant as a stand-alone server, using
get/post/json to create and validate keys

      cons:
         built on cherrypy, should be abstracted
         does not handle 1time use keys internally, but a
pre-validation check can do that

      needed for public release:
         abstract from cherrypy, make fully independant

If anyone wants them, let me know so I can freeze them in the svn repo
and xfer to you the appropriate licensing for it.  I don't like tossing
libraries into a public domain on a free-for-all, as I think current
contact info for a maintainer is pretty much essential in case of a
discovered security flaw.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---

Reply via email to