Re: Field 'roof_age' expected a number but got ('1',)

Also take off each comma after the assigment and that should fix it all, forget about indexing as i recommend before El sáb, 17 sept 2022 a las 14:38, Esteban Chacon Martin () escribió: > Use requests.POST.get('roof_age')[0] instead, seems to me like you are > getting a list ins

Re: Field 'roof_age' expected a number but got ('1',)

Use requests.POST.get('roof_age')[0] instead, seems to me like you are getting a list instead of a string when doing the get -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group an

Re: adding permission_required decorator for class based view

The introduction doc to class based view https://docs.djangoproject.com/en/4.0/topics/class-based-views/intro/ seems to prefer decorators, as it only illustrates the decorator side of things with code blocks, and doesn't illustrate mixins at all. If the mixins are the way to go, it should be ref

adding permission_required decorator for class based view

Hi, as of today, adding a permission_required and / or a login_required decorator on a class based view is a bit ugly, as you have to decorate the dispatch method, which you then have to write down in your class. On top of that, you can't directly use the decorator itself, as you have to wrap i

Re: Inconsistency when rolling back a migration that adds a primary key

d I should just switch the order of the operations. If I'm missing something, please let me know. Tim On Tuesday, 3 October 2017 21:57:35 UTC+1, Tim Martin wrote: > > Hi all, > > I've been looking at bug #28542, in which a migration can be played > forwards but not reve

Inconsistency when rolling back a migration that adds a primary key

Hi all, I've been looking at bug #28542, in which a migration can be played forwards but not reversed. I think I can see what's happening, but I'm not 100% sure what the right resolution is, so I wanted to get some input. The migration in question looks something like this: # Start out with

Re: Contribution

Thank you ! On Tuesday, May 16, 2017 at 8:37:02 AM UTC-4, Tim Graham wrote: > > Hi Martin, have you read the contributing documentation? > > > https://docs.djangoproject.com/en/dev/internals/contributing/new-contributors/ > > On Tuesday, May 16, 2017 at 8:34:30 AM UTC-4,

Contribution

Hi Everyone, I'm fairly new here , I have been using Django for past year and would like to contribute. Could someone give me any key advice on where to start. Thank you -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django

Re: To keep or not to keep: logging of undefined template variables

I don't have any objection to removing this. However, the thought occurs that my patch to the handling of undefined variables could enhance this to make it more useful. I think we could log in the case where a conditional expression actually depends on an undefined variable. I haven't thought a

Re: Template handling of undefined variables

On Wednesday, 1 March 2017 19:52:22 UTC, Luke Plant wrote: > > > This is a really big backwards incompatibility, as far as I can see. It > means that any filter may now get passed `UndefinedVariable` instead of > being passed `None` or string_if_invalid. So for example, the following > templat

Re: Template handling of undefined variables

On Monday, 27 February 2017 10:43:02 UTC, Luke Plant wrote: > > > > On 05/01/17 02:39, Tim Martin wrote: > > 2) There appears to be an inconsistency in the default_if_none >modifier. If I have a template with > >x|default_if_none:y = {{x|default_if_none:y}} >

Re: Template handling of undefined variables

On Tuesday, 28 February 2017 13:39:21 UTC, Luke Plant wrote: > > > > On 28/02/17 15:24, Marten Kenbeek wrote: > > What about adding a filter |defined that returns True if a variable is > defined, False otherwise? It may not solve any problems when it's left > implicit, but at least it allows us

Re: Template handling of undefined variables

Actually, I can imagine that the option might be worth keeping permanently. I think both the "exception on use of undefined" and "treat undefined as different from all other objects" would both be valid modes. Treating undefined as None is probably only justifiable for backward compatibility, t

Re: Methodology for increasing the number of PBKDF2 iterations

rsion. The up-side is PBKDF2 is significantly better than was previously calculated. Enjoy! On Monday, January 30, 2017 at 2:09:56 PM UTC-5, Martin Koistinen wrote: > > *IMPORTANT NOTICE:* I've just made an important change to the Google Docs > Sheet here: > https://docs.goo

