On 9/27/07, Derek Anderson <[EMAIL PROTECTED]> wrote:
>
> ok, yes, introspection we all agree has to be used for validation (1)
> and signature creation (2). we're all on the same page as that being a
> good thing.
Wait up a moment - (2) is an entirely optional part of my proposal. My
proposal p
ok, yes, introspection we all agree has to be used for validation (1)
and signature creation (2). we're all on the same page as that being a
good thing.
but what SoC2006, my subsequent work and what i think most people here
are talking about when we say "evolution through introspection" is ab
On 9/27/07, Derek Anderson <[EMAIL PROTECTED]> wrote:
>
> russell, i've re-read your linked email (from 8/4/07), and i'm still
> totally lost as to what you're proposing. i'm reading of application
> and verification of an SQL-abstraction syntax:
>
> mutations = [
>AddColumn('
russell, i've re-read your linked email (from 8/4/07), and i'm still
totally lost as to what you're proposing. i'm reading of application
and verification of an SQL-abstraction syntax:
mutations = [
AddColumn('Author', 'dateofbirth', models.DateField,
On 9/27/07, Derek Anderson <[EMAIL PROTECTED]> wrote:
>
> Russell Keith-Magee wrote:
> > I'm not sure where you got the idea that automatic introspection is
> > the issue - the proposal I put forward included automatic
> > introspection. The issue has always been the aka syntax, and the
> > conseq
Russell Keith-Magee wrote:
> I'm not sure where you got the idea that automatic introspection is
> the issue - the proposal I put forward included automatic
> introspection. The issue has always been the aka syntax, and the
> consequences of that syntax on the overall design.
because several of t
On 9/27/07, SmileyChris <[EMAIL PROTECTED]> wrote:
>
> On Sep 27, 6:18 am, "Yuri Baburov" <[EMAIL PROTECTED]> wrote:
> I'm actually waiting for some code to be put up to
> http://code.google.com/p/django-evolution/ - Russell (I'm pretty sure
> it was him... we discussed it at the end of the sprin
On 9/26/07, Xan <[EMAIL PROTECTED]> wrote:
>
> >
> > Expect something like this in a few months. The problem for now is
> > that we have no official place to put the monetary proceeds from
> > something like that.
> >
> > Adrian
>
> It's a pain that you couldn't have sooner!
All good things take
On 9/27/07, Derek Anderson <[EMAIL PROTECTED]> wrote:
>
> ok, for the official status:
>
> as mentioned earlier, yuri and i are joining forces on
> introspection-driven schema evolution. and since automatic
> introspection is so controversial (and obviously a poison pill for
> acceptance into dja
On 9/27/07, David Reynolds <[EMAIL PROTECTED]> wrote:
\> > Would anyone else find this useful?
> >
> > I'm quite happy to take a shot at it, if anyone else will find it of
> > any use.
>
> Just to clarify:
>
> http://code.djangoproject.com/ticket/5610
Sounds like a good idea to me. It would dove
Hi Jose,
I know of one preexisting CAS authentication backend which is
available on Google Code [1]. For some background on that project you
might also check out the author's blog posts [2] [3].
/John/
[1] http://code.google.com/p/django-cas/
[2] http://blog.case.edu/bmb12/2006/12/cas_for_djan
On 26 Sep 2007, at 4:07 pm, David Reynolds wrote:
>
> Hi,
>
> Would anyone else find this useful?
>
> I'm quite happy to take a shot at it, if anyone else will find it of
> any use.
Just to clarify:
http://code.djangoproject.com/ticket/5610
Anyone any thoughts?
Thanks,
David
--
David Reyno
ok, for the official status:
as mentioned earlier, yuri and i are joining forces on
introspection-driven schema evolution. and since automatic
introspection is so controversial (and obviously a poison pill for
acceptance into django-proper), we've rewriting it as an external library.
the pro
SmileyChris wrote:
> I like Derek's take on model comparison using introspection, but
> really think that it should be based on a migration system. I know
> several Django developers agree with me on this (including Russell).
i see them as two distinct, non-exclusive tasks, with automatic
intros
> I'm actually waiting for some code to be put up to
> http://code.google.com/p/django-evolution/ - Russell (I'm pretty sure
> it was him... we discussed it at the end of the sprint) has someone
> who has been working on some code and I really want to see it before I
> do any more work.
You better
> I like Derek's take on model comparison using introspection, but
> really think that it should be based on a migration system. I know
> several Django developers agree with me on this (including Russell).
Rails has migrations because it has introspection already built-in.
I don't understand why
On Sep 27, 6:18 am, "Yuri Baburov" <[EMAIL PROTECTED]> wrote:
> There were also attempts to do schema-evolution in other way, but no
> other project released more than limited alpha versions. I rechecked
> it today.
I'm guessing this could refer to my code.
I'm actually waiting for some code to
I see the new ticket in Trac:
http://code.djangoproject.com/ticket/5604
Thanks very much for creating the ticket, and submitting the patch.
Jeffrey
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django develope
Hi,
Waiting for Derek, as he's official person responsible for
implementing schema-evolution functionality in django (if we can use
"responsible" with open source) and maintainer of schema-evolution
branch.
What I can say now, is that since django now allows custom commands,
we will implement it
why it only happened in firefox ?
a strange question .
在 07-9-26,Reflejo<[EMAIL PROTECTED]> 写道:
> I can't understand how it is connected with django.
>
>
> BTW; don't do this:
> I mean: action equals "dot".
>
>
> --
> Martín Conte Mac Donell
>
>
> On 9/25/07, 张沈鹏(电子科大08年本科应届) <[EMAIL PROTECTED]>
On 9/26/07, David Cramer <[EMAIL PROTECTED]> wrote:
> The only way this can be done as of current is by saying
> "MYmodel(id=1)" which is a hack. This technically shouldn't be done as
> you're instantiating an object without a dataset. What happens when
> the shared memory select related patch wer
Hi,
I just want to know what is the status of the Schema Evolution.
Reading trac docs and browse code repository I see that you have
several implementations.
What is the most stable implementation?
What is the implementation you probably merge in svn?
What are the big future steps we (django us
Hi,
Would anyone else find this useful?
I'm quite happy to take a shot at it, if anyone else will find it of
any use.
Thanks,
David
--
David Reynolds
[EMAIL PROTECTED]
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Googl
Hi,
Back again on the django missing i18n feature in template (see
thread :
http://groups.google.com/group/django-developers/browse_thread/thread/c88b582fa4764aaa/665af6639a099ec8
)
Is there any impovements/thoughts on this ?
Maybe I should post a trac entry just not to forget this (?)
--
AD
Howdy folks --
I think given the questions in this thread I should try to clarify the
state of Django and threading:
So as far as I know, Django should be threadsafe. However, I'm also an
idiot, so "as far as I know" isn't very far at all, actually.
See, if I've learned one thing from all the t
On Sep 26, 8:07 am, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote:
> On 9/25/07, Xan <[EMAIL PROTECTED]> wrote:
>
> > I'm only interested if there is a "official shop" ofdjango: t-shirts,
> > coffee cups, etc.
> > If not, an official channel in Cafepress.com, Spreadshirt.net or
> > Shopify.com wo
Matt Boersma wrote:
> In reviewing bug #5579 (see http://code.djangoproject.com/ticket/5579),
> I discovered I never receive the confirmation email from Trac at
> http://www.djangoproject.com/accounts/register/. I've tried four
> times since Sunday, using two email addresses in different domains.
I can't understand how it is connected with django.
BTW; don't do this:
I mean: action equals "dot".
--
Martín Conte Mac Donell
On 9/25/07, 张沈鹏(电子科大08年本科应届) <[EMAIL PROTECTED]> wrote:
>
> Opps , I test so many version , but none of them can do the right job.
> Which one is I checkout previou
If you ended up adding a store, it sure would be nice if you could use
Satchmo ;)
Seriously though, if you are considering building a store vs. using a
3rd party arrangement of some sort, let me know.
-Chris
--~--~-~--~~~---~--~~
You received this message becaus
On 9/26/07, Andrew Durdin <[EMAIL PROTECTED]> wrote:
>
> On 9/26/07, Wolfram Kriesing <[EMAIL PROTECTED]> wrote:
> >
> > I ran into the problem while doing this:
> >
> > >>> from django.utils.translation import gettext_lazy as _
> > >>> s = _("my string")
> > >>> s += _("my second string")
> > Tra
On 9/26/07, paulh <[EMAIL PROTECTED]> wrote:
>
> I tried this in the user's list, but it didn't get any interest.
For future reference - if you don't get an answer in django-users,
asking in django-developers is _not_ your next step. Django-developers
is for discussing the development of Django i
On 9/26/07, Wolfram Kriesing <[EMAIL PROTECTED]> wrote:
>
> I ran into the problem while doing this:
>
> >>> from django.utils.translation import gettext_lazy as _
> >>> s = _("my string")
> >>> s += _("my second string")
> Traceback (most recent call last):
> File "", line 1, in ?
> TypeError:
On Sep 25, 10:58 pm, Graham Dumpleton <[EMAIL PROTECTED]>
wrote:
> ensure there own code is multithread safe, but now again someone is
> saying that Django itself is not multithread safe. :-(
Well, I was just repeating the what I heard from the developers. Not
so long ago a proposal was made th
I ran into the problem while doing this:
>>> from django.utils.translation import gettext_lazy as _
>>> s = _("my string")
>>> s += _("my second string")
Traceback (most recent call last):
File "", line 1, in ?
TypeError: unsupported operand type(s) for +=: '__proxy__' and '__proxy__'
>>>
the
On Sep 26, 7:01 pm, Derek Anderson <[EMAIL PROTECTED]> wrote:
> well, that was sarcasm with the "lazy" comment...come on, i love python.
> why else would i be here? :)
>
> but it is faked. two python threads can't run concurrently on a two
> processor machine. unless, as you pointed out, you'
> Nicola Larosa wrote:
>> Right. What *is* is scary is how much people cling to the horrible hack
>> that preemptive multithreading is.
Derek Anderson wrote:
> you mean to say cooperative multithreading, right?
>
> if so, heck yeah. dear lord in heaven yeah.
Erm... what?!? Cooperative MT *is*
The only way this can be done as of current is by saying
"MYmodel(id=1)" which is a hack. This technically shouldn't be done as
you're instantiating an object without a dataset. What happens when
the shared memory select related patch were to go in? You'd now have
an instance of a model thats comp
I tried this in the user's list, but it didn't get any interest.
Use of the django default forms routines form_for_model,
form_for_instance on a model that has a foreign key that references a
table with a large number (many thousands) of rows results in two
problems.
One, you get an appreciable (
well, that was sarcasm with the "lazy" comment...come on, i love python.
why else would i be here? :)
but it is faked. two python threads can't run concurrently on a two
processor machine. unless, as you pointed out, you're calling a few
hand-picked C operations (mostly i/o). they're lik
Derek Anderson wrote:
> but then again, python itself isn't multi-threaded. (all threading is
> faked - google "global interpreter lock". lazy s.o.b. python devs)
given that a stock CPython interpreter releases the lock in a few
hundred places, primarily around potentially long-running or blo
you mean to say cooperative multithreading, right?
if so, heck yeah. dear lord in heaven yeah.
Nicola Larosa wrote:
> Derek Anderson wrote:
>> but then again, python itself isn't multi-threaded. (all threading is
>> faked - google "global interpreter lock". lazy s.o.b. python devs) so
>> a
Derek Anderson wrote:
> but then again, python itself isn't multi-threaded. (all threading is
> faked - google "global interpreter lock". lazy s.o.b. python devs) so
> all your really hairy "c=c+1" type issues are already nixed.
>
> so not so scary.
Right. What *is* is scary is how much peop
42 matches
Mail list logo