lease access to dependencies such as Routes, WebError, Paste, and such?
I finally just released a new WebError, Routes, and Pylons, and have
obviously not had the time to properly devote to legacy maintenance so I'd
be thrilled with some active ppl coming on to continue.
Cheers,
Ben
On Mon, Ju
lons 1.0, there should be no backwards compatibility issues
(short of any changes to WebOb that might affect you).
Cheers,
Ben
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-devel@googleg
tabase-backed sessions. Patch by Vladimir
Tananko.
* Fix issue with long key names in memcached backend. Patch by Guillaume
Taglang.
Cheers,
Ben
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email
ylonsproject.org/projects/pyramid/en/latest/narr/renderers.html
because none of them have routes defined in the view_config decorator.
Is there a way to add a route to a view_config-decorated view when the
view doesn't have a route name?
--
Ben Sizer
--
You received this message because
n viewresult_to_response
raise ValueError(msg % (view_description(view), result))
ValueError: Could not convert return value of the view callable
function __main__.hello_world into a response object. The value
returned was {'content': 'Hello!'}. You may have forgotten to def
elp to
StackOverflow to see if their problem has a solution there, and if not have it
solved there instead of on the mail list?
Then we could just nuke pylons-dev, and have a single pylons-discuss where all
Pylons Project related topics are discussed, and refer people with more
'support&#x
rested in looking at development related
things, being able to see just that at once is very useful. Of course, it'd
also be useful if Mail Lists supported tags/categorization so its easier to
filter but ah well.
Cheers,
Ben
--
You received this message because you are subscribed t
I have a question about putting async form submitting and pyramid
default authentication together.
My sign up and sign in form is doing async form submitting, in the
back end, if there is something wrong, I return a json message with
all error messages, but when the form data is correct, I tried t
can! In fact, several of us have the commit rights needed. :)
Deprecating the old one is definitely an option.
Cheers,
Ben
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.com.
; given its already a well
known name that people already associate with this exact thing? I mean, I can
see how 'blueprint' can technically be a more accurate term, but existing
re-use of the name and lack of anyone already associating it with this seems
like a point against it.
Cheers,
or template languages? Is that a real problem? I'm just not
sure
I've been doing Pylons for a long time, and we generally do say 'paster
templates' and no one thus far has ever gotten confused afaik. But hey, its a
fun bike-shed, eh? :)
Cheers,
Ben
--
You received this mes
framework.
I know quite a few people coming to Python from the Rails world immediately
search around looking for where the equivilant 'scaffolding' is for their
projects.
Cheers,
Ben
--
You received this message because you are subscribed to the Google Groups
"pylons-devel&
ose to CherryPy's, which is great
considering it does a bit more to avoid memory leaks, stuck threads, etc.
- Ben
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.co
crease and less latency (generally starts to match CherryPy's
server then):
http://groups.google.com/group/paste-users/browse_thread/thread/b2afc88a86caade1
http://stackoverflow.com/questions/1781766/paste-httpserver-and-slowdown-with-http-1-1-keep-alive-tested-with-httperf-and-a
Cheers,
Ben
-
and don't continue it on
pylons-devel. Odd's are there's more people that will benefit as the
pylons-discuss list is substantially larger in membership then the devel one.
Again, sorry about the confusion and delay in updating the Pylons Project pages
to indicate the appropriate
r could use
the stolen cookie to do a GET/POST with a new CSRF token as the other user.
Thus any additional rotation of the CSRF token seems a bit overkill and more
prone to cause situations where a user might hit the back button and try to
re-submit a form causing them to see a CSRF error and think
ing that out! We're fixing that asap. :)
Cheers,
Ben
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.com.
To unsubscribe from this group, send email to
pylons-devel+unsubs
Yah, I was asking about Pyramid. Thanks a lot!
-Ben
On Mar 7, 9:51 am, Michael Merickel wrote:
> Assuming you're asking about Pyramid, the settings are accessible through
> the request object.
>
> settings = request.registry.settings
> secret = settings['
__init__.py file.
Thanks!
-Ben
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.com.
To unsubscribe from this group, send email to
pylons-devel+unsubscr...@googlegroups.com
the Pyramid framework, and
infrastructure development. You'll generally recieve more input on issues on
the pylons-discuss list as its much larger.
Cheers,
Ben
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group,
Hi, I am trying to do the similar thing.
It works if I use config.add_route()
but if I use @view_config, it does not work me and keeps complaining
that it cannot find renderer
what is the problem?
Thanks
On Mar 4, 4:27 pm, Mengu wrote:
> for development, i recommend you using paster. you can
as
well. :)
Cheers,
Ben
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.com.
To unsubscribe from this group, send email to
pylons-devel+unsubscr...@googlegroups.co
;s the most efficient way I can do that with currently available software?
>
> What version of webhelpers should I use? Are there any changes to the query I
> should make to make it more efficient?
The current Paginate in webhelpers can do that just fine.
Cheers,
Ben
--
You received
bOb request
would be sufficient to get the current location *and* generate the appropriate
link to the next page.
As for handling offset vs using a last key, it might make more sense to make a
better API for the object passed in then the sequence slice operation I had
imagined earlier.
Cheers,
Ben
next iteration. Also, to require the object
being paginated to support the Python sequence API, so that the hacky code that
tries to deal with various SQLA things isn't needed. Ie, there'd be some
sequence wrappers for SQLA query objects vs. a bunch of if/else code toggling
it inside the pagina
cases = cases.filter(cls.id.in_(judge_case_ids(judge)))
It's quite easy to dynamically build up the filter conditions, dynamically
include additional table joins as needed, etc.
Cheers,
Ben
--
You received this message because you are subscribed to the Google Groups
"pylon
On Dec 30, 2010, at 11:29 AM, Gael Pasgrimaud wrote:
> I've already tried to contribute but my changes was never merged.
>
> Maybe you can use this changeset:
> https://bitbucket.org/gawel/webob/changeset/ed29414cd65b
Thanks Gael! I've pulled and merged your test a
ulated so making a view registration
that requires 'name' will cause it to not be found during view lookup.
Cheers,
Ben
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-de...@goog
On Nov 24, 2010, at 3:13 PM, Mike Orr wrote:
> Why a list of sessions? That doesn't seem to give much control over
> which session you get.
It wasn't intended to. That was just so I wouldn't need to do 'global
db_session' inside the configure function.
- Ben
ble to get to the session, or to ensure the
engine is configured and bound first.
The main advantage to having the package is that since one doesn't need to
import anything from their own models during config, reflective tables are
easier. As you mention, you don't use table reflectio
x27;write_master', prefix='sqlalchemy.write.',
immediate_bind=False)
Then its up to the user during runtime to use get_dbengine and re-bind the
session during the request if they want to change to the write master, etc.
Cheers,
Ben
--
You received this message because you a
more SQLAlchemy knowledge, and pyramid_sqla would
only be making it easy to register engines/sessions and get to them from
anywhere else.
> 3) There are really several ways to structure large apps with multiple
> databases, such as multiple session objects as Ben last described. I
> do
how its acquired could then be updated later instead of
having a 'DBSession' object hardcoded at module scope in pyramid_sqla.
Cheers,
Ben
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to
emy that will let
people make more assumptions about some basic SQLA things. For example, maybe
the setup_dbsession command in the future might trigger an event
"DBInitialized" that other event listeners might be waiting for to do
something, etc.
> Likewise, I can make a 'pyra
sufficient.
Sounds good.
> I don't think this is useful. A single file app would never live in a
> package. There's no purpose in providing a template to generate a
> single-file app.
Indeed, strike that. :)
Cheers,
Ben
--
You received this message because you are subsc
ion how to set it up, or the people using zodb
with pyramid_zodb can have a template in that package that comes with it setup.
Cheers,
Ben
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email
ther packages that provide other templates will then be responsible for
documenting it. pyramid_sqla also means there's a point to build additional
sets of functionality that assist with SQLAlchemy usage in Pyramid that would
help for those who want to make bits that assume you're usin
ator, it won't work
in the add_handler call because all additional keyword args to add_handler go
to add_route (and permission is something you want for the add_view which
@action will use).
Cheers,
Ben
--
You received this message because you are subscribed to the Google Groups
"p
o be able to specify a
regex for its part so you didn't have to manually type it over and over again.
I don't want to be typing it over and over again, and its nice to have the
converter specify some basic minimum set of requirements that can be taken care
of in the regex match *bef
ich it supposedly has a clue what would be a valid conversion...
- Ben
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-de...@googlegroups.com.
To unsubscribe from this group, send email to
pyl
hives/{month:month_conv}'...)
Which I guess is fine, and as you mention it does avoid the ambiguity by making
it explicit that something else is happening with the marker.
I do anticipate ppl using the routehelper as a 'partial', which is why many
like the context manager aspect, li
)
In my experience, lots of people end up repeating themselves a ton as their
marker names frequently require the same regular expression and type coercion.
It'd be nice to have that all taken care of without clouding up the view code.
Any thoughts on converters or being able to register d
on
* pyramid_feeds - Template renderer that provides feed output support, ie
'atom', or 'rss2' and will handle taking a dict like current renderers, but
spit out a feed
* pyramid_paginate - Flexible pagination helper for sequences like the current
paginate
The most impor
On Nov 18, 2010, at 8:11 AM, Mike Orr wrote:
>> That said, I didn't personally consider the case where the desired
>> return value of the pattern "/:x_html" might be {'x':'foo'} instead of
>> {'x_html':'foo_html'} when th
ert/webhelpers/issues?status=new&status=open
Cheers,
Ben
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-de...@googlegroups.com.
To unsubscribe from this group, send email to
pylons-devel+
ast few months, I've been collaborating pretty meaningfully with
Ben Bangert, the lead developer of the Pylons (http://pylonshq.com) web
framework. This collaboration started because Ben and I have "competing" web
frameworks, both written in Python. Our repoze.bfg and Ben's Pylo
response.content_type = 'application/vnd.mozilla.xul+xml'
return response
> There is also a render_template_to_response() function somewhere,
> maybe in pylons.templating. It fills a template and creates a response
> and returns it.
Yup.
Cheers,
Ben
-
#x27;t transitioning all that quickly.
There is no book for the new Pylons paradigms yet, so you'll see a much higher
level of 'support' in the way of blog postings, and documentation for 1.0 for
some time to come I believe.
Cheers,
Ben
--
You received this message because you
On Sep 20, 2010, at 10:17 PM, Mike Orr wrote:
> How many full-time staff do you have available for two months? Just
> converting the hundreds of references to plain text would take hours,
> plus rewording the hundred-some pages of BFG docs and hundred-some
> other docs and a few more for SQLAlchem
foreign cross-references. Can that be done as a Sphinx
> plugin?
That sounds like it might be more effort than just copy/pasting the bits we
need in, and ensuring their docs flow well with the rest of the Pylons docs.
- Ben
--
You received this message because you are subscribed to the Google
disconnect when someone add's
things to tmpl_context in one case, but then it gets dropped in as a template
global under the 'renderer=' scenario. Having everything a person wants to pass
in, always go in under tmpl_context seems more consistent.
- Ben
--
You received this message because
On Sep 19, 2010, at 6:36 PM, Ben Bangert wrote:
BTW, for anyone else that just saw this message appear apparently out of the
blue, Google Groups does have the full thread but failed to e-mail it out. To
catch up, just go to:
http://groups.google.com/group/pylons-devel/browse_thread/thread
ake.
> Do you mean just changing the message to "ImportError: please install
> the 'formencode' package", or something more elaborate?
Well, no, I just mean that it'll only define the legacy things if
formencode is present. So that its not actually required to inst
on in the API docs, and that lists all the functions/classes/modules you
should need to know about for everything that is 'session' related. I get the
distinct impression this would help people find the right
module/class/function, since right now ppl end up asking these questions on the
27;re
using new things.
> But if the try/excepts have to be in the application, we're kind of
> screwed, because we can't go auto-modifying people's applications and
> breaking them.
No, I meant in the places where Pylons is importing WebHelpers and FormEncode,
On Sep 12, 2010, at 3:39 PM, Chris McDonough wrote:
> Most of this is already handled via "paster points", e.g. do
> "env/bin/paster points paste.filter_app_factory" in a virtualenv that
> has Pylons installed. What that doesn't do is give you the "egg name",
> although you don't really need the
ile is where
settings and the application wrappers are configured, which can differ between
production, staging, testing, and deployment, while the make_app is where the
application itself is configured.
- Ben
--
You received this message because you are subscribed to the Google Groups
&q
n't gone through the Pylons code or BFG code or BFG manual
> yet; I just went with "it must be so in order for the application code
> to work", based on an earlier email exchange with Ben about the
> application structure. The emails are also included for reference on a
>
e planned for Pylons post-1.0, so I'll be writing up a blog post in the next
few days outlining a rough future roadmap for where Pylons is going, and what
new features are planned.
Cheers,
Ben Bangert
--
You received this message because you are subscribed to the Google Groups
"pylons
be added to the "How to upgrade" page.
Yep, thanks! I've updated the upgrading page to include this.
Cheers,
Ben
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-de...@googleg
s and its various components what they are today.
- Ben
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-de...@googlegroups.com.
To unsubscribe from this group, send email to
pylons-devel+
nge @validate before 1.0 or if we should just release 1.0 now with
the legacy removal stuff and the few bugfixes that have come up since 0.9.7.
Changing @validate now would break a ton of code for 1.0. Maybe rather than fix
@validate, we should consider deprecating it entirely post-1.0 and move
h' to
traversal (repoze.bfg/zope style, though for backwards compat with
TG2, could use a CherryPy style traverser)
Anyways, that's about where we are now, and we're now working on some
code to play with these thoughts and see how they pan out.
Cheers,
Ben
--~--~-~--~--
. Once Sphinx can generate it, I can go ahead and replace
the routes.groovie.org site with it.
Anyone up for these tasks, or interested in updating the pylons/docs
based on the comments, or fixing any website bugs?
Cheers,
Ben
--~--~-~--~~~---~--~~
You received this m
On Jun 21, 2009, at 12:40 PM, Iain Duncan wrote:
>> I don't know what Ben has up his sleeve but I think the core is
>> essentially done with 0.9.7. The main incremental changes are on the
>> periphery: improve @validate, replace @beaker_cache, improve the
>> depen
se it when available?
Cheers,
Ben
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.com
To unsubscribe from this group, send e
llers/
> core.py
Is this because functions are being dynamically added/removed from the
controller, and the cached inspect is holding onto them? Any
elaboration on what exactly is occurring?
Cheers,
Ben
--~--~-~--~~~---~--~~
You received this message becau
used with a Pylons decorator, that drops in a
unique token into a form to prevent CSRF attacks. I can see a similar
Pylons decorator, with a WebHelper generator that would make it easy
to drop in optional use of your system for anyone making a login form.
Cheers,
Ben
smime.p7s
Description: S/MIME cryptographic signature
rds in the clear over non-SSL as
Paul suggests.
Cheers,
Ben
smime.p7s
Description: S/MIME cryptographic signature
year 2009.
I got tired of dragging on the 0.9 series, when it might as well be
0.10 instead. So it'll be 0.10 and 1.0 at once instead of 0.9.8 and
1.0. Just a difference in the version for the non-1.0 series.
Cheers,
Ben
smime.p7s
Description: S/MIME cryptographic signature
install Sphinx
Then cd into the pylons/docs/en/ dir and:
make html
Which will build the HTML copy in a _build directory that you can take
a look at.
Cheers,
Ben
smime.p7s
Description: S/MIME cryptographic signature
operation).
* replaced homegrown ThreadLocal implementation with threading.local,
falls
back to a 2.3 compat one for python<2.4
Cheers,
Ben
smime.p7s
Description: S/MIME cryptographic signature
not the actual libraries. The WebHelper functions were ported from
Rails, and haven't been updated in quite awhile, thus are out of date
and will not be maintained.
Cheers,
Ben
smime.p7s
Description: S/MIME cryptographic signature
s-dev was
used, not go-pylons.
Cheers,
Ben
smime.p7s
Description: S/MIME cryptographic signature
o remove them from the package.
Cheers,
Ben
smime.p7s
Description: S/MIME cryptographic signature
On May 28, 2008, at 1:31 PM, Ben Bangert wrote:
Pylons Security Advisory
Topic:Path traversal bug in default error controller
Module: controllers/error.py
Announced:2008-05-15
Credits: Webwise Security
Yes, I know I have the wrong date in the
Pylons Security Advisory
Topic:Path traversal bug in default error controller
Module: controllers/error.py
Announced:2008-05-15
Credits: Webwise Security
Affects: All Pylons releases with Routes < 1.7.3
Corrected:Routes 1.7.3 or greater
g a WSGI intro
and overview in the morning to help bring people up to speed as well.
Those unable to make it, are welcome to join us online to sprint.
Cheers,
Ben Bangert
smime.p7s
Description: S/MIME cryptographic signature
On May 18, 2008, at 6:25 AM, blaf wrote:
Thanks Ben to finally commit your thoughts about proposed logos and
general vision about the soul of the project. I think we should be
careful about the logo because it's a critical aspect of communicating
a first impression to the right audience. A
On May 17, 2008, at 11:13 AM, Graham Higgins wrote:
Ben recommended folks to get familiar with Sphinx.
Which I have been doing. I've been amusing myself with
http://bel-epa.com/pylonsdocs/index.html
U, WOW. Are there pylons-dev patches coming with some of these
changes? :)
I re
On May 1, 2008, at 5:33 AM, Graham Higgins wrote:
gettingstarted
configuration
controllers
templates
helpers
models
testing
debugging
deployment
I've been playing with a candidate structure which attempt to
integrate some of the pre-existing documentation.
(Ben, it&
On Apr 30, 2008, at 12:25 PM, Ben Bangert wrote:
To run the Sphinx build locally, first install Sphinx: ./superdevenv/
bin/easy_install -U Sphinx. Then go to superdevenv/pylons/pylons/
docs and type: make html
The easy_install step shouldn't be required now, I've added Sphinx to
y stated that, just setup
a dev env like I mention here, find a section of the docs you'd like
to work on, and announce it here so we avoid working on the same
doc. :)Or we could just setup a page on the wiki to track who's
working on which sections.
Cheers,
Ben
smime.p7s
Description: S/MIME cryptographic signature
ibution of copyright in the LICENSE file
I believe.
- Ben
smime.p7s
Description: S/MIME cryptographic signature
are welcome to join us online to sprint.
Cheers,
Ben Bangert
smime.p7s
Description: S/MIME cryptographic signature
as a rather nice form put together here:
http://repoze.org/contributing.html
I'll modify as needed for those wishing to contribute to the Pylons
core docs. That work for everyone?
Cheers,
Ben
smime.p7s
Description: S/MIME cryptographic signature
ns.templating import render_mako as render
Cheers,
Ben
smime.p7s
Description: S/MIME cryptographic signature
wn to nose. --with-pylons=TEST.INI, or whatever one
you want to use. The only change I can think of that might make it
easier in Pylons is if the test/__init__.py was able to figure out
what option you had specified to --with-pylons, though I'm unsure how
to get that info at the moment
al review
Please let me know. I'll be putting together a rough outline and
posting it shortly.
Cheers,
Ben
smime.p7s
Description: S/MIME cryptographic signature
eir template loader mechanism mostly the same over
revisions (which so far, they have).
At least with the render_ functions, if one of them breaks, and a
project *needs* to use the latest template system before a new Pylons
release can be issued, they can easily write their own render function.
27;c'
for variables, the included render_ functions are provided by Pylons.
No need to write them yourself.
MakoRenderer is 'ad hoc' as much as render_mako. Can you clarify what
makes one of them less ad hoc purely because its a class rather than a
function?
Cheers,
Ben
smime.p7s
Description: S/MIME cryptographic signature
ough simplicity
and elegance, so far Buffet and its abstraction ilk has been the exact
opposite. After seeing how simple and short it is to just write a
little render function that does *exactly* what you want, its hard to
see the advantage in accepting template language limitations and
abstr
ange options to the Mako templateloader, it'd be
really obvious how to do that... or change it to a different engine's
template loader as appropriate. What purpose does the MakoRenderer
object have?
Mike, I believe I've updated this as you suggested, such that Mako
u
is
down to about 4-6 lines of code. I don't think it will hurt people to
write one that works as they want.
Cheers,
Ben
smime.p7s
Description: S/MIME cryptographic signature
including a future deprecation warning for
Buffet, with more blatent deprecation warnings in 0.9.8 as 1.0 will
drop Buffet entirely.
Any other thoughts?
Cheers,
Ben
smime.p7s
Description: S/MIME cryptographic signature
alues per key's createfunc. Can you elaborate on what
you'd want to store for use with the creatfunc? I could see perhaps
supplying a createargs dict that would include variables to call it by
keyword style when used. Is that what you're referring to?
Cheers,
Ben
smime.p7s
Des
s the stored time in addition to the
value. Then upon retrieval of the value (and its stored time), it does
a check against the expiration to see if the value has expired, and
recreates it if it has. Until Beaker next accesses and invalidates the
value, it will not be removed from the backend.
Ch
his bug. Thanks
for the catch!
Cheers,
Ben
smime.p7s
Description: S/MIME cryptographic signature
ed for
keys you've asked get_cache for with createfunc in the past. So key3
should fail in addition to key1, since the createfunc was only
specified for key2. Is that the behavior you were expecting as well?
Cheers,
Ben
smime.p7s
Description: S/MIME cryptographic signature
On Feb 15, 2008, at 12:53 PM, Andrew Stromnov wrote:
Latest from HG repository. OS - Ubuntu 7.10. Python 2.5.1
Do you know when this began? All the Beaker unit tests, which do this,
still work.
- Ben
smime.p7s
Description: S/MIME cryptographic signature
1 - 100 of 129 matches
Mail list logo