Re: Methodology for increasing the number of PBKDF2 iterations

*IMPORTANT NOTICE:* I've just made an important change to the Google Docs Sheet here: https://docs.google.com/spreadsheets/d/16_KdYAW03sb86-w_AFFnM79IaTWQ7Ugx4T0VMfGteTM/edit?usp=sharing Realizing that most security policies make requirements such as "At least 1 character must be a numeral", et

Re: Methodology for increasing the number of PBKDF2 iterations

Updated the sheet with more recent GPU pricing. On Thursday, January 19, 2017 at 1:19:57 PM UTC-5, Martin Koistinen wrote: > > All, I've converted my worksheet into a Google Docs Sheet here: > https://docs.google.com/spreadsheets/d/16_KdYAW03sb86-w_AFFnM79IaTWQ7Ugx4T0VMfGteTM/ed

Re: Methodology for increasing the number of PBKDF2 iterations

spreadsheet to tweak for your system and security policy. Comments and suggestions are welcome and if appropriate, I'll make edits accordingly. On Wednesday, January 18, 2017 at 12:32:55 PM UTC-5, Martin Koistinen wrote: > > Tim, I've sent you a model I've assembled re

Re: Methodology for increasing the number of PBKDF2 iterations

eased the iterations to 100,000 on master (targeting Django 2.0). It > would be nice to determine a guideline for how to determine future > increases. > > On Monday, January 16, 2017 at 12:55:25 PM UTC-5, Martin Koistinen wrote: >> >> Tobias, >> >> Thanks for th

Re: Methodology for increasing the number of PBKDF2 iterations

user accounts. Also, if a developer is experienced/motivated enough to *lower* the hash iterations, s/he'll be more likely to also be experienced/motivated enough to put other controls in place to compensate. Best, - Martin On Sunday, January 15, 2017 at 5:45:02 PM UTC-5, Tobias McN

Re: [Feature request] Template language type annotations (#27703)

g a test suite pick up these issues is my preferred pattern, but anyway you develop it you'll have a very small amount of use from most projects. Best Regards, Martin Owens Inkscape Website Admin -- You received this message because you are subscribed to the Google Groups "Django deve

Re: Methodology for increasing the number of PBKDF2 iterations

their own Python and doing so without OpenSSL. I'm guessing that > any operating system Python will have the OpenSSL bindings. Or is that a > bad assumption? > > On Wednesday, January 4, 2017 at 2:13:09 PM UTC-5, Martin Koistinen wrote: >> >> I think this is a pretty solid

Re: Template handling of undefined variables

On Friday, 6 January 2017 10:15:22 UTC, Alasdair Nicol wrote: > > Hi, > > On Thursday, 5 January 2017 17:51:39 UTC, Tim Martin wrote: >> >> >> >> On Thursday, 5 January 2017 04:15:31 UTC, Carl Meyer wrote: >>> >>> Hi Tim, >>> >>

Re: Template handling of undefined variables

On Thursday, 5 January 2017 04:15:31 UTC, Carl Meyer wrote: > > Hi Tim, > > On 01/04/2017 03:39 PM, Tim Martin wrote: > > > 1) There are test cases where we have templates that should treat "x > >is y" as True where x and y are both undefined. &

Re: Methodology for increasing the number of PBKDF2 iterations

17 at 2:13:09 PM UTC-5, Martin Koistinen wrote: > > I think this is a pretty solid guess. Bear in mind this was a direct > install from Python.org. > > The important thing here is, this demonstrates that we cannot just assume > that all Python 3 installs have a "fast"

Template handling of undefined variables

Hi all, I've been looking at bug #24977 (Template variables with a value of None are considered to be == to non-existent properties). The problem is that in a template: {% if user.pk == some_object.invalid_property %} ... this gets rendered when the user is logged out {% endif %} This is because

