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
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
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'
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
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
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 be
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/
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,
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
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.
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
On Feb 8, 3:46 pm, Blaise Laflamme bla...@laflamme.org 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
On Feb 9, 2:21 pm, Blaise Laflamme bla...@laflamme.org 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
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?
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
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
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
On Mar 27, 4:33 pm, Blaise Laflamme bla...@laflamme.org 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
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 ;
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:
a href=http://example.com; data-a=1
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
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)
For
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
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
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':
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
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
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
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
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
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
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
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,
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
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
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.
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
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
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
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"
> 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
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
>
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,
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
44 matches
Mail list logo
