Pyramid 1.3a9 has been released. 1.3a9 is another alpha in the 1.3
series; it has some features and a few bug fixes. Here's what
happened:
1.3a9 (2012-02-22)
==
Features
- Add an ``introspection`` boolean to the Configurator constructor.
If this is ``True
Hi Vanasco,
This is a generic FormEncode question so you should ask on the FormEncode
list. I copied that list on this email. The FormEncode list is pretty low
volume, but the maintainers do respond ;).
You might want to include what you want as your final state (for instance I
assume you want in
Two possible alternatives
# if you had another reason for a list comprehension
def unicode_wrap(listed):
return [ unicode(i) for i in listed ]
def unicode_wrap(listed):
return map(unicode, listed)
--
You received this message because you are subscribed to the Google Groups
"pylons-di
the request get/post data comes in from pyramid as unicode strings.
the values i have in the database / my code for constant on many items
are integers
let's use this as an example...
account_type_ids= (1,2,3,4,5)
other_type_ids= (1,2,3,4,5)
third_type_ids= (1,2,3,4,5)
is there a bet
>
> I'm pleased to report that we've seen $2813.00 contributed so far via
> ChipIn, which is a little over 50% of our goal. This is great.
>
>
Awesome! Just did my $50.00
Iain
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this g
Sorry, you mentioned your version of the docs in response to a similar
comment that I made and I didn't reply.
I did find your explanation very helpful in breaking down the explanations
into digestible chunks - I'd very much support that yours should be merged
into the main documents.
Ben
On 22
On Wed, Feb 22, 2012 at 11:31 AM, Jonathan Vanasco wrote:
>
> 1. A nice paragraph or two giving an overview of the scope / style of
> Security that is offered , and why you might want to use it. ( even
> the first bit of
> http://readthedocs.org/docs/pyramid/en/1.0-branch/narr/security.html
> is to
Just wanted to add to this discussion , for potential things to
address in the docs:
The security authorization/authentication stuff is a bit intense.
At first glance, it looks and reads very much like an "enterprise
software" type of system, with a lot of overhead. If I were building
a CMS or a
The only problem that I see with this is if you want to remove a user from
a group it's not going to propagate to your application immediately unless
you remember to clear that cache at the same time. This could be a security
issue if you remove a user's credentials and they are still able to ac
It's ok cache the user groups? like
@cache.region('short_term', 'groupfinder')
def groupfinder(...):
Or it's better approach use the session, to check the user info is in
the user session, before invoke the sqlalchemy machinery?
Greetings.
--
You received this message because you are sub
10 matches
Mail list logo