[no subject]

def extra_permissions(permission_classes): """Decorate a CBV method to add specific permissions on the instance.""" def decorator(func): def decorated_func(self, *args, **kwargs): for permission_class in permission_classes: # Check the extra view level pe

Re: Proposal: Add An in-memory data storage backend in Django

e creation of a fork of that old package. >> >> We are talking about this during the sprints at DjangoCon US 2023 in San >> Diego with Josh Thomas and Mariusz Felisiak proposed to us to ask here on >> this list. >> >> What do you think about adding an in-memory

Re: Form builder application

>From my experience with similar projects, managing the data is relatively trivial in effort compared to the the effort required to make the front end useful and error free. Kind Regards, Michael Thomas On Sunday, 14 April 2019 19:56:43 UTC+5:30, Ali A Cetrefli wrote: > > Hi > We want t

Add natural key support for for generic foreign keys fixtures.

As asked by auvipy, this is a thread to discuss the implementation for this ticket. The idea in the proposed implementation was: When a natural key is

Re: Proposal to merge django-csp into contrib

gt;> >>> Would it be OK if someone else were to pick up this ticket and move it >>> forward? >>> >>> Robert Roskam >>> >>> On Sunday, December 6, 2015 at 11:22:20 AM UTC-5, Thomas Grainger wrote: >>>> >>>>

Re: #27485 new New feature Allow ALLOWED_HOSTS to accept an IP-range / wildcard

Thank you all. I will have a look to see if I can do it without patching. Tom On Thursday, November 17, 2016 at 12:42:56 AM UTC, Thomas Turner wrote: > > Hi > > The other day I raise a ticket to do with ALLOWED_HOSTS and it was > suggested that I post on this group before creatin

#27485 new New feature Allow ALLOWED_HOSTS to accept an IP-range / wildcard

Hi The other day I raise a ticket to do with ALLOWED_HOSTS and it was suggested that I post on this group before creating a patch The ticket is https://code.djangoproject.com/ticket/27485 The problem Now that Django 1.10.3 forces ALLOWED_HOSTS on with debug I have a problem. The problem is that

Re: RFC: DEP 7 - dependency policy

There's a fragment in the policy list of the abstract: rough consensus among the community and core team that the chosen dependency I assume that phrase should end with "is needed" -Thomas On Sat, Nov 5, 2016 at 9:20 AM Patryk Zawadzki wrote: > W dniu sobota, 5 listopada

Re: delegating our static file serving

photo = models.ImageField(storage=PrivateMediaStorage()) Regards, Thomas. On Friday, January 1, 2016 at 1:30:05 PM UTC+4, Curtis Maloney wrote: > > On 01/01/16 15:49, Fabio Caritas Barrionuevo da Luz wrote: > > A question: are there any plans to also improve MEDIA files (user > >

Re: Proposal to merge django-csp into contrib

Yeah this makes a lot more sense in SecurityMiddleware On Sunday, 6 December 2015 10:01:54 UTC, Florian Apolloner wrote: > > > > On Sunday, December 6, 2015 at 10:13:46 AM UTC+1, Aymeric Augustin wrote: >> >> I understand that the “just merge django-csp” approach minimizes effort. >> However the

Proposal to merge django-csp into contrib

Now that the django admin supports the Content-Security-Policy header I think merging django-csp into contrib would be a good fix for https://code.djangoproject.com/ticket/15727 It might also be an idea to wait for Mozilla to also respond to the proposal of this merger. See my PR here: https:

Re: REG: get_display_name function in the User model

something that is entirely site-dependent logic. You > don't even need a custom user model - a template tag (or even a > filter) could do this for you if it's a common enough case for you. > regards, Anoop Thomas Mathew +91 999 53 44 675 -- You received this message becau

REG: get_display_name function in the User model

django.contrib.auth.model.User model. Ticket: https://code.djangoproject.com/ticket/24640 Pull Request: https://github.com/django/django/pull/4506 regards, Anoop Thomas Mathew +91 999 53 44 675 -- You received this message because you are subscribed to the Google Groups "Django devel

Re: Two phase cleaning of models/forms

Since `field_order` will be in Django 1.9 the second clean loop is hardly needed in my case. https://github.com/django/django/commit/28986da4ca167ae257abcaf7caea230eca2bcd80 Am 08.04.2015 um 14:20 schrieb Thomas Güttler: Am 26.03.2015 um 15:12 schrieb Marc Tamlyn: In particular it is worth

Re: Two phase cleaning of models/forms

withdraw the proposal. If someone likes to do it: go ahead, and ask me and other for feedback :-) Regards, Thomas Güttler -- Thomas Güttler http://thomas-guettler.de/ -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django i