Re: Methodology for increasing the number of PBKDF2 iterations

-5, Tobias McNulty wrote: > ... > Martin, is it possible your version of Python 3 is not linked against > OpenSSL and hence is missing the fast version of pbkdf2_hmac? I haven't had > a chance to try your benchmark yet, but in a quick test I don't see any > difference bet

Re: Methodology for increasing the number of PBKDF2 iterations

"pbkdf2_sha256" with 100,000 iterations, verification takes, on average, 0.2751s What am I missing here? On Tuesday, January 3, 2017 at 12:45:42 PM UTC-5, Martin Koistinen wrote: > > I think the best practice is to set the iterations as high as you can > tolerate without adversel

Re: Methodology for increasing the number of PBKDF2 iterations

"pbkdf2_sha256" with 100,000 iterations, verification takes, on average, 0.2751s What am I missing here? On Tuesday, January 3, 2017 at 12:45:42 PM UTC-5, Martin Koistinen wrote: > > I think the best practice is to set the iterations as high as you can > tolerate without adversel

Re: Methodology for increasing the number of PBKDF2 iterations

I think the best practice is to set the iterations as high as you can tolerate without adversely affecting the user experience as they log-in. Iteration numbers as high as 200,000 for SHA-256 or even more are not unheard of these days. Without looking at an application's password expiration pol

Re: DEP pre-proposal for a simpler URLs syntax.

le_detail), > ), > ), >), > ] > > So long as the proposal doesn't make the above url_tree pattern impossible (or harder to do) then I think it's a positive addition. (I have projects which have very interesting urls patterns) Best Regards, Martin Owens Inksc

Re: Better form fields for django.contrib.postgres.fields

*OK thanks for the replies. The first enhancement would be a change in how choices are handled for the ArrayField. With this change,* *choices would be based on the base field. If choices keyword argument is given, a multiple choice field is used and the array value will be composed* *of thes

Better form fields for django.contrib.postgres.fields

Hi, This is my first time contributing to Django. It's a lot of different features in one to improve how form fields are produced for ArrayField, HStoreField and JSON FIeld. I opened a ticket here with more details and a screenshot of the admin for a sample model. https://code.djangoproject.c

Table Locks and bulk creating inherited models

Is there a particular reason Django doesn't implement table locks? These are vendor-specific, but seem to be common to various SQL backends, which is something Django generally does well. I am working on an application in which I would like to be able to perform bulk create on inherited models.

Cache invalidating with generic class based views

make it better. Best Regards, Martin Owens -- 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, send an email to django-developers+uns

Re: Making Django more PaaS-friendly

n "who should be editing this setting" not just what it's for, if it's a secret or if it should be different or the same per instance. Best regards, Martin Owens On Monday, April 11, 2016 at 7:33:54 AM UTC+1, James Bennett wrote: > > Apologies for how late in the proces

Cleaning up admin CSS

someone please provide me with the basics on how to make changes to the actual source of the project and submit them for inclusion in an official release. Many thanks and looking forward to helping as much as I can. Martin -- You received this message because you are subscribed to the Google G

Re: GenericForeignKey: loosening the requirements on the ContentType reference

re options, visit https://groups.google.com/d/optout. digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Re: GenericForeignKey: loosening the requirements on the ContentType reference

ups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/20151209040738.GB4130%40fishbowl.rw.madduck.net. For more options, visit https://groups.google.com/d/optout. digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Re: GenericForeignKey: loosening the requirements on the ContentType reference

oups.google.com/d/msgid/django-developers/20151209040123.GA4130%40fishbowl.rw.madduck.net. For more options, visit https://groups.google.com/d/optout. digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Re: GenericForeignKey: loosening the requirements on the ContentType reference

. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/20151209035904.GA13218%40fishbowl.rw.madduck.net. For more options, visit https://groups.google.com/d/optout. digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

GenericForeignKey: loosening the requirements on the ContentType reference

m/d/optout. digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Re: #25227 Add utility method `get_updated_model()` to `ModelForm`

