I update the http://github.com/weigj/django-multidb/tree , add support
to model binds, like this:
# settings.py
MODEL_BINDS = {
'hello.*':'db1',
'django.contrib.*':'db2',
}
I think this is most easy way bind model to db, and I also think
about connection manage for master-slaver and sha
On Jan 11, 10:28 am, Martin v. Löwis wrote:
> > I'll give it a go, but for someone who doesn't know about running 2to3
> > etc, to make things a but more obvious can you add to your page a
> > quick set of instructions as to what someone needs to do to try this
> > out. Ie., what needs to be do
Hi all,
related to work on #6845 I stumbled across an issue with validate_unique.
Currently it validates all the unique fields that are present on a
form and in cleaned_data. If the instance passed to the form has pk
set, it will exclude the model from the db lookup validating
uniqueness.
Since
> I'll give it a go, but for someone who doesn't know about running 2to3
> etc, to make things a but more obvious can you add to your page a
> quick set of instructions as to what someone needs to do to try this
> out. Ie., what needs to be done after a checkout, does one apply patch
> and then in
On Jan 11, 10:15 am, Martin v. Löwis wrote:
> > Have you by chance tried running it on top of Apache/mod_wsgi (version
> > from subversion which has Python 3.0 support)?
>
> No, only in runserver mode.
I'll give it a go, but for someone who doesn't know about running 2to3
etc, to make things a
> Have you by chance tried running it on top of Apache/mod_wsgi (version
> from subversion which has Python 3.0 support)?
No, only in runserver mode.
Regards,
Martin
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
> Did you by any chance try running the Django test suite(because that's
> probably going to be the best way to spot breakages).
No, I haven't (or only to the degree to find out that runtest.py is
not in 3.0
syntax, as it uses incorrect except clauses). I'm fairly certain
though
that the test sui
On Jan 11, 9:47 am, Martin v. Löwis wrote:
> I have updated my Py3k port of django. As before, it is just the bare
> minimum to get through the tutorial; as the possibly most significant
> change since the previous patch, it now supports psycopg2.
>
> I have updated the Wiki page athttp://wiki.
Martin,
Did you by any chance try running the Django test suite(because that's
probably going to be the best way to spot breakages).
Thanks,
Alex
On Sat, Jan 10, 2009 at 4:47 PM, Martin v. Löwis wrote:
>
> I have updated my Py3k port of django. As before, it is just the bare
> minimum to get t
I have updated my Py3k port of django. As before, it is just the bare
minimum to get through the tutorial; as the possibly most significant
change since the previous patch, it now supports psycopg2.
I have updated the Wiki page at http://wiki.python.org/moin/PortingDjangoTo3k
with the new patch.
On Jan 6, 11:20 am, "Jacob Kaplan-Moss"
wrote:
> I'd like to see this moved into an external app so that we can
> de-couple it from the 1.1 release. If it proves to be popular and
> stable, we could then consider it for 1.2.
I extracted 4604 into an external app[1] some months ago. It's quite
s
11 matches
Mail list logo