Re: 1.9 release planning

I think rare LTS releases and frequent (6month) incremental upgrades are a good compromise. Third-party packages should support LTS releases and at least the latest Django version. They may drop support for earlier non-LTS releases. Either you stick with the LTS release or you go with the cutting e

Two phase cleaning of models/forms

ate"') return if state != 'wait_until_due_date': raise ValidationError('If no due date is set, state must be "wait_until_due_date") Open questions: I am unsure if this should be used only for validation, or if it should be possible to alter values, too.

Re: Composite fields

IRC discussion sounds fine with me, but I'd like to be involved. What's the channel? Thomas On 18 March 2015 at 15:47, Asif Saifuddin wrote: > but? IRC discussion? > > On Tuesday, March 17, 2015 at 9:09:49 PM UTC+6, Thomas Stephenson wrote: >> >> Not impatient

Re: Composite fields

Not impatient or anything, but... Bump. On 13 March 2015 at 14:07, Thomas Stephenson wrote: > All the null handling stuff has been removed from the specification and > replaced with slightly more stringent restrictions on `value_to_dict`. > There is an updated version which incl

Re: csrf middleware token from request body

Hi, for me the following snippets work: var testRun = angular.module('testRun', ['ui.bootstrap']); testRun.config(function($httpProvider) { $httpProvider.defaults.xsrfCookieName = 'csrftoken'; $httpProvider.defaults.xsrfHeaderName = 'X-CSRFToken'; }); See: https://github.com/thoreg/test_executo

Re: Composite fields

tps://github.com/django/deps/pull/12> Thomas On 9 March 2015 at 17:43, Anssi Kääriäinen wrote: > On Mon, Mar 9, 2015 at 8:06 AM, Thomas Stephenson > wrote: > >> It doesn't result in good table design and adds > restrictions/complication > >> to the ORM/migratio

Re: Django Admin New Look

+1 Am 11.03.2015 21:20 schrieb "elky" : > Hi everyone, > > I reworked my previous attempt > of stylizing django admin > and now it looks more like original in terms of color scheme. See > attachments. > > For those who want to play with new theme I cre

Re: Composite fields

when the error is discovered. Django should error > out with a message that the composite field definition is invalid. > > Regards, > Michael Manfre > > On Sun, Mar 8, 2015 at 12:29 PM, Thomas Stephenson > wrote: > >> ps. There's a third option which I just thought o

Re: Composite fields

nit__(**kwargs) def deconstruct(self): # etc. The framework could handle this and mandate "If a composite field has `null=True`, then all subfields are forced into the state `null=True` etc.", applying the `__init__` and `deconstruct` stuff itself. Yep -- I like this solution bette

Re: Composite fields

e to keep the initial implementation and API simple). The point is (no pun intended) that I can't really think of a good way to map a python None to the values of a composite field _without_ the extra implicit column. It's not the nicest solution in the world, but it works. Thomas On 8

Re: Composite fields

quot;only one class in an inheritance heirarchy can define subfields" when writing the DEP though, because Ansarri wants the ability for users to extend ForeignKey with their own python behaviour. Thomas On 7 March 2015 at 22:31, Aymeric Augustin < aymeric.augus...@polytechnique.org> w

Re: Composite fields

Whoops -- would be useful to provide a link <https://github.com/django/deps/pull/12> On Saturday, March 7, 2015 at 6:13:19 PM UTC+11, Thomas Stephenson wrote: > > PR created. Unfortunately that's all the work I'm going to do on this over > the weekend, so I'll co

Re: Composite fields

re that way inclined. Thomas On Friday, March 6, 2015 at 9:52:56 PM UTC+11, Thomas Stephenson wrote: > > Y'OK. I'll create DEP 191 for the composite fields which point to model > fields defined on the model (using the syntax you provided above) and DEP > 192 for composi