might get confused if I think get_updated_model might return a model class instead of an instance. Could we use something simple like 'update()' and 'commit()' to which save would call both? Martin Owens, -- You received this message because you are subscribed to the Goog

Re: QuerySet.as_manager doesn't offer a way to use_for_related_fields

any basic manager behavior. Regards, Martin -- 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, send an email to django

QuerySet.as_manager doesn't offer a way to use_for_related_fields

r honor a class attr of the same name on the queryset. Is this a reasonable improvement? Is one of those possible implementations (or a completely different one) better? Regards, Martin Chase -- You received this message because you are subscribed to the Google Groups "Django developers (C

FileField binary/text mode

del field attributes? Thanks, Martin -- 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. To post to th

Re: Support for function application in ORDER BY

On Monday, 16 June 2014 01:25:45 UTC+1, Josh Smeaton wrote: > > Nice work, I think that's a lot better. The only thing that now worries me > is that order_by doesn't accept sql parameters for some reason. I'm not > sure how many expressions produce sql_params and if they'd be useful in an > orde

Re: Support for function application in ORDER BY

On Wednesday, 11 June 2014 12:28:20 UTC+1, Josh Smeaton wrote: > > > Model.objects.filter(...).order_by( F('fld_a').desc(), > F('fld_b')).asc() ) > > Model.objects.filter(...).order_by( (F('fld_a')+F('fld_b')).desc() ) > > I actually really like this. It's simple, clear, and gets around the >

Re: Support for function application in ORDER BY

On Tuesday, 10 June 2014 00:48:14 UTC+1, Josh Smeaton wrote: > > > However, I think having some special case code in filter(), annotate() > and anything else that takes expressions would be OK > > I strongly disagree with this. Expressions are context insensitive at the > moment, which means they

Re: Support for function application in ORDER BY

On Monday, 9 June 2014 21:28:51 UTC+1, Tim Martin wrote: > > > On Monday, 9 June 2014 20:44:08 UTC+1, Tim Martin wrote: >> >> >> I'll go ahead and try to implement this using __neg__() to invert the >> ordering. >> >> > It's still pr

Re: Support for function application in ORDER BY

On Monday, 9 June 2014 20:44:08 UTC+1, Tim Martin wrote: > > > I'll go ahead and try to implement this using __neg__() to invert the > ordering. > > It's still pretty rough, but there's some code in https://github.com/timmartin/django/tree/order_by_expr

Re: Support for function application in ORDER BY

My concern about the filter(foobar_lt=-F('baz')) issue is that it violates the principle of least surprise: it will be accepted silently and do something that nobody could expect unless they know a bit about the internals. However, I think having some special case code in filter(), annotate() a

Re: Support for function application in ORDER BY

On Sunday, 8 June 2014 13:24:01 UTC+1, Josh Smeaton wrote: > > I've thought about this previously, and what I had in mind was: > > - Expressions should support an ordering parameter of some kind in the > constructor, and save it to an ordering property. Default to ASC > - If we go with Marc's sug

Re: Support for function application in ORDER BY

