On Sun, Feb 8, 2009 at 1:56 AM, Russell Keith-Magee
wrote:
> So - some options:
>
> 1) Leave things as-is. Annotated columns always appear in the result
> set. This is inconsistent with extra(), and means you can't use
> annotated queries in __in clauses.
>
> 2) Modify things slightly - annotate()
On Sun, Feb 8, 2009 at 10:28 AM, Ben Gerdemann wrote:
>
> On Feb 7, 12:35 pm, Alex Gaynor wrote:
> > On Sat, Feb 7, 2009 at 8:27 AM, Ben Gerdemann wrote:
> >
> > A couple things, first the patch still has a pair of TODO comments, so
> > either those comments are no longer applicable, or what th
On Wed, Feb 4, 2009 at 1:41 PM, RahulDave wrote:
>
> The Plot thickens a bit with whats happening in the case of the eaten
> up QueryCanceled Error. Basically,
> somewhere in the list protocol, the QueryCancelledError thrown by
> psycopg2 gets eaten up!
>
> [snip details]
> I'm delving into the i
On Sun, Jan 25, 2009 at 12:51 PM, PB wrote:
>
> Hi,
>
> I've been experimenting with model inheritance and have become pretty
> dissatisfied with the way it is implemented in Django.
[snip gripes]
This general reaction has been registered before. You might want to search
the user's list for l
On Sat, Jan 24, 2009 at 1:16 PM, koenb wrote:
>
> In ticket #10113 I signalled two problems. The first was almost
> immediately fixed by Russel (thanks!). For the second problem I added
> a specific testcase that was giving me wrong results. It concerns an
> annotated query with ordering on a for
On Fri, Jan 23, 2009 at 3:14 AM, Julien Phalip wrote:
> Thank you Karen for this detailed answer. Your reasoning regarding
> this ticket does make a lot of sense. I totally agree with you that
> tests are highly important and that this ticket is lacking useful
> information for whoever is not fam
On Fri, Jan 23, 2009 at 12:38 AM, Julien Phalip wrote:
>
> Hi,
>
> I just wanted to draw your attention to what appears to be a bug in
> Django: the 'tell()' proxy is missing from the Windows-specific
> implementation of TemporaryFile. This causes Django to crash when
> manipulating the uploaded
On Tue, Jan 20, 2009 at 10:08 PM, Harryanto Ie wrote:
> [snip]
File
> "c:\python25\Lib\site-packages\django\db\backends\sqlite3\base.py",
> line 167, in execute
> return Database.Cursor.execute(self, query, params)
>
> OperationalError: no such table: django_session
>
> i've put django.contri
On Fri, Jan 16, 2009 at 9:43 AM, Alex Gaynor wrote:
> PgSQL is indeed PostgreSQL. Yes, I do still get the failures pre-fast
> tests, I guess I'd never run those tests. I would like to say that when I
> went back to test that the tests were unbearably slow, so that makes me
> super happy about t
On Fri, Jan 16, 2009 at 9:13 AM, Ivan Sagalaev
wrote:
>
> I've found it. My fault, as usually :-). But an interesting corner case
> too.
>
> We're using mysql_replicated db backend that basically has two
> connections. The first ("master") is active by default and is used when
> loading fixtures.
On Fri, Jan 16, 2009 at 9:15 AM, Alex Gaynor wrote:
> I'm seeing some failures exclusively under PgSQL:
> http://dpaste.com/109831/ . I'm not sure what's causing them, but it's
> just the admin views tests, no other ones.
>
(PgSQL is PostgreSQL ... ?)
I see those too, on my PostgreSQL test mac
On Fri, Jan 16, 2009 at 7:47 AM, Ivan Sagalaev
wrote:
>
> Karen Tracey wrote:
> > For the most part this change should be invisible, except for the speed
> > improvement when running tests. However, if you have tests that need to
> > actually test the effects of transa
r9756 contains the changes to make django.test.TestCase use transaction
rollback (where available) instead of database flush/reload for resetting
the database. This can provide a nice speedup when running large test
suites -- the Django/sqlite buildbot went from around 20 minutes for the
test run
On Thu, Jan 15, 2009 at 1:12 PM, Eric Holscher wrote:
> You both are indeed correct. I certainly think that the current patch can
> go in today as presented. The Ellington test suite is passing with a 10x
> speedup. We can get it to 40x speedup if we change out doctests that load
> fixtures into u
On Wed, Jan 14, 2009 at 5:35 PM, Russell Keith-Magee wrote:
>
> On Thu, Jan 15, 2009 at 5:40 AM, Eric Holscher
> wrote:
> > I think that if there is a plan to ever include fixtures into doctests,
> then
> > we should put transaction management into them. We should also decide on
> a
> > syntax (
FYI -- since this Windows Python 2.5.x problem doesn't appear to be
something we'll be able to figure out before I turn into a pumpkin and have
to go to sleep, and I'm not sure what you are thinking about with regard to
committing the code -- the rest of the test suite runs normally on the
Windows
On Wed, Jan 14, 2009 at 10:20 PM, Russell Keith-Magee <
freakboy3...@gmail.com> wrote:
> On Thu, Jan 15, 2009 at 12:01 PM, Karen Tracey wrote:
> > On Wed, Jan 14, 2009 at 9:46 PM, Russell Keith-Magee
> > wrote:
> >> Next suggestion is to check if the converters tha
On Wed, Jan 14, 2009 at 9:46 PM, Russell Keith-Magee wrote:
> On Thu, Jan 15, 2009 at 11:15 AM, Karen Tracey wrote:
> > Yeah, that's the direction I was heading in. Only I didn't have to go so
> > far as trying against trunk. Even with the aggregate code,
> >
On Wed, Jan 14, 2009 at 8:53 PM, Russell Keith-Magee wrote:
>
> On Thu, Jan 15, 2009 at 10:26 AM, Karen Tracey wrote:
> > On Wed, Jan 14, 2009 at 7:22 PM, Russell Keith-Magee
> > wrote:
> >>
> >> Help, yes. Illuminating, No. :-(
> >>
> &
On Wed, Jan 14, 2009 at 7:22 PM, Russell Keith-Magee wrote:
> Help, yes. Illuminating, No. :-(
>
> To fill you in on what I'm looking for - every aggregate value coming
> back from the database passes through resolve_aggregates() in
> django.db.models.query.py (line 212). This passes to convert_v
On Wed, Jan 14, 2009 at 6:26 PM, Russell Keith-Magee wrote:
>
> On Thu, Jan 15, 2009 at 8:16 AM, Ian Kelly wrote:
> >
> > On Wed, Jan 14, 2009 at 4:03 PM, Russell Keith-Magee
> > wrote:
> >>
> >> On Thu, Jan 15, 2009 at 4:21 AM, Ian Kelly
> wrote:
> >>>
> >>> On Wed, Jan 14, 2009 at 12:20 PM,
On Wed, Jan 14, 2009 at 5:58 PM, Russell Keith-Magee wrote:
>
> On Thu, Jan 15, 2009 at 2:54 AM, Karen Tracey wrote:
> > On Tue, Jan 13, 2009 at 10:52 PM, Russell Keith-Magee
> > wrote:
> >>
> >> If you have any objections or problem reports, speak no
On Wed, Jan 14, 2009 at 4:33 PM, Ramiro Morales wrote:
> Karen,
>
> On Wed, Jan 14, 2009 at 3:54 PM, Karen Tracey wrote:
> >
> > I'm getting some errors running the aggregation and aggregation_regress
> > tests on Windows boxes running Python 2.5.2 and 2.5.
On Wed, Jan 14, 2009 at 12:51 PM, Sebastian Bauer wrote:
>
> Hi
>
> I think it's a bug, but maybe im wrong:
>
>
> print Categories.objects.count()
> >>0
> new_obj = Categories.objects.create(name="test")
> instance_1 = Categories.objects.get(pk=new_obj.pk)
> instance_2 = Categories.objects.get(p
On Tue, Jan 13, 2009 at 10:52 PM, Russell Keith-Magee <
freakboy3...@gmail.com> wrote:
>
> If you have any objections or problem reports, speak now or live with
> the consequences :-)
>
I'm getting some errors running the aggregation and aggregation_regress
tests on Windows boxes running Python 2
Just to clarify -- the failure I hit in the Django test suite after
re-ordering rolled back test cases to run first is not one where a test
assumes another runs before it (rather the reverse) or one that can be
triggered currently by just running that single test in isolation. If you
run just file
On Tue, Jan 13, 2009 at 12:06 PM, Jacob Kaplan-Moss <
jacob.kaplanm...@gmail.com> wrote:
>
> On Tue, Jan 13, 2009 at 10:00 AM, Karen Tracey wrote:
> > OK, so that sounds like one vote for leaving things as they are for
> > doctests, that is with no rolled-back transactio
On Tue, Jan 13, 2009 at 9:05 AM, Russell Keith-Magee wrote:
>
> > So, the latest patch on #8183 (8138alternate-nodoctestxaction.diff) does
> not
> > enclose doctest runs in a rolled-back transaction. Thus the effects of
> > doctests can still bleed over into subsequent tests. This doesn't
> act
One of the item on the list for 1.1 is "Run Django test cases inside a
transaction". The ticket for this is #8138:
http://code.djangoproject.com/ticket/8138
and previous list discussion can be found here:
http://groups.google.com/group/django-developers/browse_thread/thread/49aa551ad41fb919/3d7
On Mon, Jan 12, 2009 at 8:25 AM, James Bennett wrote:
>
> On Mon, Jan 12, 2009 at 6:53 AM, mrts wrote:
> > What if we try to be nice to ourselves and get #8138 and something in
> > the lines of
> http://oebfare.com/blog/2008/mar/25/faster-django-test-suite/
> > into trunk ASAP
>
> What if we pay
On Wed, Jan 7, 2009 at 9:46 AM, Russell Keith-Magee
wrote:
> I've just pushed some updates to Github that should hopefully fix the
> problems that have been reported (ORA-00933, ORA-00923 and ORA-00972
> and the decimal/datetime conversion problems). If someone with access
> to an Oracle test mach
On Mon, Jan 5, 2009 at 6:11 PM, Malcolm Tredinnick wrote:
>
> On Mon, 2009-01-05 at 23:11 +0900, Russell Keith-Magee wrote:
> > Hi all,
> >
> > SQL Aggregations (ticket #3566) are almost ready for trunk!
> >
> > This is a call for final testing.
>
> By the way, I'm pretty sure I accidentally brok
On Mon, Jan 5, 2009 at 10:51 AM, alex.gay...@gmail.com <
alex.gay...@gmail.com> wrote:
>
> Karen,
>
> Can you try changing line 230 of django.db.models.sql.query from:
>row = row[:aggregate_start] + tuple(
> to
>row = tuple(row[:aggregate_start]) + tuple(
>
On Mon, Jan 5, 2009 at 9:11 AM, Russell Keith-Magee
wrote:
> [snip]
> In particular, I need feedback on the following:
>
> - Oracle support. I don't have any access to Oracle for testing
> purposes, so I'm relying on the community (esp the Oracle backend
> maintainers) to help me out here.
>
I d
On Mon, Jan 5, 2009 at 6:49 AM, Filipe wrote:
>
> Hi,
>
> Sorry to be posting this kind of issue to this list (not sure it's the
> right place).
>
> I've been trying to submit a ticket to trac, over at
> djangoproject.com.
> My new ticket was initially being flagged as spam, so I registered for
>
Please repost your question on django-users. This list is for discussion of
development of Django itself, not usage questions.
Karen
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post
Please take follow-ups to this question to django-users. This list is
really not for usage questions.
Karen
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send emai
On Mon, Dec 15, 2008 at 5:51 AM, Alex Rades wrote:
>
> Hi,
> my understanding about custom managers is that if you want to define a
> custom manager, you also HAVE to remember to define the "objects"
> manager first, otherwise some parts of django (eg. admin) will not
> work.
>
What does "will n
On Wed, Dec 10, 2008 at 12:59 PM, AcidTonic <[EMAIL PROTECTED]> wrote:
>
> There is no anger here sir. I'm a rather sarcastic individual and I
> guess there was a good dose there.
>
> I just cant for the life of me understand why this excellent framework
> completely missed the point there.
>
> Is
Please ask on the django-users mailing list. This one is for development of
Django itself, not usage questions.
Karen
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group,
On Tue, Nov 18, 2008 at 4:14 PM, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:
>
> To generate the files just cd django; django-admin.py compilemessages -
> l LANG_CODE
>
> Another language ticket is: http://code.djangoproject.com/ticket/9597
>
OK, thanks, I applied the two translation updates t
On Sun, Nov 16, 2008 at 7:46 PM, James Bennett <[EMAIL PROTECTED]>wrote:
>
> On Sun, Nov 16, 2008 at 5:42 PM, Jacob Kaplan-Moss
> <[EMAIL PROTECTED]> wrote:
> > I'll defer to James to make the final call, but I'd prefer to do this
> > and release 1.0.2 on Monday or Tuesday with a note that it's ba
On Sun, Nov 16, 2008 at 6:07 PM, Justin Bronn <[EMAIL PROTECTED]> wrote:
>
> > Thanks, I eventually figured this out on my own -- it was the
> > problem. Fixed in r9473 and r9474.
> >
>
> I wish I had known about MANIFEST.in sooner, is there any way we re-
> tag and re-release 1.0.1 with the miss
On Sun, Nov 16, 2008 at 2:42 PM, Frank Liu <[EMAIL PROTECTED]> wrote:
>
> @#$%!.will this composite primary key feature be included in
> Django 2.0? Or will this be ever included? Let me explain my
> frustration a bit.
>
>
[snipped]
Did I miss something? Your note makes it sound like the cor
As this is a usage question, please post it on django-users. This list is
for discussion of developing Django, not using it.
Karen
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post t
On Sat, Nov 15, 2008 at 5:57 AM, Ivan Mincik <[EMAIL PROTECTED]> wrote:
>
> Hi,
> I have a problem when adding record by Django Admin and I am not sure where
> I have to look for it. Is this some problem in Django Admin or it can be
> solved by some
> configuration in model ?
If you are unsure w
Please post your question to djang-users. This list is for discussion of
developing Django itself, not usage questions.
Karen
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to thi
Please post your question to djang-users. This list is for discussion of
developing Django itself, not usage questions.
Karen
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to thi
On Tue, Nov 4, 2008 at 8:08 AM, H. de Vries <[EMAIL PROTECTED]> wrote:
>
> Hey all,
>
> I pretty new to developing for Django itself and for that reason I
> have question.
>
> 4 days ago I submitted a bug and I wrote a patch and tests for it. I
> noticed through the timeline that there are people
On Sun, Nov 2, 2008 at 6:54 AM, Tai Lee <[EMAIL PROTECTED]> wrote:
> I've put this ticket back to "accepted" as per your comment that the
> bug should be fixed. As you say, the DDN and confused comments were
> not intended to raise a red flag, and should have been taken to a
> separate ticket. The
On Sat, Nov 1, 2008 at 9:14 PM, Tai Lee <[EMAIL PROTECTED]> wrote:
>
> #8898 and #9482 are both simple bug fixes with patches that remain
> unreviewed. #9214 is a simple backwards compatible enhancement with
> patch.
>
> I'm reluctant to mark them "ready for checkin" as I am the reporter,
> but it
On Fri, Oct 31, 2008 at 6:38 AM, mrts <[EMAIL PROTECTED]> wrote:
>
> There has been much reluctancy in letting triagers tag and prioritize
> 1.0.1 milestone tickets. Now that 1.0.1 is really close, can we
> perhaps discuss what are the things that really should be fixed before
> it is released?
>
On Thu, Oct 23, 2008 at 5:49 AM, Calvin Spealman <[EMAIL PROTECTED]>wrote:
> ...
> But I do notice I wasn't clear enough in my actual intent. I need to patch
> the descriptor, so that I can disable this in my tests *only*, no where
> else. Unfortunately, this kind of patching is currently not allo
On Tue, Oct 7, 2008 at 7:17 AM, Malcolm Tredinnick <[EMAIL PROTECTED]
> wrote:
> I'd probably say that we bite the bullet and use 1.1 except then we
> should do what one of the Spanish Marc's has suggested in a ticket
> somewhere (could I be any less specific on the details, do you think?)
> and m
This mailing list is for discussion of developing Django itself, not usage
problems with Django. Your question belongs on django-users, not here.
Please repost it there (and as a style note, fewer exclamation marks may
garner it more serious attention).
Karen
--~--~-~--~~
On Fri, Sep 26, 2008 at 1:09 PM, zvoase <[EMAIL PROTECTED]> wrote:
>
> Just wondering if I could ask how compatible Django is with CPython
> 2.6. I know that it should work fine anyway, but I thought it a good
> idea just to check. Has anyone looked into this?
>
>
There are no known problems with
On Wed, Sep 24, 2008 at 4:49 PM, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:
>
> I'll go upload a fix now, the current behavior doesn't make sense,
> since the SQL spec says that NULL != NULL, does anyone know if there
> are any dbs for which this isn't true?
>
There are a couple of oddball DB
On Mon, Sep 22, 2008 at 11:39 AM, HenrikV <[EMAIL PROTECTED]>wrote:
>
> I hope your reply was helpful to others. I asked a question because I
> am not as knowledgeable about Django internals as you obviously are,
> and this is this is to my knowledge the place to ask.
> I make no assumptions about
On Wed, Sep 10, 2008 at 4:06 PM, Karen Tracey <[EMAIL PROTECTED]> wrote:
> We have this problem that's been seen in the wild by a couple-three people
> now:
>
> http://code.djangoproject.com/ticket/8110
>
> It apparently results from the AdminLogNode's render()
On Fri, Sep 19, 2008 at 10:51 AM, smcoll <[EMAIL PROTECTED]> wrote:
>
> Take this model as an example:
>
> -
> from django.db import models
> from django.contrib.auth.models import User
>
> class Contact(models.Model):
>user = models.ForeignKey(User, unique=True, null=True, blank=T
On Fri, Sep 19, 2008 at 9:42 AM, John <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I was wondering if nested inlines' will be supported in the admin in
> any post 1.0 release. I remember seeing it mentioned in the road map
> for the 1.0 release but I guess it was dropped due to time issues.
>
>
The topi
On Tue, Sep 16, 2008 at 5:23 PM, Steve Holden <[EMAIL PROTECTED]> wrote:
>
> Fredrik Lundh wrote:
> > Karen Tracey wrote:
> >
> >
> >> We've had at least three people run into a problem (#9090) after
> >> installing 1.0 over an old level.
We've had at least three people run into a problem (#9090) after installing
1.0 over an old level. Now, we do document that before installing you
should remove any old level. But I find the results when you don't rather
odd. It's not just old files renamed/deleted in the new level that wind up
be
We have this problem that's been seen in the wild by a couple-three people
now:
http://code.djangoproject.com/ticket/8110
It apparently results from the AdminLogNode's render() function getting
called multiple times, since the patch that protects against that by not
modifying self.user in render
On Wed, Sep 10, 2008 at 12:12 PM, Eric Holscher <[EMAIL PROTECTED]>wrote:
> Yea, I totally agree with this.
>
> I wrote a blog post about how to use setuptools and distutils to distribute
> your django apps. There is no reason to reinvent the wheel here, especially
> after what Mark talked about a
On Wed, Sep 10, 2008 at 10:38 AM, Brian Rosner <[EMAIL PROTECTED]> wrote:
> On Wed, Sep 10, 2008 at 8:13 AM, shadfc <[EMAIL PROTECTED]> wrote:
> > The problem is that FieldFiles get saved to the storage backend even
> > on a save(commit=False), and (according to a more knowledgeable SeanL-
> > on
On Wed, Sep 10, 2008 at 12:43 AM, Adrian Holovaty <[EMAIL PROTECTED]>wrote:
>
> Just a quick note: I've redirected
> http://www.djangoproject.com/documentation/ and everything below that
> URL tree to the new docs subdomain, http://docs.djangoproject.com/.
> Rather than spending the time to redire
On Fri, Sep 5, 2008 at 2:34 AM, David Cramer <[EMAIL PROTECTED]> wrote:
>
> Does the error message pretty easily let you figure out what's wrong?
>
A problem I've seen with infinite recursion is that while it may manifest
itself pretty clearly on one platform, the same root problem may show
entir
On Thu, Sep 4, 2008 at 9:12 AM, Gerard Petersen <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> I found out that with "manage.py sql myapp" the generated sql for a date
> field still ends up with "NOT NULL" as a suffix. Removing this suffix from
> the mysql command makes Django properly handle the mod
On Sat, Aug 30, 2008 at 11:33 PM, Rodolfo <[EMAIL PROTECTED]> wrote:
>
> I tried creating a new ticket on Trac, but it didn't like me, and I
> didn't like the idea of creating "just another login account" just for
> that.
>
You don't have to create a login account. If you just fill in something
On Sat, Aug 30, 2008 at 12:56 AM, M N Islam Shihan <[EMAIL PROTECTED]>wrote:
> Yes, it has been made optional with this syntax class CharField(*
> max_length=None*[, ***options*])
> This is true for all other model fields as well that were expecting
> max_length parameter.
>
I don't believe this
On Wed, Aug 27, 2008 at 12:43 PM, David Spreen <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I am a member of the Debian Python Modules Team and have been heavily
> involved in the transition to Django 1.0 in Debian (1.0~beta2 is about
> to be uploaded to experimental).
>
> As you might know, 1.0 will
On Wed, Aug 27, 2008 at 9:56 AM, Jacob Kaplan-Moss <
[EMAIL PROTECTED]> wrote:
>
> On Wed, Aug 27, 2008 at 8:41 AM, [EMAIL PROTECTED]
> <[EMAIL PROTECTED]> wrote:
> > "We're not in complete and total feature freeze. "
> >
> > I assume you mean the opposite of this.
>
> Sigh.
>
> Proofread, Jacob,
On Wed, Aug 27, 2008 at 9:08 AM, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:
>
> That branch is totally dead, there is some external work attempting to
> add multi-db support, I don't know the status of it though.
>
I believe that project is here: http://hg.woe-beti.de/multi-db/
Karen
--~--~-
Please ask usage questions on django-users, not here. This list is for
discussion of developing Django itself, not using it.
Karen
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post t
On Tue, Aug 26, 2008 at 4:55 PM, Jacob Kaplan-Moss <
[EMAIL PROTECTED]> wrote:
> So I think we need to do something along the lines of what's in
> #7524... it's far, far from perfect, but it's probably the only way to
> go to avoid a lot of frustration.
>
>
So should #7524 get moved back to a 1.0
On Sun, Aug 24, 2008 at 10:24 AM, Jacob Kaplan-Moss <
[EMAIL PROTECTED]> wrote:
>
> Quick note: Malcolm and I are in Portland in the only place in the
> city sans wifi. We've talked about this and the other exc swallowing
> issue and I have some thoughts. Please hold until I'm in a more
> civilize
On Mon, Aug 25, 2008 at 7:57 PM, Michael Hrivnak <[EMAIL PROTECTED]>wrote:
> That is neither a direct nor indirect replacement for model-level
> validation.
> Many applications receive input from sources other than forms. Validation
> at
> the form and model level are both valuable, but for diffe
On Mon, Aug 25, 2008 at 12:12 PM, Malcolm Tredinnick <
[EMAIL PROTECTED]> wrote:
> On Mon, 2008-08-25 at 08:47 -0700, Matt Boersma wrote:
> > I can wrap the execute() and executemany() calls in oracle\base.py in
> > a try/except that re-raises this specific error as an IntegrityError:
> >
> >
On Sun, Aug 24, 2008 at 2:26 AM, James Bennett <[EMAIL PROTECTED]>wrote:
>
> I stand by what I said in the dev channel yesterday: this is one
> instance of a more general issue (there are lots of places where --
> because we need to import or check something -- we can end up
> "swallowing" excepti
On Fri, Aug 22, 2008 at 9:34 AM, Russell Keith-Magee <[EMAIL PROTECTED]
> wrote:
> I suspect that re-ordering the imports at the top of mysql.base will
> fix this problem. Open a ticket and I'll put this on my todo list.
>
>
Done, #8485.
Thanks,
Karen
--~--~-~--~~~---
I noticed a thread on the user's list (
http://groups.google.com/group/django-users/browse_thread/thread/c0d55dfea1f2a43c#)
reporting that the result of trying to trying to run with the database
backend set to 'mysql' but no MySQLdb installed is now the simple message:
Error: No module named mysql
On Fri, Jul 25, 2008 at 1:27 AM, Jeremiah <[EMAIL PROTECTED]> wrote:
>
> With a little research today I discovered that it is possible to do a
> case insensitive match on a binary column by using COLLATE.
Yes, specifying COLLATE is what's needed here. In fact specifying the
BINARY attribute on
On Tue, Jul 22, 2008 at 2:13 AM, David Cramer <[EMAIL PROTECTED]> wrote:
>
> I was using utf8_general. I'm swapping to utf8_bin to attempt to fix
> it, but binary encodings cause problems as well with unique indexes or
> something similar (can't remember what my test case was from Curse).
>
> On J
On Mon, Jul 21, 2008 at 12:57 PM, Chris Hasenpflug <
[EMAIL PROTECTED]> wrote:
>
> I've opened #7867 for regressiontests.model_inheritance_regress
> failures against MySQL. I've marked it 1.0 beta for now, but
> depending on requirements of the test suite passing before tagging a
> release. it ma
On Mon, Jul 21, 2008 at 2:28 PM, Ramiro Morales <[EMAIL PROTECTED]> wrote:
>
> On Mon, Jul 21, 2008 at 3:17 PM, Karen Tracey <[EMAIL PROTECTED]> wrote:
> > I just tried installing current svn (via setup.py) on a machine where I
> had
> > previously installed 0.
I just tried installing current svn (via setup.py) on a machine where I had
previously installed 0.96.2. Install works but I notice that there are
files (contrib/admin/urls.py, contrib/admin/utils.py are two I knew to check
for) that used to exist in the old version but have been deleted in curren
On Mon, Jul 21, 2008 at 11:18 AM, Jacob Kaplan-Moss <
[EMAIL PROTECTED]> wrote:
> If there's anything that absolutely *MUST* be in 1.0 alpha, speak up
> now. Please keep in mind that the alpha release is intended only for
> the "must-have" features, which are now all in. This means that the
> only
Now that newforms-admin is merged, tickets tagged with nfa-fixed ought to be
closed as fixed, right? Does that need to be done manually or will
something automagic be run that does it? (It doesn't appear that there are
all that many out there, so it could be done manually if that's easiest.)
Kar
On Sat, Jul 19, 2008 at 8:45 AM, Jacob Kaplan-Moss <
[EMAIL PROTECTED]> wrote:
>
> On Sat, Jul 19, 2008 at 3:08 AM, James Bennett <[EMAIL PROTECTED]>
> wrote:
> > Adding 'admin.autodiscover()' to the project's root URLConf fixes
> > this; normally I'd just check in a quick change to the tutorial t
A beta 2 release of Python 2.6 was released yesterday or so, and they are on
a schedule to have a final release around the same time Django 1.0 is
scheduled. Actually, slightly after, but who knows with scheduling code
releases which one will actually reach 'final' first.
Right now, http://www.dj
On Mon, Jul 14, 2008 at 12:57 AM, Russell Keith-Magee <
[EMAIL PROTECTED]> wrote:
>
> On Mon, Jul 14, 2008 at 12:25 PM, Karen Tracey <[EMAIL PROTECTED]> wrote:
> >
> > Speaking of 2.3 compatibility, the tests don't run for me on 2.3 (which I
> > jus
On Sun, Jul 13, 2008 at 11:50 PM, Russell Keith-Magee <
[EMAIL PROTECTED]> wrote:
>
> On Mon, Jul 14, 2008 at 10:55 AM, Matt Wilson <[EMAIL PROTECTED]> wrote:
> >
> > I'm trying to figure out if I'm running the tests incorrectly, or if
> > there are really are failed tests in the revision.
>
> I'm
On Tue, Jul 8, 2008 at 10:53 AM, Russell Keith-Magee <[EMAIL PROTECTED]>
wrote:
> To the best of my knowledge, there shouldn't be anything else required
> to run the tests, other than python in your system path.
>
> One possible cause is the __init__.py files; there are 3 required in
> total - adm
On Mon, Jul 7, 2008 at 10:00 AM, Russell Keith-Magee <[EMAIL PROTECTED]>
wrote:
>
> Hi all,
>
> I've been looking at #6017 and #5943 of late. These two tickets have
> been around for a while; one of the biggest reasons that they have
> taken so long to address is that they cover an area of Django
On Wed, Jul 2, 2008 at 10:47 AM, Steve Holden <[EMAIL PROTECTED]> wrote:
> Rob van der Linde wrote:
> > I see there is now a link to the registration page when you go to file a
> > ticket, but why not put it on page where the login/settings links are
> > (just underneath the search box). This is w
I have a suggestion to help ensure that Django 1.0 gives a good first
impression to new users: line up some install testers for the gamut of
supported platforms, and have these testers verify (prior to release) that
the documented installation procedure works correctly on their platform.
Motivati
On Thu, Jun 19, 2008 at 9:57 AM, Michael Glassford <[EMAIL PROTECTED]>
wrote:
>
> I'm still trying to run the Django unit tests for the first time. I've
> worked through most of the errors--all of them so far proved to be
> caused by the MySQL/InnoDB ordering problem when deserializing objects
> t
On Thu, Jun 19, 2008 at 9:21 AM, Russell Keith-Magee <[EMAIL PROTECTED]>
wrote:
>
> On Thu, Jun 19, 2008 at 9:04 PM, Peter Melvyn <[EMAIL PROTECTED]>
> wrote:
> >
> > On 6/19/08, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> >
> >> (2) provide a way to manually disable and re-enable integrity
On Mon, Jun 16, 2008 at 11:49 AM, Joseph Kocherhans <[EMAIL PROTECTED]>
wrote:
>
> On Mon, Jun 16, 2008 at 10:40 AM, Karen Tracey <[EMAIL PROTECTED]> wrote:
> >
> > Cool. One question I have regarding dates is: is there a target date for
> > merging newforms-
301 - 400 of 463 matches
Mail list logo