Re: Composite fields

writing a DEP will be > usefull, and getting an acceptance for the proposal will make > implementation easier. > > - Anssi > > On Friday, March 6, 2015, Thomas Stephenson wrote: > >> I'll reiterate that I mispoke when I said that "subfields wouldn't b

Re: Composite fields

issues than a mailing list thread. What's the current index into the deps? I'm guessing that it's 191. Thomas On 6 March 2015 at 03:13, Markus Holtermann wrote: > While I like your approach, Thomas, I should also note that I'm not an > expert on those parts of Djang

Re: Composite fields

lternately, depending on people's tastes) Model._meta.get_field(composite__subfield) Thomas On Friday, March 6, 2015 at 1:58:26 AM UTC+11, Marc Tamlyn wrote: > > I think `Model._meta` may well always want all the concrete underlying > fields included somehow, especially for migrations

Re: Composite fields

king and I can add point__in easily enough, it's just a matter of adding the relevant lookup transformations to get_lookup_transform. There were some comments surrounding that function which suggest it needs a refactoring, but I don't think it does. Thomas On 5 March 2015 at 22:30, Anssi

Re: Changes to django.db.models.fields.Field API

erent subfields with the same `name` attribute on the model). I've changed that implementation since (to support retrieving subfields via model._meta.get_field), so the change is no longer warranted. PR for the 'value_from_object' change will come later today though. Thanks, Th

Re: Composite fields

ork that is going on with Relations. Thomas On Thursday, March 5, 2015 at 2:47:51 PM UTC+11, Loïc Bistuer wrote: > > Hi Thomas, > > fields/related.py is begging for a refactor of the existing relational > fields, and ideally we'd build composite fields on top of this

Re: Composite fields

oviding extra parameters to it's subfields. Thomas On 5 March 2015 at 14:21, Josh Smeaton wrote: > With regards to the field API - that probably doesn't need an ML > discussion. Open a ticket on Trac, submit a PR, and the people that will > want to see it will review it. I

Re: Composite fields

bout a couple of small changes to the field API I'd like to make to support this proposal) had been languishing for four days without a single response. Thomas On 5 March 2015 at 11:52, Curtis Maloney wrote: > Have you reviewed all the existing works on trying to add composite fields? &g

Re: Composite fields

OK, no need for everyone to shout -- your message is heard loud and clear. I'll go and find something else to work on. On 5 March 2015 at 00:16, Thomas Stephenson wrote: > Considering the past two proposals I've made here, I doubt I'll get more > than an echo chamber effect

Composite fields

Considering the past two proposals I've made here, I doubt I'll get more than an echo chamber effect on this one. For the past week or so I've spent a bit of time on a feature I've always wanted to see land in django -- composite fields. The tickets have been open in the bug tracker for quite s

Changes to django.db.models.fields.Field API

I was wondering whether there would be support for changes to some of the methods on the field API... 1. Rename `Field._get_val_from_obj` and `Field.value_from_object` methods These two methods do exactly the same thing (except one returns a default value if available). In addition, the 'value_

Re: enum fields in django

> You can avoid those couple of joins by making your referenced table primary > key what > your enum value would have been and simple not joining it. > In this case you would simply use your referenced table for data integrity > through > foreign constraint enforcement. True, but when defining

Re: django admin: open popups as modals instead of windows

quot;-like interfaces instead? On Thu, Feb 26, 2015 at 12:40 PM, Chris Foresman wrote: > > > On Thursday, February 26, 2015 at 10:25:02 AM UTC-6, Thomas Leo wrote: >> >> I've opened a ticket [1] to implement the popups in the admin as modal >>> instead >>

Re: django admin: open popups as modals instead of windows

> > I've opened a ticket [1] to implement the popups in the admin as modal > instead > of windows. I'm no UI/UX expert but modals are more or less the standard > today, > windows looks like a relic from the 2000s. If it ain't broke don't fix it. The django admin is awesome, the reason it ha

Re: enum fields in django

m not going to push for you guys to implement something you don't want or don't think provides real value for users. Contributing to contrib.postgres is a possible option, but it's not really a postgres specific feature -- almost all of the major database vendors support it (sqlite be