es in the ORDER BY compilation logic (possibly quite substantial), or we can support: Article.objects.order_by(Desc(LowerCase('title')) The latter is a lot easier to implement, and strikes me as a nicer API. However, it's a significant step away from the ordering API we have at th

Re: Support for function application in ORDER BY

Funnily enough, I'd already seen that patch but I hadn't figured out the full significance of it. I attempted to solve #22288 (https://code.djangoproject.com/ticket/22288), but spotted that your patch would possibly solve the problem entirely, and at the very least breaks my attempt to solve th

Support for function application in ORDER BY

Hi all, I was looking at implementing the behaviour proposed in #13006 (https://code.djangoproject.com/ticket/13006). In short, the idea is to allow decorating fields in order_by() with a LowerCase() modifier to apply LOWER() in SQL before ordering: Articles.objects.all().order_by(LowerCase

admin_order_field on __unicode__ method does not enables sorting

n.register(ContainerProfile) class ContainerProfileAdmin(admin.ModelAdmin): list_display = ('__unicode__', ) If I rename __unicode__ to xxx for example, the sorting in admin on such field works. Using latest stable/1.7.x branch from github. Thanks, Martin -- You received this message because y

Field.get_default() returning dict instance causing migration to fail

f Field.get_default() returns something else than a string (or whatever psycopg2 accepts), the db backend fails. Now the question - should Field.get_default() always return a string (and thus the bug is in django-jsonfield app) or should Django handle this somehow? Should not the Field.g

The model API and strong typing

if the string is longer than max_length etc. Is there a rationale for why we don't do this? Martin -- 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 ema

Re: Proposal: A diagram showing Class Based View inheritance and mixins.

I've used this one http://epydoc.pythondiary.com/generic-views/ with good results. Very low-level but totally useful. mjl -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails

Re: manage.py and pyc's

Well, the sneaky workaround would probably be to ship a totally simple management/commands/foo_command.py that does nothing more than "from only_as_pyc import *". Would that work for your use case? mjl -- You received this message because you are subscribed to the Google Groups "Dja

Re: Deprecate FCGI support in Django 1.7

Is there actually a problem with flup? Not being maintained doesn't mean it's totally broken and it obviously works just fine for a lot of folks? mjl -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group

Re: Proposal: make Model __unicode__() default to self.name

> In addition to the previous answers, I find it important to have an unambiguous __unicode__ / __str__, and name isn't necessarily unique. Perhaps to have it a tiny little bit more useful, have it default to "MyModel object (object_pk)" ? mjl -- You received this message because y

Re: django and paramstyle: what's the actual story?

As for the death of '%s' style -- yes please, with sprinkles on top. It is totally violating the principle of least astonishment as anyone will expect '%s' to expand to a parameter string; yet that's not what it does, it magically adds quotes and whatnot. The other two variants are widely u

Custom ordering using SQL backend

c. where the usual alphanumeric sorting does not make sense. If there is enough interest, I could dig into Django core to make this whole functionality more generic, so it could be merged into a development branch in Django. I'd love to read some thoughts from you how / if I should contin

Re: URLValidator on urls without protocol

Yes it indeed was. That was a mistake on my part. I saw it as soon as I submitted. Sorry. On Nov 17, 2012, at 11:32 PM, Karen Tracey wrote: > On Sun, Nov 18, 2012 at 12:21 AM, Jared Martin wrote: > I don't mean to wake a dead dog, but what has become of this? I came across >

Re: URLValidator on urls without protocol

I don't mean to wake a dead dog, but what has become of this? I came across this problem today. For now, I've subclassed. But it should be fixed, right? On Sunday, June 20, 2010 7:35:23 PM UTC-6, Samus_ wrote: > > ticket: http://code.djangoproject.com/ticket/13804 > > also found a real-life scena

Weird characters in HTTP_USER_AGENT

ding ""UTF8"": 0x8a","" So, my question is, should not Django solve any issues with characters in HTTP headers so I can rely on it and store it safely to DB? If not, what do you suggest to do with such user agent strings? DB is set to UTF8. I am usin

Re: Feature request: collectstatic shouldn't recopy files that already exist in destination

Good idea, but shouldn't it be a per-storage thing? Perhaps this could be done with a couple of callbacks in the collectstatic run: - Before collectstatic starts, so the storage backend can pick up its inventory from the remote - One called for each file that would be copied, and that c

Re: Django's CVB - Roadmap?

> > This is the real issue. The docs. It's one of the issues, but I'm not really convinced it is the only one. My experience with CBV usually has gone like this: 1. "I need a view, let's do it with CBV" 2. "Oh hey, that was easy!" 3. "I need some more functionality" 4

An appeal for insight into the development of Django

iated. Once finished I will gladly share my results and any new insights gained on the topic with you. Kind regards, Martin Schönberger (maschon...@gmail.com) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group

Re: discrepancy in default CSRF settings

> > However, it seems that the defaults are to add the middleware, but not the > context processor. Is there a specific reason for this? > The docs say: In the corresponding view functions, ensure that the 'django.core.context_processors.csrf' context processor is being used. Usually, thi

Re: FormMixin success_url should accept callable

Hi, so I should read more carefully :)) I use Django for two years but I don't remember that I saw the reverse_lazy function before :) Yes, you can override it but it is not very DRY. Thanks, Martin On Sun, 08 Apr 2012 23:53:01 +0200, Andrew Ingram wrote: Hi Martin, There ar

