Simon Willison wrote:
> Silent errors are bad. If we were to remove them, how much of a
> negative impact would it have on the existing user base?
+1 from me.
I always set TEMPLATE_DEBUG to True and TEMPLATE_STRING_IF_INVALID to
something that stands out, during development.
--
Nicola Larosa -
koenb wrote:
> For those interested in multiple database support, I have started
> working on it again, and posted my work-in-progress to ticket #4747.
> ...
> Anyway, if anyone is interested in helping, please let me know!
I am going to need this in a month or so. Actions speak louder than
words
Daryl Spitzer wrote:
> If I don't, I see if I can at least make enough time to write up the API
> I came up with at PyCon.
Please do, that would be great.
--
Nicola Larosa - http://www.teknico.net/
--~--~-~--~~~---~--~~
You received this message because you are s
Johannes Dollinger wrote:
> Of course that's subjective, everything is.
You're in the wrong line of work, man... ;-)
--
Nicola Larosa - http://www.tekNico.net/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Djang
Jacob Kaplan-Moss wrote:
> The best way to help out right now is to grab the "docs-refactor"
> branch from my git repo
Hereby convened, we mourn the untimely demise of the "toys" hg repo:
by many will it be sorely missed, time and again, bringing tears to
the cheeks of the afflicted.
But no! Don
I have a use case for compressed fixtures too.
> Jeremy Dunck wrote:
>> I'd like to add support for fixture load/dump to deal with compressed
>> (gzip) files transparently.
Jacob Kaplan-Moss wrote:
> I don't see a good reason *not* to do this, but I also don't see the
> space requirements as a b
> Welcome, Nicola! And thanks very much for your documentation patch;
> I've committed it.
You're welcome. BTW, there's more where that came from: see the same
ticket (#1815).
--
Nicola Larosa - http://www.tekNico.net/
--~--~-~--~~~---~--~~
You received this me
> /me makes another note to spend some serious time with BZR...
Try spending some time with Mercurial, too. It's simpler, smaller and
faster than Bazaar-NG, while also being written in Python, with a
little C.
--
Nicola Larosa - http://www.tekNico.net
--~--~-~--~~~
> I can't find it now, but I recall reading on the Mercurial site that it
> doesn't support versioning directories, which seems like an awful step
> back into cvs-land. Maybe I misunderstood?
Directory versioning is obviously supported. There are some limits on
renaming:
http://www.selenic.com/p
> Sorry for the OT post, but what do people use for arbitrary
> precision decimals in Python?
>
> I would think it's in the standard libraries somewhere, but I
> must be googling the wrong terms.
It's called... [drum roll]
decimal! ;-)
http://docs.python.org/lib/module-decimal.html
--
Nicola
>> Works like a charm. (I'm hardly an svk expert, though, so there are
>> probably easier/less verbose recipes for doing the same thing.)
> If only Darcs were the norm...
As far as distributed VCSes go, I'd like to cast my vote for Mercurial.
It's a little Python jewel, as fast as Git, more con
Ilias Lazaridis is a known Internet troll.
http://www.encyclopediadramatica.com/index.php/Ilias
Let's stop feeding him/her/it, it's just a waste of time.
--
Nicola Larosa - http://www.tekNico.net/
Users know the business better than you do, whoever you are.
If you are willing to learn, you can
C8E wrote:
> and maybe also
>
> http://www.encyclopediadramatica.com/index.php/Ilias
>
> ;)
Didn't want to steal your thunder, pal, but since you weren't speaking
up, I did. Thanks for that URL! :-)
--
Nicola Larosa - http://www.tekNico.net/
--~--~-~--~~~---~--~---
This post on django-users:
http://groups.google.com/group/django-users/msg/7d4773cccde8d51d
manifests some interest in moving the old-style classes to new-style:
with some fairly short grunt work I made a patch about it, and attached
it to ticket #2109:
http://code.djangoproject.com/ticket/2109
Adrian Holovaty wrote:
> The try/except in this case is meant to handle the case in which
> somebody is using newforms without the rest of Django, which was an
> early goal of mine. Since then, I've sort of resigned myself to
> requiring Django, due to ties into the internationalization hooks and
Brian Beck wrote:
> So I'm working on a stateless sessions app that people will be able to
> swap with django.contrib.sessions in their settings if they need that
> (a recent post mentioned mobile phone browsers for example, apparently
> they don't support cookies?). I don't actually care that muc
On 11 Gen, 22:34, "Joseph Kocherhans" <[EMAIL PROTECTED]> wrote:
> I'd love to use a dictionary, but the order of backends matters. I
> wish python had a decent syntax for what basically amounts to an
> ordered dict.
It's a FAQ, and bait for flamefests, here's a big one:
http://groups-beta.googl
On 13 Gen, 06:02, "SmileyChris" <[EMAIL PROTECTED]> wrote:
> We need to come to a consensus on Django autoescaping
There's an interesting discussion on GvR's blog, with several mentions
of escaping:
http://www.artima.com/forums/threaded.jsp?forum=106&thread=146606
Speaking of Django 1.0, it als
Vadim Macagon wrote:
> I'd also like to see a script that generates a CHM (Compiled HTML Help)
> from the official Django ReST docs. The CHM could then be included as
> part of the installer-based release for Windows users. One of these days
> I'll probably get fed up waiting for the pages on djan
Malcolm Tredinnick wrote:
> But it's all "git" under the covers. I wrote up a brief description when
> I started using this a few months ago:
> http://www.pointy-stick.com/blog/topics/software/version%20control/ .
(I know, I should have directly commented on that page, and I would
have, if there
Dear devs,
please apply the patch in ticket #3364 as soon as possible.
There's still people around that do not use PsycoPG 2, because of that
obsolete note in doc/install.txt .
Thank you.
--
Nicola Larosa - http://www.tekNico.net/
I've heard that some people have a saying: "Pain is weakness le
Russell Keith-Magee wrote:
> I've just committed [12003], which reverted commit [12000].
Sorry, my bad: couldn't resist the nice rev number. ;-)
> This mirrors commit [11941], which reverted [11881]. These commits all
> relate to translation updates for the 1.0.X branch.
>
> Translations should
22 matches
Mail list logo