enum fields in django

ation. Useful addition? Or does it overlap too much with the choices API? Thomas -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it

Re: Support for DATABASES['default'] = {}

Hello, I have a case where the 'default' database does not have any sense, but I still want the tests to create and manage transactions on other defined databases, so the option `--database` would not help me. I could put something in the default database like in memory sqlite for the tests but

Re: Psycopg2 version support

ps. 2.4.5 is the real minimum. The db.backends module loads without error at 2.4.3, but proper support for Inet arrays was not added until 2.4.5, so any code that uses GenericIPAddressField could fail unexpectedly. And now I'll shut up, because I'm not entitled to an opinion here yet

Re: Psycopg2 version support

;>> In the RHEL/CentOS universe, anyone who wants to run Django 1.8 needs >>>> either SCL's (software collections that are installed next to system >>>> binaries) or has access to psycopg2 2.5. >>>> >>>> So my point for CentOS/RHEL 6 can be ign

Re: Psycopg2 version support

ngo at the latest version don't have a valid upgrade path? Thomas On Tuesday, February 17, 2015 at 12:36:11 AM UTC+11, Florian Apolloner wrote: > > Not exactly, cause installing psycopg2 via the OS package manager should > __not__ require dev packages at all. > > On Monday, Fe

Re: Psycopg2 version support

> Installing psycopg2 does require development tools, while Django does not. I'm not offering this as a compelling argument for anything, just an observation. The postgres-*.*-dev libraries are a requirement for both 2.0.14 and 2.5, so if it's possible to install 2.0.14 via the package manage

Re: Psycopg2 version support

> Installing psycopg2 does require development tools, while Django does not Installing psycopg2 2.0.0 requires exactly the same `postgres-*-dev` libraries that 2.5 does as far as I know. If it is possible to install psycopg2 via the OS package manager then 2.5 can be installed via pip. On Monda

Re: ***SPAM*** Re: Middleware+Transactions:

ew lines of code. I guess this could be possible. I guess the diff for the docs could be longer then the diff for the code. Regards, Thomas -- Thomas Güttler http://thomas-guettler.de/ -- You received this message because you are subscribed to the Google Groups "Django developers (Contribu

Re: Middleware+Transactions:

s some magic at the beginning and end of each transaction. Can you understand what I wrote? Will a patch to provide settings.MIDDLEWARES_INSIDE_TRANSACTION be accepted? Regards, Thomas Güttler Am 03.02.2015 um 11:00 schrieb Aymeric Augustin: Hi Thomas, Both ways had advantages and drawback

Middleware+Transactions:

view transaction? Regards, Thomas Güttler -- Thomas Güttler http://thomas-guettler.de/ -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it

Re: ANN: Django website redesign launched

The new Design looks great! Awesome job! One thing I really like about https://docs.python.org/3/ is the ability to show/hide the side bar. The new design features a very large sidebar, being able to toggle it would be awesome. Also as previously mentioned trac doesn't look right yet. On Tues

Ordering of fields in subclasses of a form

Hi, I've submitted a pull request https://github.com/django/django/pull/3652 for the often requested feature "Easy way to customize ordering of fields on forms that use inheritance". I'd appreciate some feedback https://code.djangoproject.com/ticket/5986#comment:32 cheers, -- You received this me

Re: Creating data in TestCase.setUpClass() (proposed refactoring)

> > On Monday, 10 November 2014 17:14:32 UTC+11, Anssi Kääriäinen wrote: >> >> On Sun, 2014-11-09 at 16:19 -0800, Thomas wrote: >> >> > In order to make the whole Django test suite pass with that change, I >> > had to adapt a bunch of tests. I described the tec

Creating data in TestCase.setUpClass() (proposed refactoring)

Hi! I'm opening this topic to discuss some TestCase refactoring I have been working on, as it might have a non-negligible impact. The basic idea — which is not mine, see #20392 and that related discussion https://groups.google.com/forum/#!topic/django-developers/N0HEAD1ht8k — is to allow the c

Re: Why doesn't ModelChoiceField.queryset support slicing?

f fetching objects in the class definition is precisely why > the extra `.all()` calls exist in `ModelChoiceField` and part of the reason > why this does not work. The proposed code from Thomas is dangerous, and > even putting that code in the `__init__` will result in rather inefficient >

