+1
Python 3.2 is not likely to be relevant going forward because conservative
users are anyway still on 2.x.
Malthe
On Wed 5 Nov 2014 at 21:39 Wichert Akkerman wrote:
>
> > On 05 Nov 2014, at 17:55, Tres Seaver wrote:
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On 11/05/2
My apologies if its downtime has caused issues.
\malthe
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
https://lists.repoze.org/listinfo/repoze-dev
This is also a problem on regular Zope, fwiw.
It's not particular hard to call ``translate`` first on the mapped
values, but it's of course a little tedious. The question is whether
it's too much of an overhead to go through any mapping, looking for
messages (i.e. the automatic alternative).
\mal
On 1 April 2011 15:28, Fabio Tranchitella wrote:
> as discussed briefly with Malte on #repoze, I'd like to add XInclude
> support to the ZPT Chameleon templates. As it turned out, it is quite
> simple and the patch is attached to this message.
Sorry for the late response. Patch looks good.
But I
On 29 March 2011 11:02, Hanno Schlichting wrote:
> Isn't that exactly what macros give you via define and use?
Except macros are funny in that they render implicitly where defined.
But you could definitely have a template that includes any number of
macros. Just make sure to not render that temp
>
>
> [snip]
>
> Is there any shorter way to do this? Can the template loader be passed
> implicitly?
It would easy to include a load function or even expression, i.e.
"load: ../header.pt", but as that example illustrates, it would be
relative to where the template itself is located.
We could in
> Since WSGI support is available in Zope 2.13, I thought repoze.zope2
> was obsolete now.
Oh I see:
http://docs.zope.org/zope2/releases/2.13/WHATSNEW.html#wsgi
Hadn't seen that. Thanks!
\malthe
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.or
Are there any impediments to releasing the trunk of repoze.zope2?
\malthe
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev
On 24 March 2011 12:02, Brian Sutherland wrote:
> I'd like to make a new release of repoze.bitblt (when my pull request is
> accepted). Is there any documentation anywhere about how releases should
> be tagged/created within the Repoze github repository?
Looking at e.g. https://github.com/repoze/
On 7 March 2011 12:11, Wichert Akkerman wrote:
> For input possibly. I consider invalid markup as possible output to be a bug
> in the template engine.
Right. Note that any dynamically included content will undergo escaping:
If your input is valid, you know that the output is going to be valid,
On 7 March 2011 12:07, Wichert Akkerman wrote:
> That is the opposite of what I want: I would like invalid markup to be
> rejected, and I want it to be completely impossible to generate invalid
> markup.
I see. Perhaps there could be a validator sitting in front of the
compiler which (as the defa
On 7 March 2011 11:59, Wichert Akkerman wrote:
> Is there a mode to make it impossible to accept or generate invalid markup?
> For some of us that is very important.
That's what this changeset does. It allows you to use invalid markup
to the extent possible. For instance, you can use HTML markup:
Just wanted to follow up on some issues with attribute escaping that
were asked on the channel.
I believe I have now adressed these concerns:
https://github.com/malthe/chameleon/commit/800306a7433250120e039773ef013702dbaec3fc
In particular, you can now use invalid markup such as:
It's no
On 2 March 2011 19:27, Shane Hathaway wrote:
> I think it's unwise to support this meaning of the pipe character in Python
> expressions. I say the new behavior is better.
Great.
\malthe
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://l
On 2 March 2011 08:18, Chris Withers wrote:
> Interesting, I use this technique a lot, and I didn't experience this
> problem with my brief test of 2.0-rc2.
Mind you, Shane means tal:comment in *attributes*:
...
I think this is a fairly quirky feature of ZPT.
Actually, I'd be inclin
On 2 March 2011 03:36, Shane Hathaway wrote:
> Also, a quirky behavior of the reference TAL implementation is if you use
> unknown attribute names in the "tal" namespace, those attributes get
> stripped from the output. It's a useful feature; it allows me to write
> comments about a tag. I alway
On 2 March 2011 03:28, Shane Hathaway wrote:
> I hope this isn't a XSS hole. I can't think of a way to add a
On 1 March 2011 14:59, Chris Withers wrote:
> This appears to work correctly in 2.0-rc2.
Great.
> I'm nervous on the added dependencies of distribute and ordereddict :-(
> Oh, and why is unittest2 being installed even when I'm not testing?
The only way to support the platforms we support is thr
On 1 March 2011 14:49, Chris Withers wrote:
>> Which version is this?
>
> 1.3.0-rc1
If you have the time, can you try the same thing in 2.0-rc2?
Thanks!
\malthe
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/r
On 1 March 2011 14:19, Chris Withers wrote:
> So, it's quoting the tags but not the entities. Bug, no?
Yes, it certainly seems so.
Which version is this?
> tal:content="structure pager"/>
That should include the content in ``pager`` as-is. What do you get?
Thanks,
\malthe
__
On 1 March 2011 12:00, Chris Withers wrote:
> tal:content="pager"/>
>
> ...doesn't appear to quote the html in the "pager" variable.
> This is different from normal zpt, why the change?
It should definitely escape it in exactly the same way.
> Also, as a corollary, the following appears to
i, Feb 25, 2011 at 12:14, Malthe Borch wrote:
>> The current development target for Chameleon 2.0 [1] is now stable and
>> seems to be compatible with Pyramid (tests run). For information on
>> what's new, see the readme.
>
> I'd like to test-drive Chameleon 2 wi
The current development target for Chameleon 2.0 [1] is now stable and
seems to be compatible with Pyramid (tests run). For information on
what's new, see the readme.
Minimum Python version is 2.5 (and compatible up to 3.2). PyPy is also
supported (only fast-forward branch tested, but should work
Hey Brian,
That's right. It hasn't been implemented and it's a bit of "false
advertisement" really.
That said, implementing it should be relatively straight-forward.
\malthe
On 14 February 2011 17:20, Brian Sutherland wrote:
> Hi,
>
> The genshi text template language doesn't seem to work at a
Hey Tim,
The server that's hosting the site was compromised yesterday. My slice
there has been suspended.
As of yet, I haven't gotten permission to access the files on there
yet from the hosting provider.
Thanks for reporting though.
\malthe
On 17 December 2010 14:22, Tim Hoffman wrote:
> Hi
Alternatively, enable implicit decoding using
``default_encoding="utf-8"`` (in the template constructor). This is
enabled on Plone, for instance.
\malthe
On 16 December 2010 14:47, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 12/15/2010 10:18 PM, Iain Duncan wrote:
Hey Eduardo, ---
It shouldn't eat that namespace prefix. I wonder if this is still the
case in the current Chameleon release. Have you tried?
Sorry for the long delay in response.
\malthe
On 5 June 2010 18:29, Eduardo Diaz wrote:
> Hi, I'm trying to use facebook's xfbml, it uses a custom names
On 12 October 2010 13:40, Paul Everitt wrote:
> In the first case, Chameleon refuses to parse the zpt because Expat tries to
> interpret <% as a startTag. In the second case...needless to say, it is
> ironic that we have overlap in syntax. I then tried wrapping a CDATA around
> the block, but
On 9 September 2010 06:08, wrote:
> coverage.misc.NoSource: No source for code: '/tmp/tmprq_hmg/tmpNuWT1u.py'
But you shouldn't take offense –– it's just a temporary file!
Hudson, it is you who is not unstable or better.
___
Repoze-dev mailing list
Re
This was fixed earlier on in the repository, but I have now also
updated the live documentation.
Thanks!
\malthe
On 29 August 2010 08:45, Chris McDonough wrote:
> This message was discarded because the sending address wasn't subscribed
> to the maillist, FWIW.
>
> On Sat, 2010-08-28 at 21:11 +0
Malthe Borch added the comment:
It's because it doesn't really make much sense to not name your tags if you
provide a translation string. However, there are already some examples of this
in the tests.
Maybe:
1) First look at the existing examples that demonstrate this. They'v
Malthe Borch added the comment:
Where is this branch? Can you paste a link to the revision diff when you've
committed it (e.g. using http://repoze.org/viewcvs/chameleon).
--
status: unread -> chatting
__
Repoze Bugs
<http://bugs.repoze.o
Malthe Borch added the comment:
> Is there a solution for dynamic template-strings? It seems to work, but i
> am not sure what happens, if template changes.
If you change the ``body`` attribute, then the template will be automatically
recompiled.
With regards to setting a template
Malthe Borch added the comment:
I'm not sure what this is, but it's not the first report I get about it.
It's difficult to debug without some way of reproducing it consistently,
although it
seems to revolve around thread-safety.
One thing about it though is that you seem to
On 17 June 2010 16:08, Charlie Clark wrote:
> This is standard behaviour for folders (the not accepting duplicates). I
> think changing it would be against user expectations.
My file system accepts duplicates (meaning replacement). I don't need
to remove the file first.
\malthe
_
Malthe Borch added the comment:
Possibly the five.pt compatibility layer (for Zope 2) should accomodate
explicitly for the
``Missing`` case, i.e. directly on its translation function.
On the ``__class__`` issue; the reason why we use it instead of invoking
``type`` is a slight
performance
It wasn't.
On 3 June 2010 13:05, Wichert Akkerman wrote:
> On 6/3/10 11:27 , Malthe Borch wrote:
>>
>> We should try and consolidate all these different bug trackers. It's a
>> mess. Too bad we don't have the proper top-level name for this. I
>> don&#x
On 3 June 2010 12:37, Chris Withers wrote:
> How do you run the tests?
python setup.py nosetests
> Hmm, it occurs to me that even if the [test] extra_requires was there, I
> don't know how to feed that into:
>
> python setup.py develop
>
> Any ideas?
Not really right now; let me think it over.
t is simple to make things.
> http://www.wiggy.net/ It is hard to make things simple.
> ___
> Repoze-dev mailing list
> Repoze-dev@lists.repoze.org
> http://lists.repoze.org/
Really that's odd; we can definitely add a [test] on next release; or
please go ahead and commit it if you can.
Thanks,
On 3 June 2010 09:50, Chris Withers wrote:
> Malthe Borch wrote:
>>
>> This has to do with lxml; it currently worksforme, but I don't know
>>
--
> File "/Users/chris/LocalSVN/chameleon/src/chameleon/zpt/i18n.txt", line 447,
> in i18n.txt
> Failed example:
> print template.render(target_language='de')
> Expected:
> http://www.w3.org/1999/xhtml";>
>
> Default
&
;> Perhaps I'm just using it wrong; how are other users handling optional
>> nonString fields?
>>
>> Thanks, Chris.
>>
>>>
>>
>> ___
>> Repoze-dev mailing list
>> Repoze-dev@lists.repoze.org
>> http://lists.repoze.org/l
I guess it's documented here:
https://bugs.launchpad.net/python-mode/+bug/328781.
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev
try passing tab at "pass": http://pastebin.com/qCMaym9S
\malthe
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev
On 13 May 2010 19:23, Douglas Cerna wrote:
> I'm trying to set up a "page" macro that includes the in it,
> like this:
That's not valid XML and since Chameleon currently uses Expat to parse
documents (albeit very customized), it refuses to accept a doctype
after a regular tag.
As Shane mention
quot; http://palladion.com
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkviuV4ACgkQ+gerLs4ltQ5lwwCdFI2BWSlXfX8ymioindFiGtE8
> EZ8AnR18921gLBaVq/nsYajVljIE7tlK
> =7ktE
> -END PGP SIGNATURE
> would do. A bit of encouragement, appreciation and recognition can boost our
> morale and can make us contribute better for Open Source Community.We are an
> NGO
> and develop software also.
According to your own homepage, Mahiti Infotech is a large Indian IT
company that specialise in a host o
On 9 April 2010 21:30, Hanno Schlichting wrote:
> Sure. I think the approach we took was good. It gave as a hugely
> successful, stable and performant engine. I just have the feeling that
> the current model has become somewhat convoluted and hinders us to do
> any more optimizations. I certainly
On 9 April 2010 20:27, Hanno Schlichting wrote:
> - Generally there's no real optimizations in the code and the current
> infrastructure makes them hard to write. Like generating efficient
> code for stuff like "var1 string:'static'". Or not filling the repeat
> variable if it isn't used inside a
On 1 March 2010 18:47, Uli Fouquet wrote:
> But with Chameleon trunk gives::
>
> --
> File "...chameleon/trunk/src/chameleon/core/codegen.txt", line 48, in
> codegen.txt
> Failed example:
> suite.source
> Expected:
>
On 31 March 2010 22:41, Andrey Popp <8may...@gmail.com> wrote:
> * Inject current view in template, because TALES expression for content
> providers make things work by adapting context, request, view (the last two
> already available inside template) to IContentProvider.
That's an easy one: see
On 15 March 2010 13:12, Douglas Cerna wrote:
> First of all, sorry for posting all these small typos on the dev mailing
> list. I'm starting with repoze.bfg and would like to contribute somehow. Is
> there a way of branching the docs, fixing the typos myself and send a diff to
> someone who can
On 4 March 2010 22:22, Shane Hathaway wrote:
> From a template developer's POV, it's useful to apply the same XML
> declarations throughout a site using metal. The current syntax is
> non-obvious and perhaps problematic, but workable. Some other syntax might
> be better, but let's not break the
On 4 March 2010 22:45, Kevin J. Kalupson wrote:
> In that case, there should be macro explicitly containing the doctype
> and other wanted headers.
Yes, but that's unfortunately impossible.
> I don't think it's a syntax issue, I think it's a behavioral issue. I
> think the 1.1 branch exhibits b
On 4 March 2010 22:02, Kevin Kalupson wrote:
> I wouldn't expect the the xml headers in a macro template to be applied to the
> page template being rendered. It makes no sense to me that an element not
> contained within a macro definition would be applied to the page calling the
> macro under an
On 4 March 2010 19:38, Jasper Op de Coul wrote:
> I don't have commit rights to the repoze repository but I attached a patch.
> The last testcase is failing, although this worked in previous versions of
> Chameleon.
I've committed this.
These seem like fairly critical regressions; I'll try to lo
Malthe Borch added the comment:
I'm not sure I understand exactly.
If you have the time, please demonstrate this with a failing test (commit if
you can, we can always
change our collective minds on it later).
Failing tests are great because they prevent immature releases.
--
s
On 27 February 2010 12:10, Uli Fouquet wrote:
> While trying to make megrok.chameleon compatible with zopetoolkit and
> groktoolkit package versions, I noticed that latest z3c.pt (1.1.0) and
> trunk are not completely compatible with Chameleon >= 1.1.0. The tests
> fail.
Do you think you can find
On 12 February 2010 21:03, Iain Duncan wrote:
> Been out of the loop for a bit, did Chameleon Genshi get match template
> support yet? I know Malte mentioned it was a possibility about six months
> ago or so.
Not yet, sadly.
\malthe
___
Repoze-dev mail
On 4 February 2010 13:48, Tim Hoffman wrote:
> Do you mean it parses all templates on instance startup. If so that
> would be prohibitively expensive
> if you have a lot of templates.
Yes.
> And startup time (just processing all
> the zcml, and all the other imports) is problematic as it is.
>
On 4 February 2010 06:21, Tim Hoffman wrote:
> So does this mean compiled code (.py) is deployed or does it parse -
> generate etc on each instance startup
> and possibly cache generated code in the module . given you can't
> write to the filesystem.
It parses and generates and each insta
We're currently using an obscure feature of the expat parser library
``CurrentByteIndex`` for at least two purposes: tricking expat into
giving us the raw text without resolving entities, and to parse
fragmented documents (e.g. with more than one top-level node).
This does not work on Jython.
An
On 1 February 2010 18:47, georgehu wrote:
> It worked without problem with other language such as "de". Is it a
> problem of chameleon.zpt?
Try and upgrade to 1.1.1, the post back.
The normal process with bugs in Chameleon has been that a failing test
is committed, then I'll usually get around t
On 1 February 2010 00:33, Chris McDonough wrote:
> It's OK by me, although I might forget to read the identi.ca group as I
> already
> have trouble keeping up with email, IRC and twitter.
I think it could be useful if this group/channel would broadcast to
the IRC channel as well; many of us prob
On 29 January 2010 11:51, Hanno Schlichting wrote:
> Ah right. Chameleon has a hard dependency on zope.i18n right now, I
> forgot. Not working with BFG nor Chameleon in any projects doesn't
> help to remember these things :)
There's no hard dependencies in Chameleon at this time.
\malthe
___
2010/1/27 Brian Sutherland :
> So in the next week or so, I will try re-implement regular expressions to
> find and replace the
> tags. Given that malthe seems to think it's a reasonable idea I'll do
> it inside repoze.bitblt
> on a branch first.
Please do it on trunk, and do it well. I've want
2010/1/26 Tim Hoffman :
> So whats the secret , pre-compile everything ?
Same procedure as last year, except we now use the compilation hoops
from Genshi which makes it work, plus some rewrites of our code
transformation logic.
\malthe
___
Repoze-dev ma
Deep in the mountains of Austria, during a snow storm, Chameleon
became compatible with Google App Engine.
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev
2010/1/12 Chris McDonough :
> But ethically this is Malthe's code, and the code itself has no license text
> in
> it. On chameleon.repoze.org he states "Chameleon is covered by the BSD
> License." So I'll ask him to clarify which BSD license he means.
BSD, as-is, dont-care.
As for LICENSE.txt,
2009/12/15 Diez B. Roggisch :
> I guess the question has been asked before, and I'm aware that the state of
> python 2.5 support is ultimately a zope-issue.
Python 2.5 is supported since two years. We commonly use Python 2.6 though.
\malthe
___
Repoze-d
2009/12/10 george hu :
> I have a submit button with value in Chinese string, some thing like:
>
This has been fixed (now) in r7593. Please confirm on your end.
Thanks,
\malthe
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repo
2009/11/27 george hu :
> I'm trying to use zpt to render a nested list and I found an example in the
> mail list of zope,
Try this:
http://pastie.org/722303
The problem you had was that the macro will be defined only after the
tal:repeat operator; you need to split these up. In general, it's
ina
2009/12/1 Martin Aspeli :
> Lest I offended anybody, I would like to insert an additional smiley at
> the end of that last sentence, like so:
>
> ;-)
I think there was no offense, but it is only fair to mention that the
British are very much at war right now, displaying a great ignorance
on a dai
2009/11/27 george hu :
> does any body know what is the problem here?
I would suggest that you first use the ``CHAMELEON_CACHE=1`` and
``CHAMELEON_DEBUG=1`` environment flags to be able to inspect and
step-debug through the template code.
Ideally you would be able to step-debug directly in the te
2009/11/25 Alberto Valverde :
> Everything works fine when I request the application/json and
> application/json+xconfig mimetypes with a xhr since I can control the
> "Accept" header, however, when a browser makes a "normal" request the result
> is unpredictable (in practice) since '*/* is sent in
2009/11/23 Iain Duncan :
> Hey folks, just floating the idea of splitting the issue tracker
> mailouts on to their own mailing list? In my experience on this and
> other lists, it's a lot more pleasant to read the mailing list without
> having to scroll through the issue tracking comments. Just a t
Be careful when using "legacy" Zope packages; if you import them
before the BFG thread-local patch, they might register components with
the global base components registry instead of your app's registry
(because the ``getGlobalSiteManager`` object is imported and used for
registration).
\malthe
__
Malthe Borch added the comment:
Speed matters; ``lxml`` is very fast and does not incur any significant
overhead. I feel that
BeautifulSoup would (this might not be correct).
Regular expressions are very fast, and sometimes brittle. Everything's a
compromise.
However, image-tag
2009/11/12 F. Oliver Gathmann :
> I guess I'm asking if there is a standard, "bfg-approved" way of avoiding
> artificial container model classes - or did I just "not get it" yet?!
You can use ``*subpath`` (or any other name of your choice) to
retrieve this match as-is, without invoking the travers
Malthe Borch added the comment:
I've applied this patch, slightly altered.
--
status: unread -> chatting
__
Repoze Bugs
<http://bugs.repoze.org/issue106>
__
Malthe Borch added the comment:
Perhaps we can use ``lxml`` to extract the locations (string start-
and end- ranges) for the tags and then simply use regex
matching on those.
This way, the original document isn't changed, but we don't have the
pitfalls of
2009/11/11 Damien Baty :
> Malthe, I think you have replied to the wrong ticket. The patch I described
> has
> not been applied (and regular expressions, well, we can use them everywhere,
> of
> course, but... ;) )
Perhaps we can use ``lxml`` to extract the locations (string start-
and end- rang
Malthe Borch added the comment:
I see this patch has already been applied.
Perhaps we should consider using regular expressions to do this. Chances are
that it'll be a) faster, b) less intrusive.
--
status: unread -> chatting
__
Repoze Bug
2009/11/4 Damien Baty :
> For the record, this issue has been fixed today in r6960.
Great!
> I wrote a few months ago (08/06/09):
Sorry, I have that e-mail starred since June. I guess I can unstar it now :)
\malthe
___
Repoze-dev mailing list
Repoze-d
2009/11/2 Martin Aspeli :
> I think it's better to use top-level namespaces to indicate ownership,
> if nothing else to avoid the chance of things clashing. For the repoze
> project to "claim" the wsgi.* namespace seems both a bit presumteuous
> and clash-prone.
It does not a claiming of a namespa
Perhaps packages which provide middleware functionality should be
named ``wsgi.*``, e.g. ``wsgi.bitblt`` or ``wsgi.who`` and we'd opt
similar namespaces for packages that belong to other realms.
I'm not sure this ``repoze.*`` notion is very healthy in terms of
getting traction outside the Zope-com
I've repackaged ``chameleon.core`` and ``chameleon.zpt`` into one
package, ``Chameleon``.
Repository:
http://svn.repoze.org/chameleon/trunk/
Note that this egg does not have a hard dependency on the ZCA
libraries, or ``zope.i18n``.
The first release has been given the version 1.0.
During th
2009/10/31 Michael Mulich :
> I was using the get_template approach in my application to gain access
> to a macros templates prior to looking at repoze.bfg.skins. Using a
> view that returns a dictionary and a renderer that points to a page
> template (.pt file) that uses the skin expression defin
2009/10/24 Tres Seaver :
> No, it works fine for values wich aren't markup: if you want a variable
> containing markup to be rendered without escaping, you need the
> 'structure' directive in TAL: the shortcut always escapes markup.
Alternatively, wrap your ``addform`` value as a literal (``from
2009/10/23 Chris McDonough :
> I don't think there's anything in particular in the way. I'd like to have
> some concrete use cases before we add the code, because it could be
> difficult to document.
We have this particular use-case (we might not have it anymore, but
for the record):
You want tr
2009/10/22 Chris McDonough :
> Do we just need to change the path matching syntax instead to get your
> *.html case to work? Is there another case for predicates?
I think that in general, predicates make sense without the view on
s. Is there anything in the way of letting them act upon
``route.ma
2009/10/22 Tres Seaver :
> The view predicates are there to allow selecting a particular view among
> several registered for the route or context: e.g., to dispatch to
> different views for GET versus POST for the same route / context and
> view name.
It makes perfect sense with .
With , however
Currently the predicates pertain only to views, regardless of whether
they're declared using a or a directive (or using the
``bfg_view`` decorator).
I would expect that if you declare a predicate on the route, that the
route would only be used if that predicate matches. Instead, the route
is use
For essentially static content or other cacheable content, edge-side
includes are an attractive way to provide personalized o-wrap (e.g.
"Hello, %{your_name}") on high-volume sites. This is a proposal for a
middleware which makes it easy.
The setup is a WSGI-application which returns cacheable HTM
2009/10/3 Iain Duncan :
> Hey folks ( or rather Malte! ), wondering whether there are plans to
> include full match template support in chameleon.genshi? Is such a thing
> possible while still retaining speed?
It is possible; I've previously outlined an idea for an
implementation. It's not easy th
2009/9/26 Iain Duncan :
> Sorry if this is the wrong place to ask this, if it is, please let me
> know where I should. Wondering if anyone can tell me what is necessary
> to display html coming from template variables with chameleon.genshi? IE
> what would have been ${HTML(var_with_html)} in genshi
2009/9/12 Chris McDonough :
> At some point I had considered using a Chameleon expression prefix to
> separate these sorts of "builtin" names from the main template namespace
> names. For example, instead of "tal:replace="href api.context_url",
> you'd access builtins via an expression type, e.g.
2009/8/24 Chris McDonough :
> Malthe said it might be possible to register one or more new TAL expression
> types (each of which might represent a namespace) so templates could do
> something like tal:content="api:something" (note colon instead of dot) to get
> top-level names instead. The view wo
Alberto Valverde wrote:
> Attached is a patch with a doctest showing the error.
Applied and fixed in r5971. Thanks!
\malthe
___
Repoze-dev mailing list
Repoze-dev@lists.repoze.org
http://lists.repoze.org/listinfo/repoze-dev
Currently ``repoze.who`` meets the demand for application-agnostic
user authentication (identification, sign-off) and population of
metadata.
This is a proposal to extend the set of plugins that can be registered
through the ``repoze.who`` middleware.
CRUD:
Create, read, update and delete identi
1 - 100 of 179 matches
Mail list logo