FormMixin success_url should accept callable

:) Kind regards, Martin Tirsel -- 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 to django-developers+unsubscr...@g

Re: Possible bug with admin inlines

Danny reading your reply gave me an idea to try and it worked. I switched the order of the inlines. So I put C first, then B. This way C validates properly, then B is deleted and the cascaded deletion deletes C and everything works as expected. On Monday, March 5, 2012 6:15:18 PM UTC-5, Danny W

Possible bug with admin inlines

Hello, I have come across this issue in Django v1.2.5, just test it on 1.4rc1 and can still reproduce. Not sure if it's a bug or a case of "don't do that". But here goes. Here's the models.py: http://pastebin.com/8QU9dkYd Here's the admin.py: http://pastebin.com/JGFu5nhv So what we have are

Re: Newline stripping in templates: the dnl way

> > foo bar {# >> #}baz >> >> >> You just made a strong argument against multiline tags: I wouldn't want > to see them abused this way! > Ah, I fully expected to be shot down on "aesthetic" reasons. I still think it's better to have some (maybe slightly ugly) way to do things than no way an

Re: Newline stripping in templates: the dnl way

For this (avoiding newlines) the currently discussed multiline tags would work pretty well too without adding more cruft to the template language: foo bar {# #}baz mjl -- You received this message because you are subsc

FileField should be a context manager

pen() as a_file: a_file.read() Any reason I shouldn't make a ticket and patch for this? - Martin Chase -- 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.

Ability to get values using HTTP GET in admin changelist_view

Hello, It would be of great help to me if the ability to pass variables through HTTP GET were possible within the admin changelist view. For example, I use Django admin tools to manage security advisories that come from various sources. I need the ability to create a "meeting view," which essent

Re: assertFormSetError

Thank you for reviewing it. Cheers, Martin On Mon, Jun 27, 2011 at 2:29 PM, Russell Keith-Magee wrote: > On Mon, Jun 27, 2011 at 12:58 AM, Martin Green > wrote: >> The unittest client currently does not allow for the testing of >> non-formset errors.  I have made a ticket

assertFormSetError

it should be aiming for. Currently the documentation states it was added to SVN, should this be changed to 1.4, and some suitable release note added? Can I presume if it is added to trunk that it will become part of django 1.4 in due course? Regards, Martin -- You received this message because

Re: assertFormSetError

Documentation has now be changed assuming that it will be added to Django 1.4, after input from IRC channel. Martin On Sun, Jun 26, 2011 at 5:58 PM, Martin Green wrote: > The unittest client currently does not allow for the testing of > non-formset errors.  I have made a ticket for this &

Error with new version of psycopg2 [ticket 16250]

When i use the version 2.4.1 of psycopgs testing works normal, but with 2.4.2 i got this error: https://code.djangoproject.com/ticket/16250 -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develo

old session data revived?

I am trying to store a python object in the session data, which holds lots of parameter values from various previously visited forms. All of the submit actions push to the same view function. After seeing that data appear to be randomly wrong, I am managing the saving of this data myself with cP

Re: django-3k

just run it for yourself. Regards, Martin -- 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...@googlegroups.com. To unsubscribe from this group, send email to djang

django-3k

I have now published my 3.x port on bitbucket, at http://bitbucket.org/loewis/django-3k/ It can now convert and start the test suite, however, this doesn't produce any results, yet. Feel free to use the bitbucket issue tracker to report problems or contribute changes. Regards, Martin --

Re: Porting Django to Python 3

APPS > setting. Again, I don't see a need to support these. I doubt the ability to create them would be the primary reason why people would switch to Python 3... > I imagine that some of these things will 'come out in the wash', so to > speak, and the lack of automatic conversio

Re: Porting Django to Python 3

fferent (unicode vs. bytes in both cases). Fortunately, Django already attempts to differentiate bytes and unicode fairly well, so it was easy to fix the remaining spots which would break under 3.x. Regards, Martin -- You received this message because you are subscribed to the Google Grou

Re: Ticket #399 -- bigint support

like I did. All the best, /Martin On Dec 12, 10:29 am, Manu wrote: > Gosh... copy paste was a bit fast... ti > washttp://code.google.com/p/django-iptocountry/ > > Manu -- You received this message because you are subscribed to the Google Groups "Django developers" group. T

Re: Running unit tests when you can't create a new database

Sean, That's great stuff; exactly what I was looking for. Thanks for the pointer! /Martin On Dec 9, 12:40 pm, Sean Brant wrote: > This might help you > outhttp://ericholscher.com/projects/django-test-utils/keep_database_runn > Or at least give you some pointers. > > -

Re: Running unit tests when you can't create a new database

where you don't have database creation privileges. Before I dig in and try to figure this out by myself, has anyone out there written a test runner you could share with me? /Martin On Dec 9, 4:50 am, Russell Keith-Magee wrote: > On Wed, Dec 9, 2009 at 7:22 PM,   wrote: > >&g

Re: Running unit tests when you can't create a new database

when I test against another database than MySql. /Martin On Dec 8, 6:21 pm, rebus_ wrote: > 2009/12/9 Martin Omander : > > > > > Hi all, > > > How about letting Django users run unit tests without creating a new > > test database? > > > To use Django'

Running unit tests when you can't create a new database

king the Django testing code. Would it be worth it to add an option in the testing code that would allow users to run unit tests without database creation privileges? Any thoughts on what it would look like? Cheers, /Martin -- You received this message because you are subscribed to the Google

Re: Ticket #7539 (ON DELETE support) in Django 1.2?

On Sat, Aug 15, 2009 at 10:45:44AM -0700, hcarvalhoalves wrote: > ForeignKey(..., propagate_on_delete=True) > CASCADE > > ForeignKey(..., propagate_on_delete=False, null=False) > RESTRICT > > ForeignKey(..., propagate_on_delete=False, null=True) > SET NULL > > ForeignKey(..., propagate_on_delet

Study on communication and collaboration in software development teams

hesitate to contact me. Best regards from Paderborn, Germany Martin Gelhaus (gelh...@uni-paderborn.de) -- Click here to do the survey: http://thales.cs.upb.de/limesurvey185/index.php?lang=en&sid=91192&token=gvzn8zveq9p9cw9 Martin Ge

Re: 1.2 Proposal: django debug toolbar in contrib

On Tue, Aug 11, 2009 at 09:50:35AM -0500, Alex Gaynor wrote: > Right now django-debug-toolbar has a pretty stable panel interface and > I actually can't recall it changing since release. A possibly more > interesting issue is that some of the debug information it get's is > somewhat of a hack, th

Re: Py3k port updated

Django that I haven't ported. Django apparently features a large variety of error reporting scenarios, depending on where exactly in Django the error occurs. If you run into problems, feel free to contact me. Regards, Martin --~--~-~--~~~---~--~~ You received t

Re: Py3k port updated

> 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

Re: Py3k port updated

though that the test suite fails quickly, with just a few tests passing. Contributions are welcome. Regards, Martin --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to t

Py3k port updated

. The patch applies against Django's trunk; it was tested with the HEAD of Python's py3k branch (i.e. 3.1). Regards, Martin --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" gr

  1   2   >