On Jan 12, 2009, at 12:13 PM, Mike Orr wrote:
>
>> On Jan 8, 12:59 pm, mk <[email protected]> wrote:
>>> Hello everyone,
>>>
>>> I'm sad to report that QuickWiki as installed from pypi doesn't work
>>> with Pylons 0.9.7. I installed it using easy_install, followed the
>
> On Thu, Jan 8, 2009 at 10:52 AM, Thomas G. Willis <[email protected] 
> > wrote:
>>
>> My first guess would be Quickwiki is for 0.9.6 nad has not been
>> upgraded to be useful in 0.9.7 yet.
>
>
> I just saw this.  QuickWiki is out of date.


I have just taken a shot at getting this to work with:
- Pylons 0.9.7
- SQLAlchemy 0.5.2
- Evoque 0.4

and packaged the result as an easy_install-able distribution at:
http://pypi.python.org/pypi/QuickWikiEvoque

There are a few minor issues, that I have listed in the top-level  
README.

The "tutorial" text for this would still be the original page, at:
http://wiki.pylonshq.com/display/pylonsdocs/QuickWiki+Tutorial
except for obvious replacements as indicated above.

Most of the work is of course in the SQLAlchemy migration -- remapping  
this
part onto the original QuickWiki app should be straighforward. I could  
do also
pursue doing that if wished. Also, a review of the original tutorial  
text itself...

Anyhow, if anyone can look specifically over the SA parts and suggest  
more
exemplary usage it would be great.

> The specific problem
> probably means the three new middlewares are missing, as described in
> "What's New in Pylons 0.9.7?"
>
> http://docs.pythonweb.org/pages/viewpage.action?pageId=11174779

Ah, one of the issues I mention above is exactly about these now- 
required middlewares.

Cheers, mario



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" 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/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to