Re: Why doesn't ModelChoiceField.queryset support slicing?

I believe the problem is related to the fact that a sliced queryset cannot be filtered (it currently raises an AssertionError when trying to do so). If you need to produce a "top n results" queryset which can be filtered — which is implicitely required for the queryset you pass to a ModelChoice

Re: The greatest proposal yet: rename this damn group

+1 for @Wim Feijen's rewording but... I think the wording of the Group description isn't the issue, my guess is that people who make the mistake of asking django-user's questions in the django-developers mailing list didn't read the description to begin with. > They are almost all from people who

Re: The greatest proposal yet: rename this damn group

+1 for django-contributors django-contributors is clearer than django developers. When companies are hiring web developers, they will often title the position "django developer". Usually these companies are not looking for people who "contribute" to the framework, but use the framework to deve

Re: [ANNOUNCE] Django 1.7 released

Keep up the great work! On Tuesday, September 2, 2014 6:13:21 PM UTC-4, James Bennett wrote: > > Django 1.7 is now available: > > https://www.djangoproject.com/weblog/2014/sep/02/release-17-final/ > > Alongside this are bugfix releases for 1.4, 1.5 and 1.6. The bugfix 1.5 > release is the final r

Re: Why not Single Table Inheritance?

d fear: New columns that is outside my current comfort zone. I want to use STI the next time I need model inheritance. Regards, Thomas -- Thomas Güttler http://thomas-guettler.de/ -- You received this message because you are subscribed to the Google Groups "Django developers&qu

Re: FormWizard needs confirmation step logic. ticket #21644

The company I'm currently contracting for, makes heavy use of formtools, I'd be disappointed to see it go. On Monday, May 26, 2014 6:04:31 PM UTC-4, Tim Graham wrote: > > My observation is that not many core developers seem interested in > contrib.formtools these days. It was added by Adrian in

Why not Single Table Inheritance?

some discussion about this [1]. One reason against it was, that supporting not-null is not available. But a db constraint which checks the type and data column could solve this. What do you think? Thomas Güttler [1] https://code.djangoproject.com/wiki/ModelInheritance#a1

Re: Great Wall of DEP

Their is some value in commenting directly on a pull-request, for example you can comment on specific lines of code, and the interface is very friendly. With that being said, having a link to related google group pages (or another mail-archive site) in the pull-request message would be a great

Re: Feature request: ttl method for cache

obviously be disabled by default and docs > would say about the extra memory this feature needs. See https://groups.google.com/d/msg/django-developers/ctKJzBTONu8/opbWqUIcOKgJ for a similar case that has come up before. The tuple solution used there could easily be adapted to store the time

forms: get_changed_data(): Remember old values

above triple list available in django core? Thomas -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com.

Re: condition decorator: if-unmodified-since support and updated etags

thank you. It's submitted https://github.com/django/django/pull/2573 On 16.04.14 18:24, Tim Graham wrote: > The mailing list is typically only required for "major" features. I'm > not entirely sure the extent of what you are proposing, but I don't > think it'll need a mailing list discussion -- a

Re: condition decorator: if-unmodified-since support and updated etags

Hi Tim, I'm a bit confused by: On 16.04.14 16:51, Tim Graham wrote: > https://docs.djangoproject.com/en/dev/internals/contributing/ Requesting features: First request the feature on the django-developers list, not in the ticket tracker. It’ll get read more closely if it’s on the mailing list. Thi

condition decorator: if-unmodified-since support and updated etags

Hello, I have implemented support for the If-Unmodified-Since header http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.28 in the condition decorator and added an parameter to support updating of the etags for write operations http://tools.ietf.org/id/draft-reschke-http-etag-on-write-09.t

Ticket #22355: Humanize timedelta objects in Templates

Hi All, I've created a ticket along with the patch, tests and docs for a filter for humanizing timedelta objects on django templates. Please find the concerned ticket here: https://code.djangoproject.com/ticket/22355 It would be awesome if any of the generous committers could review it and adv

Check Framework Feedback

