Re: Buglet: beaker gets data_dir='None' as string so can't use memory cache

[Ben Bangert]

On Jul 9, 2007, at 2:57 PM, Chris Shenton wrote:

Been away for a few weeks but this appears the root of Owen Davis'
"Session Issue" reported June 20:

http://www.mail-archive.com/pylons-discuss@googlegroups.com/ msg04306.html

If my pylons .ini file doesn't specify a setting for 'data_dir' then
beaker gets passed a data_dir variable whose value is the string
'None', which fails the test for the None value and beaker tries to
create a directory with this name.  In Owen's case (and the reason I
found this myself today) his process didn't have permissions to create
that dir.  You can workaround this, as Owen's responders mentioned, by
setting a writable directory for data_dir, e.g., '/tmp'.

But something's parsing the .ini file and setting data_dir to 'None'
instead of None, which should allow beaker to create a memory cache
instead of disk.  I'm too stupid to see where this is being done,
however. :-(

Perhaps this is fixed in SVN but I'm not sure which package is doing
this -- beaker, pylons, something else? I'm using pretty recent code:

Cheers,
Ben

Ah yes, a bug in how Pylons 0.9.5 was sending config variables into Beaker. Beaker was updated to handle this case as well, and was released tonight. It should remedy the problem with the options being read.

smime.p7s
Description: S/MIME cryptographic signature