On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>
> Jacob Kaplan-Moss wrote:
> > On May 25, 2006, at 11:27 AM, lazaridis_com wrote:
> >
> >> At this point, Django's persistency layer seems intresting, but the
> >> evaluation uncovered a few weaknesses, most importantly the lack of
> >> sche
On 6/1/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>
> [EMAIL PROTECTED] wrote:
> > You can try this EnergyKey
> > http://www30.webSamba.com/SmartStudio
> > This may be help you.
> > Now I always use EnergyKey, it helps me so much in my work.
>
> very intresting tool!
There's an interesting ph
On 6/14/06, Uros Trebec <[EMAIL PROTECTED]> wrote:
>
> 2.1. Basic models:
> To enable history tracking Bob has to create a sub-class for those
> models that he will like to track:
>
> class Post(models.Model):
> author = models.CharField(maxlength=100)
> tit
On 6/20/06, Simon Willison <[EMAIL PROTECTED]> wrote:
>
> On 20 Jun 2006, at 16:25, James Bennett wrote:
>
> > Security by annoyance is security that people learn to hate and turn
> > off as soon as they can, so in the end it doesn't really make them any
> > more secure than they were before.
>
>
On 6/21/06, oefe <[EMAIL PROTECTED]> wrote:
>
> Agreed.
> To prevent XSS vulnerabilities because someone forgot to specify the
> escaping rule, I would suggest that templates should, maybe even must
> specify their escaping. For example, require each template to contain a
> special {% autoescape
On 6/27/06, toth anna <[EMAIL PROTECTED]> wrote:
>
> Is there any (elegant) opportunity for a "container level
> logic". For example, there can be only 5 from a specific
> type of item, and inserting a new, we have to delete oldest
> object.
> Or when saving an object, container "splits" it, and c
On 6/27/06, toth anna <[EMAIL PROTECTED]> wrote:
>
> Tom Tobin <[EMAIL PROTECTED]>:
> > You should be able to get the behavior you want by
> overriding the
> > save() method on your models.
>
> Is there any usable examples somewhere for me?
Here's the
On 6/27/06, Tom Tobin <[EMAIL PROTECTED]> wrote:
> On 6/27/06, toth anna <[EMAIL PROTECTED]> wrote:
> >
> > Tom Tobin <[EMAIL PROTECTED]>:
> > > You should be able to get the behavior you want by
> > overriding the
> > > save() method on yo
On 7/16/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> I have put an initial version of the auto-escaping patch I mentioned
> yesterday into ticket #2359. I'll briefly describe what it does below.
> The patch includes changes to the core and a test suite for the
> auto-escaping changes (whi
On 7/16/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hi django-developers,
>
> I had the need for a field type similar to USStateField: an
> OlympicNationField which takes 3 uppercase letters to the official olympic
> nation abbrevation.
I would feel better using ISO 3166-1 country codes
Jacob sits a couple of seats over from me, and he's on his way out the
door; he says he'll take a look as soon as he gets home. :-)
On 7/18/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> It looks like I just got blacklisted when I tried to post the
> compilation of tutorails that i mentio
On 7/24/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Don't mean to pester but is there a way for me to post the list on the
> wiki? Like I said, I think I'm blocked now. :(
Ouch, I'm sorry. :-( I'm sure Jacob meant to get back to you, but I
know he's been insanely busy with preparations
On 7/27/06, Joe <[EMAIL PROTECTED]> wrote:
>
> Adrian Holovaty wrote:
> >
> > There's no real reason, other than the fact that the core developers
> > all use (and are happy with) the Subversion/development versions of
> > Django, with which we've been enjoying the great changes to Django
> > over
On 7/27/06, Joe <[EMAIL PROTECTED]> wrote:
>
>
> Tom Tobin wrote:
> > In line with other sentiments I've expressed here in the past: IMHO,
> > this means your *project manager* is addled, not Django's release
> > process. If you can understand that the
On 7/27/06, Tom Tobin <[EMAIL PROTECTED]> wrote:
> On 7/27/06, Joe <[EMAIL PROTECTED]> wrote:
> >
> >
> > Tom Tobin wrote:
> > > In line with other sentiments I've expressed here in the past: IMHO,
> > > this means your *project manager* is
On 7/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
> Tom Tobin wrote:
> > On 7/27/06, Joe <[EMAIL PROTECTED]> wrote:
>
> > In line with other sentiments I've expressed here in the past: IMHO,
> > this means your *project manager* is addled
On 7/27/06, Luke Plant <[EMAIL PROTECTED]> wrote:
>
> Unless I missed something, the default escaping proposal hasn't been
> committed. And I've had an idea that I don't think came up, that I
> thought was perhaps worth throwing into the mix.
>
> Basically, {{ }} does escaping automatically, a
On 8/4/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> As someone who spends most of my day job working in Djangos' template
> system, I can say that I would also prefer the same evaluation as Gary
> 99% of the time. I really think it should be the default.
I have to concur with Jeff; while
On 8/4/06, Ahmad Alhashemi <[EMAIL PROTECTED]> wrote:
>
> In Rails, template tags can have an extra hyphen at the end to denote
> the fact that they should consume the newline right after the tag. So:
>
> {% some_tag %}
>
> Would look like this:
>
> {% some_tag -%}
I can't help but feel that this
After two far too-long days at work, far too much head-to-desk banging
at home, and a rather stupid aha-I've-got-it, oh-wait-I-don't,
I-need-sleep on Django-users, I've come to the conclusion that post-MR
Django doesn't support manipulator-aware validators. This was
possible in pre-MR-removal ver
On 8/9/06, Tom Tobin <[EMAIL PROTECTED]> wrote:
>
> I've already gotten the first case working, and I'll tackle the second
> after work tomorrow; I'll report back with my thoughts after comparing
> the two.
I actually implemented the second case (a ``takes_manipu
On 8/9/06, Tom Tobin <[EMAIL PROTECTED]> wrote:
> I'd like to restore this ability to Django trunk; there are a couple
> of ways I could go about this, and I'd like input as to which would be
> cleaner:
I came up with a third possible way of handling this (which is nearl
On 8/11/06, James Bennett <[EMAIL PROTECTED]> wrote:
>
> On 8/11/06, Karl Guertin <[EMAIL PROTECTED]> wrote:
> > I'll admit that I haven't really looked into how the admin system
> > works post-magic removal but I could work 90% of the extensions I want
> > if I could 1. register a callback for ch
On 8/11/06, Tom Tobin <[EMAIL PROTECTED]> wrote:
> On 8/9/06, Tom Tobin <[EMAIL PROTECTED]> wrote:
> > I'd like to restore this ability to Django trunk; there are a couple
> > of ways I could go about this, and I'd like input as to which would be
> > c
On 8/16/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> I have the same. I've tried to clean up the main wiki page and it
> rejects the changes.
Core-dev-types: would it be okay to whitelist these guys?
--~--~-~--~~~---~--~~
You received this message because
you.
Once I do this, you won't trigger the "Akismet rejected spam" or any
other spam-rejection errors.
Tom Tobin
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django develop
On 8/26/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Akismet thinks this bug is spam, so I cannot submit it to Trac.
If you're being locked out due to the spamfilter (and this goes for
anyone else), please email me with your IP (or IP range) or, if you
have a wide dynamic IP range, the long
On 8/28/06, Joel Heenan <[EMAIL PROTECTED]> wrote:
>
> I have noticed there is a great number of patches like mine that don't
> ever seem to be reviewed and all seemed to be assigned to Adrian but
> he seems to be concentrating on new features at the moment. As someone
> who wants to contribute to
On 8/30/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> I would agree if you take 'False' as a real string which shouldn't evaluate
> to False, but I had the following templatetag called:
>
> {% mytag "some string" False %}
>
> Which now resolved in an error:
I'm wondering why you need to p
On 8/31/06, antonio <[EMAIL PROTECTED]> wrote:
>
> Anyhow, this week, we completed our migration to 0.95 and magic removal
> which was painful but has shown us how much more great work you guys
> have been up to. Before the move, we were running on a hacked version
> of 0.91 that we had spent some
On 4/16/07, James Bennett <[EMAIL PROTECTED]> wrote:
>
> Short and sweet: since we're already planning some
> backwards-incompatible changes for the next release, how about we
> hammer out auto-escaping of template output while we're at it? Even
> those of us who don't like it (myself included) ar
On 4/17/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
> >
> > I'm still -1 on autoescaping as implemented in the latest patch in
> > #2359; the terminology used is strongly HTML-centric (e.g.,
> > ``convert_to_words.is_safe`` -- safe from what?). We should be using
> > naming that makes it expli
On 5/14/07, Luke Plant <[EMAIL PROTECTED]> wrote:
>
> On Tuesday 15 May 2007 01:09:08 Secret wrote:
> > There is a section below with the title "Atheism and Evolution are
> > WRONG."
> >
> > All those who have sinned deserve to suffer in Hell forever. "Pride"
> > is an example of a terrible sin.
>
On 11/28/05, Amit Upadhyay <[EMAIL PROTECTED]> wrote:
> <% include template_name %> includes the named template which is like
> get_template of the Python API for loading templates, for consistancy we
> should have a comma seperated template list similer to select_template.
> (Untested) Patch atta
On 11/28/05, Amit Upadhyay <[EMAIL PROTECTED]> wrote:
> On 11/28/05, Tom Tobin <[EMAIL PROTECTED]> wrote:
> > Please submit patches (along with tickets) to Django's Trac at
> > http://code.djangoproject.com/
>
> Done: http://code.djangoproject.com/ticke
On 11/28/05, Amit Upadhyay <[EMAIL PROTECTED]> wrote:
> Just that I felt dropping a mail on the list gives a little more visibility
> and opportunity to get feedbacks, than just filing a ticket, which only a
> handful of core-thus-busy developers monitor.
Hmm, I actually have the opposite impress
I'd be interested in feedback on ticket #919, which implements a
"random" tag which parallels the functionality of the random filter.
I'd also be curious as to where the best place would be to implement a
possible helper class for the weighted random option, as I was
considering making the weight
On 11/29/05, Amit Upadhyay <[EMAIL PROTECTED]> wrote:
> What is the use case of this tag? This looks like logic, template in
> philosophy dictates the layout of the data generated in the views. Putting
> weights for example, is it not more of a logic than presentation?
Some measure of logic is na
On 11/29/05, Tom Tobin <[EMAIL PROTECTED]> wrote:
> I'd be interested in feedback on ticket #919, which implements a
> "random" tag which parallels the functionality of the random filter.
I've split out a weighted random class, `RandWeight`, that lives in
`dj
On 12/2/05, Tim Keating <[EMAIL PROTECTED]> wrote:
>
> -1 from me. As a *user*, I would much rather just generate random
> content inside of my view code.
I'm surprised this makes you -1 rather than -0; do you hate it that much? :-)
> I'd like to point out the cited example
> (random photo on F
On 12/3/05, Tim Keating <[EMAIL PROTECTED]> wrote:
>
> "Hate" is too strong a word. However, I do feel that this is not a
> positive addition.
> My apologies, I hate to be negative about someone else's hard work.
Don't worry, I'm merely poking back in jest; I asked for criticism in
the first pla
On 12/15/05, Robert Wittams <[EMAIL PROTECTED]> wrote:
>
> Basically, promote Admin settings to a full inner class, rather than
> nesting it in meta. It would still end up in meta though.
+1; the improvement in readability would be welcome. The Admin
declarations are too visually messy at the mo
Since the idea of incorporating Dojo as Django's AJAX toolkit was
brought up, I've been researching the toolkit; I must admit that I'm
bothered by statements from the project regarding its licensing on the
Dojo-interest mailing list -- specifically, claims by the project
about the Academic Free Li
On 1/10/06, Antonio Cavedoni <[EMAIL PROTECTED]> wrote:
>
> Maybe we could start a "unicode" branch right after "magic-removal"
> is merged back into the trunk?
+1 to that; I'd rather not see magic-removal last forever as a
"catch-all", diverging further and further from trunk. :-)
On 1/12/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Hello,
> In my recent project I have been finding myself wishing that the {%
> ifequal %} tag had support for AND OR.
Have you considered passing a boolean into the template from the view
with the corresponding value? I don't think the
On 1/12/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> I like this a lot! SimpleContext is good...Other thoughts?
BaseContext?
I opened ticket [1259] as it seems that there's a mismatch in
magic-removal between aspects of the admin interface regarding model
names being referenced as singular or plural. I believe there was
recent discussion on standardizing to singular model names; if someone
can confirm which way this is
On 1/22/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> I've been messing with manipulator code in magic-removal, and it
> struck me that we could avoid a lot of the boilerplate, cruft and
> newbie confusion by making models validation-aware.
+1; this would even be useful in non-standard scena
On 1/27/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
>
> I haven't been following the magic removal branch closely, but here:
> http://code.djangoproject.com/wiki/RemovingTheMagic
>
> There is a migration script for mysql. This line looks wrong:
> ALTER TABLE auth_groups_permissions RENAME TO auth
On 2/3/06, Brian William Kaplan <[EMAIL PROTECTED]> wrote:
>
> I'm not able to write the patch because Django is placing too many
> restrictions on what I can do as far as this.
Err, simply because some people are raising concerns about the
proposed implementation? Or do you mean something to do
On 2/9/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
> On 2/10/06, limodou <[EMAIL PROTECTED]> wrote:
> >
> > I'v summited a ticket
> http://code.djangoproject.com/ticket/1337 for this.
> >
> > What do you think about?
>
> -1 from me.
I second that -1; by the logic in that ticket, we migh
On 2/12/06, limodou <[EMAIL PROTECTED]> wrote:
>
> I don't want to touch this subject more. If you don't understand I'll
> explain it again:
I think we understand what you're saying; the problem is that we don't
agree. ;-)
As others have pointed out, it is perfectly acceptable to create your
ow
I know things have been fairly set on Dojo as of late, but I thought
I'd give a heads-up as to Yahoo's new offering, the Yahoo User
Interface Library. It's BSD 3-clause licensed, and seems to cover
AJAX, visual effects, and widgets.
http://developer.yahoo.net/yui/
On 2/14/06, limodou <[EMAIL PROTECTED]> wrote:
>
> On 2/15/06, Tom Tobin <[EMAIL PROTECTED]> wrote:
> >
> > http://developer.yahoo.net/yui/
> >
> Yeah, I'v seen it also. It sounds good and the documents are also
> well. But the widgets seems not very
There currently seems to be a bit of redundancy with regards to the
"blank" and "null" field options; tickets #1043 and #1353 seem to be
the inverse of one another, each addressing that one must specify both
blank=True and null=True to get the expected behavior (i.e., being
able to specify and save
On 2/18/06, Luke Plant <[EMAIL PROTECTED]> wrote:
>
> On Saturday 18 February 2006 23:27, Tom Tobin wrote:
> > Is there a scenario in which it would be
> > useful to only specify one of these options, and not the other, for
> > non-string fields?
>
> I have
When working with and troubleshooting forms, it can be a common
mistake to have a particular field be required yet not present in the
form. Currently, such a case will lead to a "please correct the
error(s) below" message without those errors in question actually
being displayed, as the errors are
On 2/20/06, hugo <[EMAIL PROTECTED]> wrote:
>
> >There currently seems to be a bit of redundancy with regards to the
> >"blank" and "null" field options
>
> So I am -1 on the proposal to get rid of one of those two. Every
> combination (even null=True and blank=False - think about legacy data)
> ma
On 2/20/06, hugo <[EMAIL PROTECTED]> wrote:
>
> blank=True with implicit null=True isn't probably what users would
> expect when applying it to charfields. And having a rule where
> charfields have null=False in combination with blank=True and
> non-charfields have null=True with blank=True is rath
On 2/24/06, Luke Plant <[EMAIL PROTECTED]> wrote:
>
> On Friday 24 February 2006 23:36, [EMAIL PROTECTED] wrote:
>
> > magic-removal: Removed 'init-minimal', which wasn't doing anything
> > useful
>
> It seems to be used by runtests.py...was this an oversight Adrian?
Yeah, that one caught me by su
On 2/24/06, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
>
> As I was creating init-minimal I thought it would actually do
> something, but as I reorganized the modules, it looked more and more
> like it wasn't needed at all. (I certainly thought it would be
> necessary before I started though.) So
On 2/25/06, ChaosKCW <[EMAIL PROTECTED]> wrote:
>
> Hi
>
> I have raised the following ticket:
> http://code.djangoproject.com/ticket/1399
>
> I propose adding a new paramter to the list_detail.py generic view to
> allow you to name your model/objects to something other than 'object'
> or 'object_l
On 2/25/06, Luke Plant <[EMAIL PROTECTED]> wrote:
>
> How likely is it that you will reuse that for a different type of
> object? Even if you do, it is pretty likely that any object which has
> the same interface as my 'person' example could be called
> 'person' (even if it was really 'Customer',
Having found myself fiending for regular expression lookups in Django,
I implemented the behavior in ticket #1465. It has a few caveats:
case-sensitive regexes only work in PostgreSQL, PCRE-ish regexes only
work in PostgreSQL and sqlite (the other backends use POSIX "extended"
regexes), and regula
On 3/6/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> On Mar 4, 2006, at 3:36 PM, Tom Tobin wrote:
> > Furthermore, it implements a slightly
> > backwards-incompatible change with regards to the admin interface:
> > regular expression searches can be p
On 3/7/06, Luke Plant <[EMAIL PROTECTED]> wrote:
>
> The new python site went live: http://www.python.org/
>
> And Django is on the front page. Sweet.
Although it would irk me a bit less if they dropped the silly "mega-"
prefix. :-p
--~--~-~--~~~---~--~~
You recei
On 3/8/06, Christopher Lenz <[EMAIL PROTECTED]> wrote:
>
> The patch reverts some changes (such as the removal of core fields)
> which were never really completed. While I'm aware that a much
> improved version of edit_inline is on the way (using Dojo/AJAX and
> all that), I think that the branch s
On 3/13/06, Kieran Holland <[EMAIL PROTECTED]> wrote:
>
> I don't like the idea of arbitrary content in template tags either but does
> your "definite no" also apply to this old idea:
>
> {% endif %}{# endif start_process #}
>
> I think comments should be encouraged in templates and the
> comment/e
On 3/14/06, Eugene Lazutkin <[EMAIL PROTECTED]> wrote:
>
> Kieran Holland wrote:
> >>>
> >>> {% endif %}{# endif start_process #}
> >> I think that original idea is cleaner: {% endif start_process %}.
> >
> > Perhaps in this case, but I would prefer we don't do special-case
> > solutions to what is
On Sat, Jun 7, 2008 at 2:06 PM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
> * Wait for newforms-admin to be done, merge it, and release 1.0 (well,
> a series of beta/rcs, then final). This has been "plan A" all along.
+1; this is The Right Thing.
> * Release an interim release right away to r
On Tue, Jun 10, 2008 at 7:13 PM, Russell Keith-Magee
<[EMAIL PROTECTED]> wrote:
>
> However, I'm happy to defer to
> someone with a higher degree in grammarnazism.
With that in mind, I whipped out my copies of the Chicago Manual of
Style and Garner's Modern American Usage last night.
And came up
The Django community aggregator includes non-English posts, which are
unfortunately pure noise for those of us who don't understand other
languages. Can we either restrict the aggregator to English posts, or
at least create sub-feeds for English and non-English posts?
I don't mean to tread on th
On Fri, Jun 13, 2008 at 11:01 AM, pi song <[EMAIL PROTECTED]> wrote:
> Are they real posts? I thought just spam.
They certainly *look* like real posts, but I can't understand anything
outside of the technical (English) terms used. :)
--~--~-~--~~~---~--~~
You rec
On Fri, Jun 13, 2008 at 11:05 AM, Arien <[EMAIL PROTECTED]> wrote:
>
> On Fri, Jun 13, 2008 at 10:58 AM, Tom Tobin <[EMAIL PROTECTED]> wrote:
>>
>> The Django community aggregator includes non-English posts, which are
>> unfortunately pure noise for th
On Fri, Jun 13, 2008 at 11:31 AM, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
> I propose an option on the side of the page that asks whether or not
> to translate the posts into english. The google translator is fairly
> effective and a lot of the russian posts I have looked at have bee
> ver
On Fri, Jun 13, 2008 at 11:33 AM, Alex Koshelev <[EMAIL PROTECTED]> wrote:
>
> It is not a problem. Just skip non-English posts at all. English is
> international language of cource but not the one.
Except it *is* a problem when I'm forced to deal with a regular influx
of what is, to me, *noise*
On Fri, Jun 13, 2008 at 12:02 PM, Arien <[EMAIL PROTECTED]> wrote:
>
> The non-English posts are clearly useful to the Django community as a
> whole, as it appears that the majority of its members don't speak
> English as their native tongue.
I'm totally fine with non-English feeds being availabl
On Fri, Jun 13, 2008 at 12:04 PM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
>
> I'll look into setting up language-specific feeds (and a general
> non-English one). If it's easy, I'll do it. If not, anyone is welcome
> to look at the djangoproject.com source and submit a patch; I'll
> happily a
On Fri, Jun 13, 2008 at 12:07 PM, Marty Alchin <[EMAIL PROTECTED]> wrote:
>
> There's an aggregator, IRC log, various mailing list archives, wiki
> articles, ticket comments, localized community sites, the list goes on
> and on. In the spirit of community-oriented sites (like djangosites,
> django
On Fri, Jun 13, 2008 at 12:27 PM, Alex Koshelev <[EMAIL PROTECTED]> wrote:
> -100
>
> Non-English post isn't noise!
>
> Some English posts has more less profit then non-English ones.
*To me*, someone who can't read them, yes, they're noise. I'm sorry.
If I can't read it, it does nothing for me b
On Fri, Jun 13, 2008 at 12:23 PM, Alex Koshelev <[EMAIL PROTECTED]> wrote:
> There is existing multi-lingual aggregator http://djangosearch.com/
That's just been mentioned in the new "djangochatter" thread as well
... very interesting. Continuing over there.
--~--~-~--~~
On Fri, Jun 13, 2008 at 12:25 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Also for anyone interested, there's this:
>
> http://djangosearch.com/
Well. Damn. That looks like what we're talking about here.
I wonder if it indexes everything the "official" aggregator does?
--~--~
Bah, simultaneous thread-splitting. Send any replies to the other
"djangochatter" thread.
On Fri, Jun 13, 2008 at 12:23 PM, Tom Tobin <[EMAIL PROTECTED]> wrote:
> On Fri, Jun 13, 2008 at 12:07 PM, Marty Alchin <[EMAIL PROTECTED]> wrote:
>>
>> There's an
On Fri, Jun 13, 2008 at 12:32 PM, Marty Alchin <[EMAIL PROTECTED]> wrote:
>
> On Fri, Jun 13, 2008 at 1:23 PM, Alex Koshelev <[EMAIL PROTECTED]> wrote:
>> There is existing multi-lingual aggregator http://djangosearch.com/
>
> I didn't realize djangosearch broke articles down by language,
> comple
On Fri, Jun 13, 2008 at 12:36 PM, Marty Alchin <[EMAIL PROTECTED]> wrote:
>
> On Fri, Jun 13, 2008 at 1:23 PM, Tom Tobin <[EMAIL PROTECTED]> wrote:
>> Ugh, time. I have a bad habit of assuming I have more of that
>> resource available than I ultimately do. :)
On Thu, Jun 19, 2008 at 11:39 AM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
> I've published an experimental Git clone of Django's SVN repository
> (created with git-svn). If you're a Git user and want to use this
> repository, be my guest. Please still upload patches to Trac for
> review, but
On Thu, Jun 19, 2008 at 4:27 PM, Marc Fargas <[EMAIL PROTECTED]> wrote:
> El jue, 19-06-2008 a las 14:03 -0700, Michael Elsdörfer escribió:
>> FWIW (I'm currently playing around with all three of them), bazaar
>> appears to support pushing into svn as well.
>
> Yes, with bzr-svn. Didn't play too mu
Thanks to some happy signal magic, I've come up with a
"DateTimeZoneField" that takes a "time_zone" argument; time_zone can
be a tzinfo instance or a field lookup to a zoneinfo string (e.g.,
"America/Chicago"). The field can then consume any sort of datetime
object, and will always spit back a ti
On Wed, Jun 25, 2008 at 11:17 AM, Ramiro Morales <[EMAIL PROTECTED]> wrote:
>
> On Wed, Jun 25, 2008 at 1:12 PM, Tom Tobin <[EMAIL PROTECTED]> wrote:
>
>>
>> I propose that the PostgresSQL backends start acting like the other
>> backends regarding time
I don't spend much time in #django on Freenode, but for a moment, I'd
like you to check the logs of that channel.
http://oebfare.com/logger/django/
Specifically, I'd like you to note interactions with user "Magus-"
(with trailing dash).
I think we have a representation problem on our hands. If
On Wed, Jun 25, 2008 at 4:48 PM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
> Calling someone else out publically is a move of last resort, and one
> that should be avoided at all costs.
::sigh:: I'm sorry; after this and another spat on the ChiPy list, I
think I'm not very good at the whole t
On Thu, Jun 26, 2008 at 9:05 AM, Mike Scott <[EMAIL PROTECTED]> wrote:
> I understand there are some complexities involved, but essentially its
> just creating a uniform javascript API to use - not unlike the may we
> have a uniform database api.
That's a gross understatement. :-)
The various J
On Fri, Jun 27, 2008 at 11:36 AM, rskm1 <[EMAIL PROTECTED]> wrote:
>
>> Help me out here: how can I make it more obvious? You missed that;
>> others often do to. Can you share with me some insights on how you
>> missed it?
>
> I'll chime in. Basic rule of thumb for GUIs:
> * If it's going to fail
On Fri, Jun 27, 2008 at 5:55 AM, Antti Haapala <[EMAIL PROTECTED]> wrote:
>
>
> On 25 kesä, 19:12, "Tom Tobin" <[EMAIL PROTECTED]> wrote:
>
>> All PostgresSQL supports in terms of *storage* is
>> a fixedtimezoneoffset, not the actual zoneinfo name;
On Mon, Jun 30, 2008 at 4:29 AM, Antti Haapala <[EMAIL PROTECTED]> wrote:
>
> 2008/6/27 Tom Tobin <[EMAIL PROTECTED]>:
>>
>> Well, it stores the *offset*, which is virtually useless in real-world
>> applications.
>
> I haven't tested on 8.3, but
On Tue, Jul 1, 2008 at 4:25 AM, Kenneth Gonsalves
<[EMAIL PROTECTED]> wrote:
>
> why should he be more polite? He follows the policy of 'teaching to
> fish' rather than spoonfeeding. I have several times got flamed by
> him for getting impatient and giving the answer. I would say that he
> is the s
On Wed, Jul 2, 2008 at 7:17 AM, Arien <[EMAIL PROTECTED]> wrote:
>
> Can we get back to our regular program now and move personal problems
> to private communication, please? Thank you.
Insofar as referencing particular individuals goes, I agree. I should
have raised any issues with particular c
On Thu, Jul 3, 2008 at 9:26 AM, phillc <[EMAIL PROTECTED]> wrote:
>
> random person: "i need help"
> magus: gives technical answer
> random person: does understand python
> magus: points to docs
> random person: you are rude
1) Let's stop referring to specific people, mmkay? I made that
mistake,
On Thu, Jul 3, 2008 at 9:26 AM, Jannis Leidel <[EMAIL PROTECTED]> wrote:
>> Even if these sorts of features have a patch and are "Ready for checkin,"
>> that does not mean they get a 1.0 milestone. They still take core
>> developer time to review and commit, time that also needs to be
>> focused
On Sat, Jul 5, 2008 at 3:10 AM, Keir <[EMAIL PROTECTED]> wrote:
> I have recently been working on my first project in Django and have
> encountered a small problem when using ModelForm. Here's my ModelForm
> class
You're on the wrong list. ^_^ For support questions, you want django-users.
The
1 - 100 of 180 matches
Mail list logo
