On Saturday, March 11, 2017 at 10:14:11 AM UTC-5, Robin Harms Oredsson
wrote:
>
> The only pattern I've really found seems to be:
> - It always happens on aborts
> - It seems to be during some server load
> - It only seems to happen during requests that only read data
>
I don't use ZODB, but I
On Monday, April 11, 2016 at 5:23:26 PM UTC-4, Tres Seaver wrote:
>
> I do all such "global setup" tasks inside the "main" function, registered
> as the 'paste.app_factory' entry point. E.g.:
>
I usually do the same, unless the "global setup" is happening in some sort
of submodule/directory
> On Wednesday, April 6, 2016 at 8:14:02 PM UTC-4, Jeff Dairiki wrote:
>>
>> Maybe that's enough motivation to go that way?
>>
>
Ok. I lasted a full week using the global scoped session and just couldn't
do it anymore.
Back to my old way / the new way. I updated the project to use the
fort
On Wednesday, April 6, 2016 at 8:14:02 PM UTC-4, Jeff Dairiki wrote:
>
>
> I'm not very familiar with the stock scaffold. I just went to look at it
> and was initially confused, since the scaffold in the master branch
> currently uses a reified request property to construct the SqlAlchemy
> s
I edited my original post before hitting submit, and managed to clear out
the important stuff. Ha.
On Wednesday, April 6, 2016 at 2:42:38 PM UTC-4, Jeff Dairiki wrote:
>
> I use a reified request property to create the SqlAlchemy session.
> The factory function adds an "add_finished_callback" t
A few routes I have need to explicitly commit the session, and require me
to use "long lasting sessions"
(https://pypi.python.org/pypi/zope.sqlalchemy#long-lasting-session-scopes)
Since this disables transaction's call to "close" on commit, what is the
best way to close the SqlAlchemy session?
On Wednesday, March 16, 2016 at 9:36:44 PM UTC-4, Zsolt Ero wrote:
>
> David Cramer from Sentry replied to me that if Sentry is used with the
> middleware, then it should automatically receive the WSGI context:
> from sentry.middleware import Sentry
>
> application = Sentry(application, client=C
Assuming the issue is what you think it may be...
What if you just used the .ini file to declare that you want translogger
enabled and some variables, but then your app setup code handles the setup
(and fixes the template line).
That would still let you control everything off an ini, but your
Assuming (1) Ian isn't going to maintain it anymore, (2) You have his
blessing as the new maintainer [but want to push this off]...
You may be speaking about this, but if not...
Have you considered an approach like starting a new github organization for
pastedeploy (or paste) ? That would make
@Steve-
Would it make sense to just explicitly state "Pylons was put into
maintenance-only status in 2012."
On Tuesday, February 9, 2016 at 3:02:23 AM UTC-5, Steve Piercy wrote:
>
> I've also merged a PR to change the wording on this page to reflect
> reality.
> http://www.pylonsproject.org
Read the docs on `add_request_method`. It's pretty great. I think the
docs continue on the set property method, and explain the pattern a bit
more.
Anyways, combined with reify, there is very little overhead. You can also
use dotted-name strings to register, which can make things a bit easie
I have about a dozen reified request properties on an application. They're
great.
It's entirely possible to abuse it – but that's what coding standards are
for.
We have about a dozen objects on our request. They could be consolidated
into a smaller, nested, hierarchy... but they're all "requ
In my experience, the standard scaffold way is perfect for most uses.
If your codebase grows very large, or you start needed to run non-pyramid
services, you may need to rethink things.
One of my projects outgrew the typical 'views' approach. Now, we prototype
the functionality onto the views
On Tuesday, January 5, 2016 at 2:06:28 AM UTC-5, Steve Piercy wrote:
>
> What is the value for maintaining the domain name pylonshq.com?
>
permanent redirects for a few years for legacy links and search engines.
that's about it.
--
You received this message because you are subscribed to the
I just wanted to add that PylonsHQ redirects to PylonsProject (and is the
name of the github project), and that link should be maintained.
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails
On Wednesday, December 16, 2015 at 3:00:08 AM UTC-5, Robin Harms Oredsson
wrote:
>
> OK thanks, I'll try to increase logging verbosity some way. The permission
> part is something I've managed to rule out :/
>
Just to be sure... did you switch to the user that supervisor runs as, and
were abl
Then the only things I can think of are:
* user/permissions error on supervisor starting the process
* an environment variable missing/unset/overwritten in supervisor
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To unsubscribe from this grou
What does "zeo storage fails" mean? Is the service not starting, is
pyramid not connecting to it?
Have the logs suggested anything ?
Anyways, I'm unclear if there is a race condition involved between the
storage engine and your pyramid app. If pyramid needs the storage engine
to start up, an
This is a bit of a pie-in-the-sky idea... but it occurred to me the other
day that there should be a standard way of organizing/packaging plugins
that provides for debugtoolbar support.
i.e., a standard style for creating a plugin that also has a debugtoolbar
panel (or other hook into the tool
If you're going to script a request, then you'll need to follow the
bootstrap/commandline/shell docs. That means loading your whole app and
tying into the request lifecycle.
I have some various commandline tasks that require me to run several tasks
though a pyramid environment.
To handle th
Ok, this use case is somewhat similar to ours... in that it doesn't require
pyramid at all. We use sqlalchemy, but zodb shouldn't be much different.
We have 2 packages:
* `myapp_pyramid`
* `myapp_celery`
`myapp_pyramid` will import `myapp_celery` to call it's `@task` decorated
functions. the
What exactly are you trying to do with Celery - can you give an example?
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to pylons-devel+unsubscr...@googlegroups.co
For development I use nginx on http/https default ports, serving static
directly and proxypass back to pserve for dynamic content.
The staging/production environment just swaps out the proxypass for uwsgi.
Everything in nginx is built out with components/includes, so it's
literally just swapping
On Thursday, September 24, 2015 at 12:28:01 PM UTC-4, Bert JW Regeer wrote:
>
> I personally use uWSGI with nginx, however there are also a lot of people
> that simply reverse proxy to waitress.
>
Production: uWSGI with nginx. nginx is controlled by the standard os
hooks; the uwsgi services
I wouldn't run this via supervisord, because supervisord is really aimed at
managing services that are supposed to be "on" (ie, production or staging
environments). You'll encounter a lot of issues when you need to persist
an off-state across reboots or need to tweak certain settings (which wil
Most python software news is organized in planets. There's a lots of ZODB
over at http://planet.plone.org/
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to pyl
I may be reading this wrong, but couldn't you just define your custom
attributes in `__customer_acl__` and `__api_acl__`, then define `__acl__`
as a custom property on a shared base class that simply proxies the
attributes in the lookup order you want over to Pyramid's default policy?
--
You r
I'm not sure what `request.peewee_dbs()[db].connect()` does, but I would
probably recommend against this db setup pattern that you're using. By
doing this in a tween, every request that pyramid handles will do a
connect/disconnect to all the databases you defined.
One of the more popular patte
preface: I think you should be able to do what you want inside of Pyramid.
In terms of modifying a JSON response by ADDING an attribute (like the
auth_id), it's not that hard and you don't need to deserialize. You can
capture the response in a tween and just replace the trailing '}' with ',
"m
Nice!
I'm just looping panels right now with isinstance() to discern the correct
one.
It took a while to get the config right, but I was able to implement this
without any edits to debugtoolbar yet.
https://github.com/jvanasco/pyramid_debugtoolbar_api_sqla
--
You received this message becaus
I had an idea a while back for a Toolbar <-> Panel api, and I think I need
to build it out. hoping someone here can set me straight and offer some
better ideas on how to pull this off.
The simple idea:
1. Give each panel a `toolbar` attribute after instantiation. this
would allow any pan
I would create an Issue and propose it on the Github. One of the core
maintainers will say something like "Great!", "Maybe..." or "No way".
I've seen (and personally gotten) a lot more "No Way" than "Okay" for
proposed changes.
This is such an edge case though, that I don't know if they'll g
You might be able to use the "Project" variable, if you pass in a
Capitalized form
$ pcreate --scaffold starter Foo
> 'project': Foo,
> 'package': foo,
Note that this doesn't "Capitalize" the name. it keeps it as-is:
$ pcreate --scaffold starter FooBarBash
> 'project': FooBarBash,
> 'package':
On Thursday, October 2, 2014 11:01:33 PM UTC-4, Bert JW Regeer wrote:
>
> This seems like functionality that any ol’ profiler should be able to give
> you, and wouldn’t require any changes in Pyramid.
Mostly, yes. For my personal needs, I can backtrack data out of this on my
dev environment
When doing performance audits, an annoying feature of Pyramid is that it's
not very easy to pinpoint where the slow part is.
I'd like to suggest some sort of logging facility for the internal request
lifecycle
there are a handful of things that I think could provide useful metrics,
either disp
Honestly , It depends on how you see the application grow.
I've been doing more of "Choice D" lately-
Choise C - Keep that stuff in the View.
Choice D - Have an "internal API" for methods like "getAllComments";
exposing something like "lib.internal_api.getAllCommentsForBlogentry(id)"
Fo
Wish I saw this earlier.
I use my own cookies and auth. It was trivial to set up.
You can bootstrap any authorization/cookie setup with either an `event
subscriber` ( NewRequest ) , a `tween` that wraps your app, or by setting
up `class based View Callables` that inherit from a single base cla
On Tuesday, July 23, 2013 2:52:32 AM UTC-4, Laurence Rowe wrote:
>
> I've not used the scaffold myself, but invalidation is handled by
> zope.sqlalchemy which ties SQLAlchemy into Pyramid's request lifecycle with
> pyramid_tm.
>
i didn't realize that pyramid_tm was in the environment.ini; than
Someone posted a docs suggestion to -devel, which made me look at the
current sqlalchemy scaffold.
I'm not sure it's 'correct'
a few weeks ago I asked Mike Bayer (sqlalchemy) what the best practices for
webapps were (
https://groups.google.com/forum/#!topic/sqlalchemy/ZsHxDzlATCQ )
he r
this was super confusing to me for a while too, until i looked at some of
my debug info and really understood the tweens.
iirc, the callstack is essentially:
* tween start
* `handler(request)` ( which can wrap other tweens )
* tween end
* response callback
* finished callback
the tweens are ba
On Friday, June 28, 2013 5:04:08 PM UTC-4, Mike Orr wrote:
>
>
> Are there any other syntactic sugar patterns that would be helpful in a
> Javascript-rich or HTML 5 application?
>
you should support html5 custom data attributes , the *data-** syntax.
ie:
http://example.com"; data-a="1" d
Does anyone know how / where I can request an alternate licensing
permission ?
I'm trying to create a new Session package that replaces most of beaker
with a dogpile backend.
Dogpile and Beaker both have the BSD license. pyramid_beaker is under the
bsd-like Agendaless Consulting license ; and
On Mar 27, 4:33 pm, Blaise Laflamme wrote:
> you're about t reverse-engineer mcdonc's brain... be careful ;)
ha!
i just needed to figure out the mako integration , which was pretty
straightforward ( see the other thread ).
--
You received this message because you are subscribed to the Google
I've been working on a method to optimize whitespace with Mako
templates -- instead of collapsing insignificant whitespace after
Pyramid renders the view_callable, it's stripped when Mako first
compiles the template.
I'm trying to figure out the best way to integrate this with Pyramid.
At first I
thanks. makes sense.
i'm just trying to reverse engineer some templating flowthroughs.
most other things were logically grouped together.
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To unsubscribe from this group and stop receiving emails f
looking at the source, I see:
* pyramid/chamelon_text.py
* pyramid/chamelon_zpt.py
* pyramid/mako_templating.py
was there any reason for these being on the top-level, and not under a
consolidated namespace like pyramid/templating , or did this just
happen randomly ?
--
You received this messag
I'd suggest these 2 strategies:
1. Dual-License the Docs as a choice between Current or the Perl
Artistic license. The Artistic license is OSI & Debian approved, but
neuters most commercial activities ( docs can be on retail CDs , but
books would fall under a "reasonable copying fee" ).
2. split
just an observation
i had an issue with route matching, due to my error of not having a
proper regex in the route
/archive/{}/{mm}/{dd}/{slug}
was quickly fixed with:
/archive/{:\d{4}}/{mm:\d{2}}/{dd:\d{2}}/{slug}
does anyone else think that this syntax is weird? shouldn't
On Feb 9, 2:21 pm, Blaise Laflamme wrote:
> No the new theme is not online, I've been just playing with different ideas
> before starting the public project. The current theme is
> here:https://github.com/Pylons/pylons_sphinx_theme
>
> Do you attend pycon this year?
Sadly no, I have a few confl
On Feb 8, 3:46 pm, Blaise Laflamme wrote:
> Hi jonathan,
>
> feel free to modify the sphinx theme and send a pull request. Actually
> older versions like 1.1, 1.2, etc, are not out-of-date but up-to-date with
> those versions. There are the latest and the development one that reflects
> the curre
what controls how the pyramid docs get built and stored onto
doc.pylonsproject ?
looking at the github source (
https://github.com/Pylons/pyramid/tree/master/docs
) it looks to me like only the current docs are in master, and the
older ones are built off misc releases
the reason why i ask, is th
these are all good points.
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/pylons-devel/-/XOhPX89JubgJ.
To post to this group, send email to pylons-devel@googlegroups.com.
That pattern / functionality is great. I'm just talking about
proactively saying "this name space is reserved for plugins, this
namespace for projects - you can rest assured that as Pyramid grows
and new functionality is added, you will not be affected as long as
you stay within that container".
The past few updates to Pyramid have had a few changes around the
Request object - new attributes, new functionality to add attributes,
etc.
With that, combined with the best-practice of passing the Request
object around during the request lifecycle, I wanted to suggest
creating a 'project' and
holy crap that sounds awesome.
On Tuesday, September 25, 2012 2:42:24 PM UTC-4, Michael Merickel wrote:
>
> On Tue, Sep 25, 2012 at 1:13 PM, Jonathan Vanasco
> >
> wrote:
> > This is purely my very opinionated 2¢ ...
> >
> > I've had to integra
This is purely my very opinionated 2¢ ...
I've had to integrate against oAuth a few times, and have constantly found
it a hassle.
The existing 'core' Python libraries for it are rather scattered in terms
of active development, maturity and "street cred" ( by which I mean that
you'll often fin
>
> Additionally you could provide help on how to generate such a secret (but
> that's extra candy). I have looked through various parts of the
> documentation and it is always set to something like 'seekrit' and similar,
> but it is never mentioned how to make sure that this is secure.
>
fwiw
I went a bit crazy the other day dealing with pyramid_mailer
after going through all the code for pyramid_mailer and
repoze_sendmail , I realized that the send_to_queue function occurs
within the transaction.
this isn't mentioned anywhere within the docs and it is described in a
section /after/ t
A couple of small requests for the website after trying to jump on it
to view source :
- The first slide on the splash screen is for a "Download". It would
be great if there was a GitHub link on that too.
- It would be great if the "projects" pages had links to github as
well
- Finally, it would
On May 15, 7:33 pm, Michael Merickel wrote:
> What? Pyramid doesn't have a "debug" code path, minus emitting some
> log messages. Do you mean that the debugtoolbar is doing something to
> the response?
I'd imagine its either the error screens from pyramid_debugtoolbar or
whatever settings like
I ran into an issue a few months ago regarding a NewResponse
subscriber and failing to catch errors (
https://groups.google.com/group/pylons-discuss/browse_thread/thread/54b5b3eb5e2ccfe/4e9a2abc09b9651f
)
As I prepare for a production release , my old code ( which i forgot
to remove ) started firi
i built a non-cms thing a few weeks back , to illustrate how a bunch
of packages i wrote work.
http://github.com/jvanasco/pyramid_packages_demo
there might be some stuff in there that helps you.
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" grou
glad to help!
On Mar 13, 10:43 pm, Massimo DiPierro
wrote:
> I just did it.
>
> http://pypi.python.org/pypi/Gluino
>
> Thanks for the help.
>
> massimo
>
> On Mar 13, 2012, at 9:36 PM, Jonathan Vanasco wrote:
>
>
>
>
>
>
>
> > Check this tuto
Check this tutorial
http://wiki.python.org/moin/CheeseShopTutorial
The general flow
1. Register your account on PyPi -
http://pypi.python.org/pypi?%3Aaction=register_form
2. 'register' the package with pypi: `python setup.py register`
3. 'upload' the package : `python setup.py sdist upload'
whe
the current classifier is :
Framework :: Pylons
that makes sense for Pylons stuff, but Pyramid is a bit of a
departure. i.e. things labeled "Framework :: Pylons" but intended for
Pyramid are likely to not work under Pylons at all.
--
You received this message because you are subscribed to the
two quick suggestions for scaffolds. i'd be happy to submit a patch
if the maintainers agree:
1. Move cache_max_age to a dev.ini setting
scaffolds currently have this line:
https://github.com/Pylons/pyramid/blob/master/pyramid/scaffolds/alchemy/%2Bpackage%2B/__init__.py
https://github.com/Pylo
i'm not too familiar with "paster create" - do you think it would be
possible to make an entry point that warned people to use pcreate?
--
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@googlegroup
and playing around a bit, i see that the newest version of pyramid
moved to pcreate from paster create... so perhaps the above is not
needed.
--
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@googl
I think at one point it was required by one of pyramids dependents,
and then it changed.
It's either not possible or safe to create a new project with paster
right now.
For example:
- On my OSX 10.6 machine , I used to run pylons under 2.6.
- I upgraded python to 2.7 to build & migrate some apps
I think the criticisms in the post -- and their defense here -- are
really important. I've had the same struggles.
While many are not technically valid , they appear to be so because of
the documentation and positioning of pyramid.
Pyramid is really powerful framework, but its also quite low-lev
oh neat!
at first i thought this was for some sort of preview text, then
realized it was for a url friendly marker
i do something a little different.
also, i'd check to make sure what you get the url chars from. last i
checked, most things in python, perl, etc were written to rfc 1738 or
2396 b
just because these libraries are not being supported by the framework
doesn't mean that they're incompatible with the framework.
the pylons people are focusing on the backend framework , and simply
not trying to do the automagic integration points that generate
javascript code per-libary
you can
how would people feel about having a config option to replace the
c.form_errors object in pylons/validators/__init__.py with an
AttribSafeContextObject from pylons/util.py -- the same sort of object
that c is
i'd be glad to patch it if people agree -- a lot of my templates would
look way cleaner
only works with routes, but i didn't find any non-routes mappers for
pylons ;)
this is a dumb little helper that is useful as all hell (though it
took me too long tracing vars throughout pylons to figure out )
personally, i think url_for should call this as well, to make sure
that it generates
74 matches
Mail list logo
