Hello everyone,
I have a problem when run createsuperuser.py command in python 3.4. How can
I solve it definitely?
Look the code:
https://gist.github.com/lucassimon/7837dce442e3a4a090ce4d155b4a2035
--
You received this message because you are subscribed to the Google Groups
"Django developer
Excellent - thank you!
On Friday, October 10, 2014 4:00:33 PM UTC+2, Karen Tracey wrote:
>
> There is a ticket open on this issue:
>
> https://code.djangoproject.com/ticket/19508
>
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to
Django sites respond to broken URLs with a blank error 400 page. E.g. here
on Disqus:
http://disqus.com/%C3A4
This error is raised inside the WSGI application and currently there's no
way to avoid it or to use some custom error 400 page. We do have a nasty
patch that's grossly inefficient and
n if you disagree with
> some aspects of the specification of MERGE, wouldn't it be valuable to
> implement it properly? Since I'm not the most knowledgeable person on this
> topic, where can I learn more about the reasons for this choice?"
A fair point.
--
Simon Riggs
ulary you're using isn't acceptable in this forum,
> 3) Personal attacks based on prejudice will not be tolerated.
Well, for 1) any comments are most welcome. I didn't see any evidence
of the other two.
All opinions welcome.
--
Simon Riggs http://www.2ndQuadrant.com
we would
like to solicit open feedback about how such a feature might look and
what aspects make it more/less likely to be adopted by Django.
Detailed feedback on ORM related issues is welcome.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Tra
gers fire
}
else
{
perform INSERT
AFTER INSERT triggers fire
}
INSTEAD OF triggers would fire on views only, so would be shown in the
above instead of the before triggers
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
),
("check_quantity", Check(quantity_sold__gte = 0)),
("check_price", Check(car_price__between = [0, 1])),
)
So a list of constraint name and a Check() pairs. I think the idea was that
Check() could be ANDd or ORd together a bit like the Q() object.
It worked with Post
If this has already been discussed/rejected/accepted, sorry, I did a search
and found nothing.
There are several snippets and a number of methods to enable "universal"
decorations of views in Django, but none of them feels really natural.
Also, being able to keep this class of code in one place
Contrib redirects is still a handy little app, but it's dependency on
contrib.sites is often unnecessary and a little annoying.
Would anyone else be keen to see the dependency removed, gracefully? If so
I'll spin up the code.
--
You received this message because you are subscribed to the Googl
Yes but management commands should be irrelevant for django-secure
Am 15.09.13 17:52, schrieb Aymeric Augustin:
> On 15 sept. 2013, at 16:40, Simon K. wrote:
>
>> But in production the entry point is the wsgi.py file, isn't it?
> It's the main entry point in product
development you would usually use manage.py to invoke your devserver.
But in production the entry point is the wsgi.py file, isn't it? At least
this seems to be a more reliable approach for me than the pure
differentiation based on the state of the debug setting.
Simon
--
You received this
lyn, it's easier to use
> for the simple cases and it's accessible from outside the form, from a view
> for example.
>
> The current patch only documents the dict construct for `ValidationError`
> since `Form.add_errors` was a private method in my original patch; sh
Lack of clean control over field-specific form errors is an issue that has
been raised and discussed many times over the years, but still the solution
seems pretty inadequate. We're even directing people hack around with
_errors and making excuses for it in the documentation.
https://docs.django
On Monday, 12 August 2013 17:23:40 UTC+10, Aymeric Augustin wrote:
>
> It would be interesting to describe what actual problems these libraries
> encountered. Were they caused by actual deprecations or by changes in
> private APIs?
>
One example would be simplejson, why not leave a stub there
It's great all the housekeeping we've been doing lately, and I'm sure we
all agree nice to have clean, tidy code; but I wonder if we've been a
little too unforgiving at the expense of easy compatibility with important
third party apps?
Celery, sorl-thumbnail, mptt, registration, shorturls, comp
only need to obfuscate it enough to defeat the
> compression scheme, not an adversarial attacker.
>
>
> On Wed, Aug 7, 2013 at 3:23 AM, Simon Blanchard wrote:
>
>> I think they nibble at it. They look at the compressed length - the
>> shorter the compressed length closer t
On 13 June 2013 07:41, Simon Meers wrote:
> On 13 June 2013 03:33, wrote:
>
>> I think that the usability of ForeignKeyRawIdWidget could be vastly
>> improved if the representation part of the widget (the object name, in
>> bold) were to be updated when a new object g
7 August 2013 16:56, simonb wrote:
>
>> How about requiring that if csrfmiddlewaretoken is set, no matter what
>> http method (GET, POST...), it is correct otherwise 403 response.
>>
>> Simon
>>
>> --
>> You received this message because you are subscribe
which will defeat any attempt to
utilise an index to supply the ordering. i.e. it results in a
sequential scan and should be avoided.
I'd suggest an explicit option to change the ordering ASC | DESC,
which is matched by a SQL Standard feature.
--
Simon Riggs http://www.2ndQuad
e may be some interesting alternatives there. Also, can additional
parameters be added to javascript functions and be safely ignored by
unsuspecting old code? Perhaps the signature compatibility is a non-issue.
I think we should retain the RawIdWidgets and raw_id_fields for both
backwards-compatibility and al
ound
great.
BTW- there are two Simon's here. I'm "simon29" from the original ticket,
not "Simon" from this thread.
On Saturday, 11 May 2013 03:00:04 UTC+10, Simon wrote:
>
> Hi,
>
> When I started using Python a couple of months ago, a quick Google for
Apologies Daniele, I hadn't realised that had actually posted before I
finished editing. I've now posted the final verison
On Friday, May 10, 2013 5:57:43 PM UTC+1, Daniele Procida wrote:
>
> On Fri, May 10, 2013, Simon > wrote:
>
> >Of course, once the ticket has
ers do?
I'm unlikely to use Django moving forward. There are a number of reasons
and I'd be lying if I said this was the biggest but it was a factor in my
decision.
Anyway, I wanted to take a few minutes and share the impressions I've had
to date - perhaps this way, others
Hi.
I'm a newcomer to both Python and Django and just wanted to share my
experience trying to solve a couple of problems.
When I started coding in Python a month ago, Django was sufficiently common
in Google searches that it was my first port of call. I've found quite a
few features which I lo
Most likely, yes, so it looks like a bug fix now not an optimization.
> Also, multicolumn NOT IN lookups aren't
> supported on all databases (SQLite at least), so for that case NOT
> EXISTS semantics is going to happen anyways.
Yes, I think that's the clincher.
--
Simon Rig
hat weirdness that makes it hard to
optimize for, or at least, not-yet-optimized for in PostgreSQL.
In most cases it is the NOT EXISTS behaviour that people find natural
and normal anyway and that is the best mechanism to use.
> However, the query constuction to move the condition in
Also, did you see psycopg2.extras.DateTimeRange?
On Monday, December 31, 2012 8:56:12 PM UTC+11, mpaolini wrote:
>
> Hi all,
>
> sorry for the noise, forget my previous mail as it was pointing to the
> wrong commit,
> here's the good one:
>
>
> https://github.com/mpaolini/django/commit/b754abd
Marco, this is great.
I wonder if it would be possible to add range fields without modifying
django?
On Monday, December 31, 2012 8:56:12 PM UTC+11, mpaolini wrote:
>
> Hi all,
>
> sorry for the noise, forget my previous mail as it was pointing to the
> wrong commit,
> here's the good one:
See https://code.djangoproject.com/ticket/15273
On 23 November 2012 23:30, Ludwig Kraatz wrote:
> Hi,
>
> is there a specific reason why the RedirectView does not have a
> "view_name" attribute and out-of-the-box supporting to reverse it?
>
> if self.url:
> url = self.url
> elif self.v
It's a shame we couldn't skip straight to Python 3.3 and take
advantage of PEP414...
On 22 August 2012 07:32, Adrian Holovaty wrote:
> On Tue, Aug 21, 2012 at 5:46 AM, Aymeric Augustin
> wrote:
>> In my opinion, option (2) is a logical move at this point. However I
>> believe it deserves a publi
unicode_compatible?
(Though, @-syntax class decorators are only available from 2.6+, but
I'm guessing we won't be able to drop 2.5 support at the same time as
picking up 3. I guess we could just tidy up when we do.)
Simon
--
You received this message because you are subscribed to the Go
Monday 20th August 0900-2359 AEST at PyCon Australia 2012 (Hobart) [1]
The Interaction Consortium [2] have kindly offered to provide pizza
and beer (presumably only for those physically present ;)
Join us via the #django-sprint IRC channel on Freenode; see [3] for
more information.
[1] http://20
intended approach and its flexibility and
benefits. There are still a few details to iron out in evolving the ideal
implementation, but this at least demonstrates the gist of it. Does anyone
else think this is worth exploring?
Simon
[1] https://code.djangoproject.com/ticket/17924
[2] *
https://gro
ovements that can be
made to make field-tweaking easier and more elegant, as proposed in
[1] which Keryn pointed out in [2]. It would probably be better to
continue this conversation in those tickets.
Simon
[1] https://code.djangoproject.com/ticket/17924
[2] https://code.djangoproject.com/ticket/1806
also submit a
doc revision in the other case.
Simon
<https://github.com/charettes/django/compare/class-based-generic-edit-views-messages.diff>
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on th
I've been working on a similar project which takes the django-dynamo
project a bit further.
It's undocumented ATM but you can find the code at:
https://github.com/charettes/django-mutant
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To
ions through django-updates and monitor Trac.
Simon
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email t
Hi Yasar!
Are you sure you're at the latest trunk revision? (16911)
I'm not getting any failures with this revision and the test_sqlite
settings?
http://dpaste.com/623028/
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this dis
It might be worth it to look at this existing effort to document _meta:
http://readthedocs.org/projects/django-model-_meta-reference/.
Simon
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web vi
http://lmgtfy.com/?q=vcvarsall.bat
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-developers/-/v6EuZV0jI6AJ.
To post to this group, send email to django-devel
On Wed, Aug 10, 2011 at 3:08 PM, Anssi Kääriäinen
wrote:
> On 08/10/2011 03:18 PM, Simon Riggs wrote:
>
> That adds additional SELECT statements, which then extends a lock
> window between the check statement and the changes. It works, but in
> doing so it changes an optimis
ock check
failed and we can handle that. This keeps the locking optimistic and
doesn't add any additional SQL statements.
e.g.
UPDATE foo
SET col = newvalue, optimistic_lock_field = optimistic_lock_field + 1
WHERE pkcol = p_key
AND optimistic_lock_field = p_version
DELETE FROM foo
WHERE pk
How is that supposed to interact with the `cleaning` mechanism of the field?
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-developers/-/BNMXjILUK7gJ.
To post
gt; because constraint checks are *never* checked during testing. The small slew
> of bugs I found is a demonstration of that, to me.
No, sorry, nested transaction commands aren't supported.
> Anyhow, thank you once again Simon for shedding light on this for me.
No problem. Thank
On Sun, Jul 10, 2011 at 3:27 PM, Jim Dalton wrote:
> On Jul 10, 2011, at 3:13 AM, Simon Riggs wrote:
>
>> Maintaining the property of deferrable constraints seems important
>> here, so changing the deferrability of constraints, or overriding it
>> using the SET CONSTRAIN
e the ROLLBACK at *end* of
test. This will fire any outstanding checks. That way all constraint
checks will occur in the same place they would during a commit, yet we
can maintain the situation that the test ends with a rollback.
--
Simon Riggs http://www.2ndQuadrant.com/
Postgr
se statement directly? That way *any* legal
CASE statement can be used, without inventing new ORM syntax each
time.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
You received this message because you are subscribed to
On Mar 15, 9:46 am, Russell Keith-Magee
wrote:
> On Fri, Mar 11, 2011 at 1:14 PM, Simon Litchfield wrote:
> > Who votes we should come up with a django-blessed 'official' default
> > project layout / directory structure?
>
> Sure -- no disagreement that it wo
Who votes we should come up with a django-blessed 'official' default project
layout / directory structure?
Might sound like a triviality, but sometimes it's the little things.
1. Newcomers -- startproject throws 9/10 into confusion and results in a messy
first few projects.
2. Gurus -- eac
Hi Carl,
> FWIW, django-model-utils [1] includes an InheritanceManager that
> implements polymorphic queries in a single query via select_related.
Ah, there goes my theory that I thought of it first :) And of course
introspection of subclasses via the reverse OneToOne descriptors is
perfect.
--
eous multi-table
inheritance models in a single query (see example in [1]). I haven't
looked deeply enough into django_polymorphic to see if it includes
such optimisations. I'm sure we could further tweak the internals to
make things more efficient and developer-friendly in this regar
This addon[1] has not been updated since the doc were and doesn't work
anymore.
You can try this updated version[2] I use which works fine.
[1] https://addons.mozilla.org/en-US/firefox/addon/django-docs-search/
[2] https://gist.github.com/813029
--
You received this message because you are sub
s. If so i'll file a feature request whith a patch
and tests. I might need some help on doc however.
Simon
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
an expected behavior.
I'm also wondering if the issue shouldn't be tackled at the
forms.fields.Field API level instead.
What about defaulting Field.__init__ localize kwarg to settings.USE_L10N?
Simon
[1] http://code.djangoproject.com/ticket/14101
--
You received this message because yo
This means that, for now, there is
> no good answer for you (that I'm aware of). Whatever hack or
> workaround you are able to come up with is what you're gonna get.
> Sorry.
BTW the ticket for this is #897 [1] and there is a suggested
workaround (explicit declaration o
ry Django project I work on; this way the browser maintains separate
cookies for each one, so I don't have to keep logging in/out, etc. I'd be
very disappointed to see this functionality disappear.
Simon
--
You received this message because you are subscribed to the Google Groups
&
Honza's #5833 is nifty. It's a pity it missed the cut last year for
1.1. It's been kicking around for 3 years, and there seems to be
plenty of similar tickets that it'd address too.
Any chance for 1.3? Is it just the lack of tests/docs or are there
design concerns?
--
You received this message b
On 30 October 2010 07:50, Andrew Godwin wrote:
>
> It's working fine for me on my freshly-updated 1.2.X branch - did you make
> sure the caches were clear, etc, etc?
>
Yes, and I'd experienced it on several different
servers/projects/client-machines. Yet I've just tested it on a new project
al
On 27 October 2010 19:40, Andrew Godwin wrote:
> On 27/10/10 07:01, Simon Meers wrote:
>
>> Has anyone else found that using prepopulated_fields in admin.ModelAdmin
>> since r14123 produces a javascript error: "d.join is not a function"?
>>
>
> I didn&
Has anyone else found that using prepopulated_fields in admin.ModelAdmin
since r14123 produces a javascript error: "d.join is not a function"?
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-devel
On 27 October 2010 08:15, Simon Litchfield wrote:
> The ModelAdmin's permission hooks are great- has_add_permission,
> has_change_permission, and has_delete_permission.
>
> It would be nice if they were supported by inlines in the same way; ie
> InlineModelAdmin, StackedI
The ModelAdmin's permission hooks are great- has_add_permission,
has_change_permission, and has_delete_permission.
It would be nice if they were supported by inlines in the same way; ie
InlineModelAdmin, StackedInline, TabularInline, GenericStackedInline,
GenericTabularInline.
UI is fairly obviou
On Sep 30, 8:47 pm, Andrew Wilkinson
wrote:
> I have a patch in the bug tracker that fixes this exact problem
> -http://code.djangoproject.com/ticket/11565. The patch is just over a
> year old now so it might not apply that cleanly to the current trunk.
Revised patch here (against r13296) --
htt
Anyone? I know it is a relatively complex patch to review, but it would be a
shame to see such a frequently requested feature/fix miss the 1.3 boat.
On 29 August 2010 08:06, Simon Meers wrote:
> A gentle reminder to anyone who would like to review the recent patch
> uploaded for #3
If everything is under version control, you'll need to detect the server
status somehow. Some options:
- check the absolute path of the settings file on the filesystem if you can
ensure this path is different on the production server
- import socket; and check socket.gethostname()
- check for "runs
crow/django-error-capture-middleware/wiki/Home
Thoughts? I know I'm not the only one who has run into this (Russ?)
Cheers
Simon
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@go
Users regularly get confused when you present them with a raw_id popup
window which shows action checkboxes beside the list of items they are
selecting from -- they try to click the checkboxes, and wonder why the
window isn't closing. IMHO it really doesn't make much sense to be
performing actions
A gentle reminder to anyone who would like to review the recent patch
uploaded for #3400 [1].
I have come across quite a number of people who consider list_filter's
current inability to span relationships (e.g. as search_fields can) to be
one of the more obvious/annoying of Django's limitations an
losed as a duplicate,
since #13165 has a more mature/up-to-date patch. It is just awaiting
resolution of permission issues and the input of a UX expert, together with
#13163 [2]
Simon
[1] http://code.djangoproject.com/ticket/13165
[1] http://code.djangoproject.com/ticket/13163
On 7 August 2010
The patch here [1] fixes this if anyone feels like reviewing. This bug is
preventing me from using trunk on several projects at present, so it would
be great to get the patch checked in. It also fixes a number of other
problems people have been reporting, I believe.
Simon
[1] http
ve is an
extension to the SQL standard.
SQL Standard formulation for this query syntax is new in SQL:2008 where
it is now called OFFSET ... FETCH ... To my knowledge only DB2 and
Postgres support the new standard syntax.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24
Simon --
Slicing result sets is clearly the developer's responsibility IMHO.
Even with hard limits, MySQL still fails miserably in many situations;
hence the proposal to support hinting from the ORM.
Russ --
Firstly, re namespacing. No worries, let's just keep it RDBMS-
specific, ie
> I'll put it on my todo list; if anyone else wants to give it a sanity
> check, I'd appreciate the extra eyeballs.
Looks pretty sane to me, though I wonder if the deserialisation should
raise an exception if the pk is missing and an incomplete set of
natural key fields is provided? Nice work, tha
On Thu, 2010-07-08 at 15:58 -0500, Alex Gaynor wrote:
> On Thu, Jul 8, 2010 at 3:51 PM, Simon Riggs wrote:
> > On Mon, 2010-07-05 at 00:59 -0700, Simon Litchfield wrote:
> >> > If you can come up with answers to these points, I might get
> >> > interested. 1 and
On Mon, 2010-07-05 at 00:59 -0700, Simon Litchfield wrote:
> > If you can come up with answers to these points, I might get
> > interested. 1 and 2 are fairly trivial; I can think of some obvious
> > answers for 3, but 4 is the big problem, and will require some
> ser
H(tablename, headline) AGAINST (+Django -jazz
Python IN BOOLEAN MODE);
Seems to be very MySQL specific...
regards
Henrik
Simon Litchfield Jul 05 12:59AM -0700 ^
> interested. 1 and 2 are fairly trivial; I can think of some obvious
> answers for 3, but 4 is the big problem, and will require
> I would like to know how you're validating your assertion that MySQL
> is the most used backend. It doesn't match my experience or
> observation.
Nobody knows for sure. I'd put my money on it though.
> The fact that this is a MySQL-specific issue is perhaps the biggest
> impediment to my enthus
On Jul 5, 5:08 pm, hinnack wrote:
> Thats interesting.
> Can you explain, how the search keyword made it into the source?
> Entry.objects.filter(headline__search="+Django -jazz Python")
> SELECT ... WHERE MATCH(tablename, headline) AGAINST (+Django -jazz
> Python IN BOOLEAN MODE);
> Seems to be ve
> If you can come up with answers to these points, I might get
> interested. 1 and 2 are fairly trivial; I can think of some obvious
> answers for 3, but 4 is the big problem, and will require some serious
> research and consideration.
Well, I'm glad you like the with_hints() approach. Items 1-3 a
For those of us using MySQL, having large tables, whilst also wanting
queryset goodness --
http://code.djangoproject.com/ticket/11003
It goes a little something like this --
Model.objects.filter(field=value).with_hints('my_index')
All those in favour say I.
Simon
--
You received th
On 22 June 2010 19:59, Massimiliano della Rovere <
massimiliano.dellarov...@gmail.com> wrote:
> Anyway using this method I can't sort columns any more.
> This is why I was suggesting having links created by the framework:
> callable aren't sortable.
>
They can be -- set admin_order_field on the c
On 21 June 2010 17:49, Massimiliano della Rovere
wrote:
> If I understood correctly, these patches are related to the change view of
> the instance, not to che change list view (the page where instances are
> listed).
Correct; I interpreted your request for "the change page of the linked
object"
> EmailField, UrlField, Foreign Key, OneToOneField and ManyToManyField
> clickable in the admin changelist interface of Django 1.3:
> if you click you are redirected to:
> - Foreign Key, OneToOneField and ManyToManyField: the change page of
> the linked object
This is already implemented in the p
, then get a "permission denied" message --
though in the relatively rare cases where a related object is
registered in the same admin site but the user doesn't have permission
to change it.
IMHO the UX improvements in [3] are worth getting on board ASAP.
Simon
[1] http://code.dja
sts.
I am just the messenger in this, carrying goodwill between projects.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Training and Services
--
You received this message because you are subscribed to the Google Groups
"Django developers"
d on Windows). So 8.2 is the minimum sensible version for
next release of Django, though 8.3 should be minimum recommended with
8.4 current stable release as dev target.
Happy to help with any issues arising from that move.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 2
145 tests in 29.500s
Simon
[1]
http://docs.djangoproject.com/en/dev/internals/contributing/#running-the-unit-tests
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegrou
shouldn't
> get an edit link. Given the addition in 1.2 of object-level
> permissions, this means permissions need to be per-object. Have I
> missed something in my hasty patch read?
Correct; no permissions checking is performed at present. In some
places checking would be almost impossibl
On 25 May 2010 07:50, Simon Meers wrote:
>
> I've uploaded some screenshots [1] of the new patch for #13163 [2] and
> #13165 [3] in action, to allow people to see the affect without
> necessarily applying the changes.
>
> These enhancements have *vastly* improved the navi
http://downforeveryoneorjustme.com/djangoproject.com
On 1 June 2010 17:23, Vinay Sajip wrote:
> I've been having trouble accessing www.djangoproject.com recently,
> from here in the UK. Is this a known problem? Is the server down?
>
> Regards,
>
> Vinay Sajip
>
> --
> You received this message b
I was today momentarily caught out by the missing documentation for
formfield_for_manytomany, and found #11882 [1] which has a patch for
this very issue and was marked "Ready for checkin" last year. It's a
shame it missed 1.2 Anyone care to give it a push?
[1] http://code.djangoproject.com/ticket/
I've uploaded some screenshots [1] of the new patch for #13163 [2] and
#13165 [3] in action, to allow people to see the affect without
necessarily applying the changes.
These enhancements have *vastly* improved the navigability of the
admin interface between related objects.
Please have a look an
> I was trying to figure out why I was getting Internal Server Errors
> when attempting to upload a patch on code.djangoproject.com -- I have
> discovered that there is "no space left on the device"!
This seems to be fixed now (thank you webmaster). However it may be
worth noting that the email ad
I was trying to figure out why I was getting Internal Server Errors
when attempting to upload a patch on code.djangoproject.com -- I have
discovered that there is "no space left on the device"!
Now you can't even add a comment to the database:
Traceback (most recent call last):
File "/home/trac
g, is there an 'official' triage team? Or once we've
been working on django for long enough do we promote ourselves to triagers?
I've not been able to find anything in the documentation apart from being
"trusted community members with a proven history of working with th
ul (for which I
had to create hacked copies of the full inline templates).
I know we're in 1.2 bugfix, so feel free to leave this until later.
Otherwise:
- Is this change useful/minor enough to include in 1.2?
- Does anyone know of cases where this behaviour should be disabled (see
ticket
Thanks for looking into this Russ
> Firstly, django-dev isn't "second tier tech support" - if you don't
> get an answer on django-users for a user-space question, that's a
> pity, but it doesn't mean you can or should "escalate" to django-dev.
I realise this; I thought this was the place to discu
imported from other app/module!
#
Python 2.6.4, Django SVN-12401
Is this a bug? The same happens if you try to import, say,
django.contrib.auth.forms.AuthenticationForm and subclass it. Surely
I'm missing something here?
Simon
[1]
http://groups.google.com/grou
rseSingleRelatedObjectDescriptor,
and objects can be accessed via
Student.school.field.related.parent_model.objects.all(), but a shortcut
would be nice.
The auto-generated models could provide ordering by value, a unique
constraint on the field, and a simple __unicode__ method like the examples
above.
Si
1 - 100 of 491 matches
Mail list logo