mon tags? Example: {{{ @register(Tag.COMPATIBILITY) }}} ---- Thank you for this check framework. I like it. Regards, Thomas Güttler -- Thomas Guettler, http://www.tbz-pariv.de/ -- You received this message because you are subscribed to the Google Groups "Django developers" group. T

Re: MAC adddres field

MAC fields, use netaddr for the python side and also add '__net_contains' type lookups for the PG net related functions. Not sure about how the support is past 1.4, as this delves deep into ORM internals for the extra field lookups. But it is at least being actively maintained now :-) -Thom

Re: UUID Field really wontfix?

rrent UUID-Field authors if they can create a patch. Thomas -- -- Thomas Guettler, http://www.thomas-guettler.de/ E-Mail: guettli (*) thomas-guettler + de -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group,

UUID Field really wontfix?

This ticket is closed since several years. Maybe it is time to think about it again. Add UUID Field: https://code.djangoproject.com/ticket/4682 Thomas Güttler -- Thomas Guettler, http://www.thomas-guettler.de/ E-Mail: guettli (*) thomas-guettler + de -- You received this message because

Improve Django markdown rendering.

I have submitted a path to improve the way Django handles html in markdown. Specifically how it escapes it. Ticket 6526 has all of the detail, could someone please review my patch. Thanks in advance. -- You received this message because you are su

Re: Django UnicodeEncodeError in errorlist

ne of the last steps is to encode the unicode result to (most of the times) utf8. I have seem a lot of unicode errors in django. But most of them were fixed long ago. The last (I know of): https://code.djangoproject.com/ticket/18063 "repr() should return only ascii, not unicode" Thomas

Edit Ticket Description in Trac

Hi, I would like to modify the descriptions of tickets. Unfortunately this is not possible for me at the moment. Can someone give me the permission for at least modifying my tickets? Thomas Güttler Trac Login is "guettli" -- Thomas Guettler, http://www.thomas-guettler.de/ E-Mai

Re: Ticket for Docs improvement Was: Proposal: upgrading the choices machinery for Django

Am 05.04.2012 10:03, schrieb Łukasz Rekucki: On 5 April 2012 09:45, Thomas Guettler wrote: Hi, I created a ticket, incl. patch https://code.djangoproject.com/ticket/18062 While the example itself is useful, I don't really think Django's documentation should state obvious f

Ticket for Docs improvement Was: Proposal: upgrading the choices machinery for Django

prove our documentation. Also, the fact that we *don't* have a sub-framework for this lets people do whatever they want -- including using the dj.choices module. So I am -1 on including this in Django proper. Adrian -- Thomas Guettler, http://www.thomas-guettler.de/ E-Mail: guettli (*) tho

Re: Proposal: upgrading the choices machinery for Django

(STATE_DONE, _('done')), ) state=models.CharField(max_length=16, verbose_name=u'Status', default=STATE_NEU, choices=states) }}} I like this since, you can access the verbose string like this: Foo.states[obj.state] -- Thomas Guettler, http://www.t

Re: Design decision on ticket #13223

Why would file uploads not work? If the file has already been uploaded on the previous object, it will appear in the clone view. Any files uploaded when the clone view is submitted will be uploaded on save and associated with the new object anyway. It is perfectly valid for two DB rows to point

Re: Read only Test Was: Speeding up tests

Hi, I am interested in it - could you be so nice and make this available anywhere? Thanks a lot in advance. TR Am 17.01.2012 um 12:04 schrieb Thomas Guettler: > Hi, > > same subject, but different content: > > we have a lot of tests which are read only. They don't mo

Read only Test Was: Speeding up tests

s unittest code is non public. But if there is any interest, we could make it public. Is anyone interested? Thomas Güttler On 16.01.2012 17:46, Anssi Kääriäinen wrote: .... -- Thomas Guettler, http://www.thomas-guettler.de/ E-Mail: guettli (*) thomas-guettler + de -- You received this messa

#2131 SendFile Support

tself. i.e. as serving large files is not what Django is made for. }}} -- Thomas Guettler, http://www.thomas-guettler.de/ E-Mail: guettli (*) thomas-guettler + de -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this

common variable (Deploying Feature in manage.py)

. Several deploy apps could use this common variable. In our company we have a common variable. PROD is zero: if STAGE: # some dev system... -- Thomas Guettler, http://www.thomas-guettler.de/ E-Mail: guettli (*) thomas-guettler + de -- You received this message because you are subs

