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
On Thu, Jun 26, 2008 at 3:47 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> It appears that dumpdata includes things that syncdb will create
> automatically, and then loaddata attempts to insert them again,
> violating the unique constraint.
You've just found #7052. Changeset [7615]
Yes, this should be asked on the users group.
As you've discovered the syncdb command may also populate some tables
with initial data - which isn't desirable in your situation.
I think that for a beginner, the connotation of "sync" could be a
little confusing and it probably takes making
Thanks Jacob and Jeremy for these suggestions ;)
On Jun 26, 2:30 am, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 25, 2008 at 11:24 AM, Jacob Kaplan-Moss<[EMAIL PROTECTED]> wrote:
>
> ...
>
> > I don't know that it'll make it in before 1.0 since we're focusing on
> > stuff on the
On Wed, Jun 25, 2008 at 10:40 PM, Gary Wilson Jr. <[EMAIL PROTECTED]> wrote:
>
> Russell Keith-Magee wrote:
>> My preferred solution here would be to provide a way for test cases to
>> substitute a top level URL pattern object for the duration of the
>> test. For example:
>
> Swapping the root
Hi folks --
I'm setting up sprints leading up to the 1.0 release, and I need some
volunteers to host a couple of 'em.
So far, here's what we've got by way of sprinting:
July 10-12: EuroPython
July 18: Sausalito, CA
August 1: ?
August 8: Lawrence, KS
August 15: ?
August 22: ?
So we need a spot
I'd like to offer one more perspective. Magus- (Collin) was one of the
first folks to help me in the IRC channel. And, initially, I did think
to myself "well, that's a little smug."
Then, I tried helping people the way he does for a mere fraction of
the time he does. Answering the same 5
On Wed, Jun 25, 2008 at 4:21 PM, Tom Tobin <[EMAIL PROTECTED]> wrote:
> Specifically, I'd like you to note interactions with user "Magus-"
> (with trailing dash).
Four points:
1. His name is Collin.
2. He's one of the channel ops.
3. As someone who hangs out in the channel pretty much 24/7 I
"Has to go". Heh. While I certainly agree he doesn't exactly come
across as nice, I wouldn't call him abusive. He's terse and a bit
impatient but generally friendly.
He's an Op and I've never seen him ban people senselessly. I log in on
weekends and often see him in the room walking people
Ha, Magus is great. He's helped so many people, it's mind boggling.
Rather than ban him, I'd say he should get donations.
The problem on every IRC channel or email list is that often people
don't actually listen to the advice given to them, or read the
documentation pointed out to them. Magus
It's too bad you had a negative experience with someone in the IRC channel.
However, aside from how abrasive he can be from time to time, he's usually
the only one to answer questions in there. I'd guess he does a majority of
the help in there (no offense to the others that do a good deal of
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.
Hi,
this could be question for -users, but I have a feeling it would
eventually end up here.
I'm questioning if my usage of dumpdata and loaddata are "correct".
Here's my use case:
1. Server A:
- python manage.py dumpdata > dump.json
2. Server B:
- createdb
- (copy
These are tickets that don't have an owner, are DDN, and are in the 1.0
alpha milestone.
http://code.djangoproject.com/ticket/6406 - discusses hooks for form saving
http://code.djangoproject.com/ticket/7268 - The only thing left here is
changing script names in django to a consistent naming
On Wed, Jun 25, 2008 at 11:24 AM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
...
> I don't know that it'll make it in before 1.0 since we're focusing on
> stuff on the roadmap, but if you're willing to be patient this'll
> almost certainly go in after. And possibly before if I find the time,
>
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 zones: they should start ignoring them
>>
Hey Julien --
#1105 looks quite nice (though it looks like your patch was generated
weirdly... at least, the paths are strange -- no real problem,
though).
I don't know that it'll make it in before 1.0 since we're focusing on
stuff on the roadmap, but if you're willing to be patient this'll
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 zones: they should start ignoring them
> completely (i.e., use a plain TIMESTAMP [WITHOUT TIME ZONE], and stop
> using SET TIME
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
On Wed, Jun 25, 2008 at 9:42 AM, Joseph Kocherhans <[EMAIL PROTECTED]>
wrote:
> More discussion is needed, but it seems like we're at a point where we
> should be discussing a list of possible options. I forget what all of
> them are, but maybe someone can write them up and post them here?
Yes.
On Wed, Jun 25, 2008 at 5:03 AM, Russell Keith-Magee
<[EMAIL PROTECTED]> wrote:
>
> On Wed, Jun 25, 2008 at 1:18 PM, Jeff Anderson <[EMAIL PROTECTED]> wrote:
>> Here is another list:
>>
>> #6003 (from nfa-blocker)
>> #6450
>> #4148
>
> Done. #6003 needs a little more discussion; I'd like to hear
Okay, I've submitted #7537 with three patches. I manually split out
sub-changes from a previous version, so some things may be broken, but
hopefully in simple ways.
The first patch at least could go in almost as-is (one little design-
decision FIXME) and would be immediately helpful. The second
Russell Keith-Magee wrote:
> On Wed, Jun 25, 2008 at 1:17 AM, Marc Fargas <[EMAIL PROTECTED]> wrote:
>> I can think of two options right now:
>>* manage.py test should not run django.contrib.* tests, those are
>> supposed to have been run in runtests.py and working fine (that's the
>>
[EMAIL PROTECTED] wrote:
That one looks like it should have been #4148:
http://code.djangoproject.com/ticket/4148
On Jun 25, 1:25 am, Collin Grady <[EMAIL PROTECTED]> wrote:
Jeff Anderson said the following:
#4118
Do you have the wrong # here? That ticket is closed:
Ken Arnold wrote:
> I wanted to get any feedback on this change before submitting a
> ticket, but if people think it's a good idea, I can clean up the patch
> and make a ticket.
Anything that gets REST projects and nfa off the ad-hoc dispatchers
sounds like a good idea to me. Along with a
On Wed, Jun 25, 2008 at 1:17 AM, Marc Fargas <[EMAIL PROTECTED]> wrote:
>
> But oviously, contrib apps should (to not say must) test their views to
> be sure that code released works! Hence, there should be a way for
> contrib apps to have an urls.py and test it.
Agreed. This is something we
Hello,
In django.utils.synch is located RWLock. When you try enter the same
lock twice (probably in some subprocedure) you can't. I think that
correct semantics is that you had acquired this lock in this thread so
you should get it again with no problem. Other (but not preferred)
variant is
That one looks like it should have been #4148:
http://code.djangoproject.com/ticket/4148
On Jun 25, 1:25 am, Collin Grady <[EMAIL PROTECTED]> wrote:
> Jeff Anderson said the following:
>
> > #4118
>
> Do you have the wrong # here? That ticket is closed: duplicate :)
>
> --
> Collin Grady
>
> It
Jeff Anderson said the following:
> #4118
Do you have the wrong # here? That ticket is closed: duplicate :)
--
Collin Grady
It was a brave man that ate the first oyster.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
29 matches
Mail list logo
