On 7/19/07, Mario Gonzalez <[EMAIL PROTECTED]> wrote:
> Dears hackers, I want to ask a question, for you maybe it will be
> just foolish but, I've seen the open tickets, I'm trying to write some
> patch for some of them but my help it's not enough :-( and they are a
> lot.
>
> Are you going to w
Hey all,
Sorry for the double-post, but I've written up some examples /
documentation:
http://kered.org/blog/wp-content/uploads/2007/07/django_schema_evolution_documentation.html
Also, I've ported the changes to SVN. I would like to solicit testers,
for potential inclusion in django-proper.
If you have the time, Mario, you can always create a "django 1.0
release theories" website :)
Then all you have to do is come up with some interesting plot twists,
some celebrity blogs, and a "find the missing feature" game, and
before you know it, 1.0 will be here!
-rob
On Jul 19, 3:49 pm, "Ja
Hi Mario --
This has been discussed (to death) a number of times. Please search
the archives.
[Short answer: 1.0 will be released when we can guarantee API
stability. We're not there yet.]
Jacob
--~--~-~--~~~---~--~~
You received this message because you are sub
Dears hackers, I want to ask a question, for you maybe it will be
just foolish but, I've seen the open tickets, I'm trying to write some
patch for some of them but my help it's not enough :-( and they are a
lot.
Are you going to wait until all those tickets will be closed? is
there a date limit
Hey all,
I've ported my schema evolution work from my SoC project last summer to
Django v0.96. To use it, download the patch below, and run the following:
$ cd //site-packages/django/
$ patch -p1 < ~//django_schema_evolution-v096patch.txt
It should output the following:
patching file core/m
On Jul 19, 2:10 am, Michael Radziej <[EMAIL PROTECTED]> wrote:
> Was git-svn easy to set up? I'm having issues with its ugly sibling
> "git-svnimport" ...
On a Mac with MacPorts, very easy:
$ sudo port install git-core +svn
Anywhere else I'm not sure but the above suggests that git-svn is a
http://code.djangoproject.com/ticket/4117
I'm leaning towards the solution outlined in the second post of this
thread instead of the patch on #4117.
http://groups.google.com/group/django-developers/browse_thread/thread/e55be1c11893c069
How have others using newforms solved this?
Thanks
...
ja
Hi Malcolm,
thanks for your feedback!
I'm trying to anwer both mails in one (hope it works out).
I'm in the mid of porting my stuff to the current trunk, and first there
were of course a lot of failing doctests. After I changed the
__proxy__.__str__, I was able to see the problems
('' in a trac
On Wed, 2007-07-18 at 18:36 +0200, Michael Radziej wrote:
> Hi,
>
> after the unicode merge, the repr() of a lazy translation string is
> ''
>
> This gets in my way of testing, since it used to be just the resulting
> string. I'm helping myself with a
>
> class __proxy__(Promise):
> #...
On Thu, 2007-07-19 at 11:16 +0200, Michael Radziej wrote:
[...]
> Malcolm, is there a reason for this, perhaps python2.3 related?
No, it's partly a built-in safety feature (something like ugettext_lazy
isn't designed to be converted directly to a string. It's unsafe) and
partly a matter of avoidi
On Wed, Jul 18, Jacob Kaplan-Moss wrote:
> On 7/18/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
> > after the unicode merge, the repr() of a lazy translation string is
> > ''
>
> You just need to do ``unicode(laxystring)`` to get the original
> string. I'm sure Malcolm has a good reason for t
On Wed, Jul 18, Rob Hudson wrote:
> After going to a git presentation by Randal Schwartz and watching the
> video by Linus on git, I decided to play with it some for a patch I'm
> testing in Django. I got git and git-svn installed on my Mac, pulled
> down the Django source and started a new bran
13 matches
Mail list logo