Re: Suppressed template errors in admin

gt; a promise. If the django core makes a promise that TEMPLATE_STRING_IF_INVALID=RaiseMissingVariable() is supported in admin (and other contrib apps), I will help to get it done. Up to now, that's why I don't use the template language in my apps. Zen of Python: Errors should never pass silently.

#13024 Signal sent on application startup

) See https://docs.djangoproject.com/en/dev/topics/settings/#custom-default-settings But there are too many places, where the settings get loaded. I could write a patch, but this is more a design decision. Thomas -- Thomas Guettler, http://www.thomas-guettler.de/ E-Mail: guettli (*) thomas

Re: Advice on #13260 - '%' in args to urlresolvers.reverse()

om/msg25678.html > > > The original message got two responses; one saying quote automatically, > the other saying it's up to the user. The ticket is in "design decision needed" since 14 months: https://code.djangoproject.com/ticket/13260 Who can make this decision? Thom

Re: ImportError catching in urlresolvers.py

ion (and the AttributeError). I want to see the original exception. It would be nice to have a better solution in django. Maybe a settings variable CATCH_EXCEPTIONS? Thomas -- Thomas Guettler, http://www.thomas-guettler.de/ E-Mail: guettli (*) thomas-guettler + de -- You received this message

Re: State of X-Sendfile support?

On 25.03.2011 12:55, Łukasz Rekucki wrote: > On 25 March 2011 12:34, Thomas Guettler wrote: >> Hi, >> >> I look at your example code. You need to name the webserver in the >> code. That's not very nice. I guess it should be possible to >> guess the web

Re: State of X-Sendfile support?

Hi, I look at your example code. You need to name the webserver in the code. That's not very nice. I guess it should be possible to guess the webserver (apache vs nginx) by looking at request.META. Documentation would be nice.... Thomas On 25.03.2011 10:23, Gustavo Narea wrote: >

Re: Expensive queryset cloning

Hi Alexander, I have seen this in my app, too. It still runs fast enough. But I guess the django code could be optimized. Thomas On 15.03.2011 01:49, Alexander Schepanovski wrote: > I was optimizing my django app and ran into this. My app was spending > too much time cloning querys

Re: contributing to django as a part of master thersis

On Wed, Feb 9, 2011 at 12:00 PM, Russell Keith-Magee wrote: > Another interesting, but more complicated opportunity in this area > would be asynchronous database calls [1], which some databases (by > which I mean, Postgres) support. > > [1] http://initd.org/psycopg/docs/advanced.html#asynchronous-

Re: Strong security measures for the Auth Framework

Also see this comment: http://code.google.com/p/django-registration/issues/detail?id=14 On Fri, Nov 26, 2010 at 20:18, Thomas Schreiber wrote: > I agree that instructions should be clearer on the importance of > adding password strength rules. We can all agree there is no one size >

Re: Strong security measures for the Auth Framework

I agree that instructions should be clearer on the importance of adding password strength rules. We can all agree there is no one size fit all solution to password strength, but a standard default would be helpful for production. I recently attempted to use the cracklib module on webfaction but it

Re: RFC #9964 - fix "missing" db commits by forcing managed transactions to close

e case (as in the case of raw > SQL), the user is required to call transaction.set_dirty() to get correct > behavior. > ... -- Thomas Guettler, http://www.thomas-guettler.de/ E-Mail: guettli (*) thomas-guettler + de -- You received this message because you are subscribed to the Google

Should CSRF Middleware return 403 or 500 error from AJAX call?

Hey devs, I posted this on django-users last week but didn't hear back. I'm wondering if this is a bug and if so, if I should take a crack at a patch. I ran into some unexpected CSRF behavior. An AJAX request that includes the "X-Requested-With: XMLHttpRequest" header but does not include csrf to

#4992: Cache GET requests with QUERY_STRING

member) should not set "ready for commit". Could someone please review it? Thomas -- Thomas Guettler, http://www.thomas-guettler.de/ E-Mail: guettli (*) thomas-guettler + de -- You received this message because you are subscribed to the Google Groups "Django developers&quo

  1   2   3   >