Re: Python 3: should we apply unicode_literals everywhere?

I would also prefer Option 2, as the places where str('...') are needed are not all that many. Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https:/

Re: Python 3 - style question

I think Option 2 is better, for the reasons you state. Regards, Vinay Sajip -- 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 g

Re: Python 3 port status

o, the diff is pretty big, so it may push the diff-determining code into less well tested areas. So I use meld, which hasn't let me down :-) Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" group.

Re: Python 3 port status

b issue tracker on the repo [4]. Note that my changes are in the django3 branch, and not the master branch. Regards, Vinay Sajip [1] https://github.com/vsajip/django [2] https://gist.github.com/1373553 [3] https://github.com/vsajip/django/blob/django3/django/utils/six.py#L356 [4] https://githu

Re: json vs simplejson

s one place where there are limitations in the 2.x stdlib - other places include cStringIO and cookies. For example, if you pass a Unicode object to a cStringIO.StringIO, it doesn't complain, but does the wrong thing: >>> from cStringIO import StringIO; StringIO(u'abc

Re: admin_changelist failing on Oracle

ing in the near future. There was already a ticket for this - #17932 - which I've reopened, and added a pull request. Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, s

Re: admin_changelist failing on Oracle

'date'. I added a db_column='event_date' and all seems well. As this is a standard Django regression test, I presume a ticket should be raised? Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" gr

admin_changelist failing on Oracle

HANGELIST_EVENT_SQ".nextval INTO :new."ID" FROM dual; END; The error is django.db.utils.DatabaseError: ORA-06552: PL/SQL: Compilation unit analysis terminated ORA-06553: PLS-320: the declaration of the type of this expression is incomplete or malformed Can anyone sugge

Re: Python 3 port - now available on GitHub

fixed that a couple of days ago. Anssi has kindly posted feedback to the GitHub issue tracker on my repo, so I'm following up there. Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send

Re: Python 3 port - now available on GitHub

s a little out of date). It's a self contained script, so just downloading it and running it should allow you to create a working virtual environment. Thanks for your input so far. Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Djan

Re: Python 3 port - now available on GitHub

opyright", "credits" or "license" for more information. >>> from django.db import utils >>> Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this gro

Re: Python 3 port - now available on GitHub

"/usr/lib/python3.2/unittest/case.py", line 889, in assertIn >     if member not in container: > TypeError: Type str doesn't support the buffer API I'll investigate this too. I've enabled the issue tracker in the port's GitHub repo [1] - feel free to add any furt

Python 3 port - now available on GitHub

, expected failures=2, unexpected successes=1) Recent tests only cover the SQLite backend and were run on Linux. Help with testing other DB backends (and the GIS functionality) would be much appreciated! Regards, Vinay Sajip [1] https://github.com/vsajip/django/tree/django3 [2] https

Re: GitHub migration done!

Hi Charles, > I setup a new mirror using hg-git: > >  https://bitbucket.org/django/django-hg-git > > I work for Bitbucket and I'll make sure the mirror is maintained. Thanks very much for doing this. Regards, Vinay Sajip -- You received this message because you are subs

Re: GitHub migration done!

t it up as a cron job, so it's not actually a mirror yet, but some manual pulls and pushes to the remote Mercurial repo worked fine. I'll wait to hear back from Atlassian to see if they've set anything up, before I do anything more. Regards, Vinay Sajip -- You received this messa

Re: GitHub migration done!

better than no mirror at all. Okay, I'll take a look at it. In the meantime, I've pinged someone at Atlassian to see if they already have something/might be interested in hosting and maintaining a mirror (since BitBucket actually uses Django). I'll still try it out with a local re

Re: GitHub migration done!

nance, and I do use Mercurial as well as Git. Did you implement it using a local repo and a cron job, or was there something else you used which was more purpose-built? Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django develope

Re: GitHub migration done!

t Mercurial mirror of Django: https://bitbucket.org/django/django/ Is that going to be changed to be a mirror of the GitHub repo, or will it disappear altogether? Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers&quo

Django use of stdlib HTMLParser "internals"

I would like to get an opinion about this from the Django committers - so can someone please look at this python-dev thread and/or Python issue and comment? Thanks and regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers"

Re: Errors in tests

ltins] to the seemingly equivalent def _reset_dicts(self, value=None): value = copy(value or {}) value.update({'True': True, 'False': False, 'None': None}) self.dicts = [value] then the errors no longer occur. Ticket created: https://code.django

Errors in tests

'other'... vinay@eta-oneiric64:~/projects/django/tests$ All the errors appear to have the same root cause. I'm testing with Python 2.7.2+ (default, Oct 4 2011, 20:06:09) on Ubuntu Oneiric 64- bit. Can anyone shed any light on this? The value being passed to the update method is an ins

Django and dictionary ordering

ID: {'username': 'adrian', 'password2': 'secret', 'password1': 'secret'} != VALID: {'username': 'adrian', 'password1': 'secret', 'password2': 'secret'} - VALID: {'username

Python 3 port updated for 2.6 compatibility

et up working GIS configurations, so the GIS backends remain untested. Regards, Vinay Sajip [1] https://bitbucket.org/vinay.sajip/django/ -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-deve

Re: Proposal: drop Python 2.5 support in Django 1.5

ple. I'm not sure what versions of 2.6 are on different releases of RHEL, CentOS etc. Regards, Vinay Sajip -- 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@googlegroup

Re: Proposal: drop Python 2.5 support in Django 1.5

ted. Supporting 2.6- >2.6.4 will require cleaning kwargs, and to avoid this one would need to state that Django will only support 2.6.5 onwards. Of course, that might affect quite a lot of users with 2.6 system Pythons which are < 2.6.5 (e.g. on Ubuntu Jaunty the system Python is 2.6.2). Regar

Re: Django 1.4 alpha on December 22nd

l of u() and b() from the port, as well as more extensive testing on both 2.x and 3.x. Regards, Vinay Sajip -- 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. T

Re: Python 3 port - all Oracle tests (bar one) now pass on 2.7.2 and 3.2.2 with the same codebase

On Dec 11, 6:02 pm, Aymeric Augustin wrote: > > There are also the GIS database backends in django.contrib.gis.db.backends: > postgis, spatialite, mysql, oracle. > Of course - well, I wouldn't want to have nothing to do ;-) Regards, Vinay Sajip -- You received this messag

Python 3 port - all Oracle tests (bar one) now pass on 2.7.2 and 3.2.2 with the same codebase

539f \u3081\u3050\u307f')) AssertionError: '¿¿ ¿¿¿' != '林原 めぐみ' - ¿¿ ¿¿¿ + 林原 めぐみ Any pointers as to the cause of the remaining failure (which is an old problem[1]) would be appreciated. So we now have good results on SQLite, PostgreSQL, MySQL and Oracle, which I believ

Re: Python 3 port - all PostgreSQL tests now pass on 2.7.2 and 3.2.2 with the same codebase

end, I assumed it wouldn't matter, but apparently it does :-( Can anyone enlighten me as to what to do about this? Thanks & regards, Vinay Sajip [1] http://groups.google.com/group/django-developers/browse_thread/thread/15b710ba6912998d/63e9559398a13660 -- You received this messag

Re: Python 3 port - notes for people wanting to review changes/port apps

s if Pyramid is using the same approach. Perhaps the time is ripe to develop some special 2to2plus3 fixers ... Regards, Vinay Sajip -- 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

Python 3 port - notes for people wanting to review changes/port apps

/wiki/PortingNotesFor2To3 and I would welcome your comments - I'm sure I've missed a thing or two. I will update the page as things occur to me or in response to feedback about it. Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developer

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

od for 1.5, however, so hopefully we can merge soon > after the release of 1.4. Even then, I think 1.5 would be a "Python 3 > preview" i.e. we wouldn't promise the same level of support for Python 3 > as for Python 2.X. Sounds like a plan :-) Regards, Vinay Sajip -- Yo

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

the official documentation, but you might find my notes on the Wiki helpful: https://code.djangoproject.com/wiki/PortingNotesFor2To3 Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this g

Python 3 port - all PostgreSQL tests now pass on 2.7.2 and 3.2.2 with the same codebase

SQL backends. I suppose Oracle will be the next one to focus on: Ian Kelly was getting 17 failures and 24 errors on 7 Dec[2], but some changes have been committed since then. Is Oracle XE (Express Edition) a valid platform for Django's Oracle tests? Does anyone here have experience inst

Re: Python 3 port - all MySQL tests now pass on 2.6.7 and 3.2.2 with the same codebase

needing to set up a database backend like MySQL or PostgreSQL, is there any chance you could run those benchmarks (on the regression test runs under 2.x and 3.x) and post results? Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django devel

Re: Python 3 port - all MySQL tests now pass on 2.6.7 and 3.2.2 with the same codebase

similar pattern emerges on OSX. Regards, Vinay Sajip -- 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

Re: Adding Support for PyMySQL (for Python 3)

ght well be to do with my MySQL installation (stock 5.1.58 for Ubuntu 64-bit). It might be worth trying with my latest Django repo and my patched MySQLdb on your installation, if you have the time and inclination... BTW are you on IRC? If so, what nickname do you go by? Regards, Vinay Sajip --

Re: Adding Support for PyMySQL (for Python 3)

see where the Swedish collation it refers to comes from. Will continue to investigate ... Regards, Vinay Sajip -- 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 u

Re: Adding Support for PyMySQL (for Python 3)

ly true. Possibly I need to check the detail of where that value is used in the 2.x adapter and see what the 3.x adapter does in that area. Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this gr

Re: Adding Support for PyMySQL (for Python 3)

ion. Regards, Vinay Sajip -- 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...@goo

Re: Adding Support for PyMySQL (for Python 3)

at https://gist.github.com/1446201 - total run time was 9737 secs, BTW, but that is quite possibly down to differences between our machines. Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to thi

Re: Adding Support for PyMySQL (for Python 3)

e test suite is running now with the MySQLdb backend. I got some warnings for utf-8 bytestrings as fixtures were loaded, but it's run the first 275 or so tests without errors or failures so I'm going to let it run to see how far it gets. I will push my changes to the above repo soon.

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

failures and one error now -- I'll post back once those > are done, with a set of patches, hopefully. Great - thanks! Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send em

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

of your solution, then. > I've already pulled Ian Kelly's changes from his BitBucket repo. Which MySQL driver are you using for Python 3? I started looking at git://github.com/davispuh/MySQL-for-Python-3.git but it appears to expect queries formatted with {} rather than %s, so it doesn'

Re: Python 3 port - all tests now pass on 2.5.4, 2.6.2, 2.7.2 and 3.2.2 with the same codebase

that part about "upper" is probably right - it doesn't make sense to run "upper" on anything other than text. Part of it is just bugs in my conversion - if you look at some of the other test methods in the same test case, it appears that I applied b() in some places when

Re: Python 3 port - all tests now pass on 2.5.4, 2.6.2, 2.7.2 and 3.2.2 with the same codebase

been fast on OS X; something about the way it rolls back the database > between tests) I presume you've tried the advice given here: http://www.stereoplex.com/blog/speeding-up-django-unit-test-runs-with-mysql Regards, Vinay Sajip -- You received this message because you are subscribed to

Re: Python 3 port - all tests now pass on 2.5.4, 2.6.2, 2.7.2 and 3.2.2 with the same codebase

e.html) > I'm testing w/ trunk to get a baseline w/ psycopg2. I'll admit I'm using a > slow HDD, but I waited well over an hour. > > When I get back from work, I'll try psycopg2 and MySQL again tonight. Thanks for that, and for the useful feedback on the sqlite runs, too

Re: Python 3 port - all tests now pass on 2.5.4, 2.6.2, 2.7.2 and 3.2.2 with the same codebase

'egg:%s:%s' % (app, pkg_name)) > > then all (expected) tests pass. Thanks very much for this fix, I have applied it and tested in a venv, and can confirm your findings. I have pushed this to BitBucket. I have installed a PIL Python 3 port and bugs in that are causing 1 failure and 1 err

Re: Python 3 port - all tests now pass on 2.5.4, 2.6.2, 2.7.2 and 3.2.2 with the same codebase

ct that it's something to do with merging upstream changes into my port, but I haven't pinned it down. I pushed my changes this afternoon, so you could try pulling my changes and re-testing. Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Gr

Re: Python 3 port - all tests now pass on 2.5.4, 2.6.2, 2.7.2 and 3.2.2 with the same codebase

sts in 4871.121 seconds, which would mean an average of 4 seconds per test! The full suite of 4475 or so tests would then take almost five hours! I will try to test with psycopg2 on another machine, but that might not be possible for a while, so I'll have to rely on the good offices of others li

Re: Python 3 port - all tests now pass on 2.5.4, 2.6.2, 2.7.2 and 3.2.2 with the same codebase

in a VM, and have done no tuning other than fsync = off, so data from other testers might be more representative than my own. Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email

Re: Python 3 port - all tests now pass on 2.5.4, 2.6.2, 2.7.2 and 3.2.2 with the same codebase

don't think we should worry too much about the performance just yet, especially as Anssi is not apparently seeing the same kind of slowdown. Others can confirm or refute whether this slowdown is seen in their environments. Regards, Vinay Sajip -- You received this message because you are subs

Re: Python 3 port - all tests now pass on 2.5.4, 2.6.2, 2.7.2 and 3.2.2 with the same codebase

with fsync = off. All else set to default values. Time to investigate Jeremy's link to Frank Wiles' post ... Tests are running in a (64-bit) VM with 1GB RAM on a machine with 8GB physical RAM. Regards, Vinay Sajip -- You received this message because you are subscribed to the Google G

Re: Python 3 port - all tests now pass on 2.5.4, 2.6.2, 2.7.2 and 3.2.2 with the same codebase

On Dec 5, 12:14 pm, Anssi Kääriäinen wrote: > On 12/05/2011 01:41 PM, Vinay Sajip wrote: > > The test_ticket10432 should not generate any query at all. The tests in > django/db/models/sql/where.py should ensure that in the case of empty > __in condition the query will not be exec

Re: Python 3 port - all tests now pass on 2.5.4, 2.6.2, 2.7.2 and 3.2.2 with the same codebase

On Dec 5, 11:30 am, Florian Apolloner wrote: > > Use a tablespace which lies in a ram disk, you can't get any faster than > that I/O wise ;) I've seen posts telling how to do this, but I had hoped to avoid the need for it ... Regards, Vinay Sajip -- You received this

Re: Python 3 port - all tests now pass on 2.5.4, 2.6.2, 2.7.2 and 3.2.2 with the same codebase

On Dec 5, 12:57 am, Anssi Kääriäinen wrote: > > To speed up things, here are the tests that failed for me after the > fixes posted upthread: >  - cache >  - select_for_update >  - queries >  - admin_views > I've eliminated many of the errors here, but a few remain, at least some of which are rela

Re: Python 3 port - all tests now pass on 2.5.4, 2.6.2, 2.7.2 and 3.2.2 with the same codebase

On Dec 5, 1:16 am, Jeremy Dunck wrote: > > See also:http://www.revsys.com/writings/postgresql-performance.html > Thanks, I'll dig into that. Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" grou

Re: Python 3 port - all tests now pass on 2.5.4, 2.6.2, 2.7.2 and 3.2.2 with the same codebase

t;  - cache >  - select_for_update >  - queries >  - admin_views > > Although I ran out of patience, there might be more still. Well, thanks for that feedback. I'll run these selectively and see what's thrown up. Regards, Vinay Sajip -- You received this message because

Re: Python 3 port - all tests now pass on 2.5.4, 2.6.2, 2.7.2 and 3.2.2 with the same codebase

eed to set for a reasonable performance? I assumed the tests would use transactions by default, but I'm not sure if that's correct. Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this gr

Re: Python 3 port - all tests now pass on 2.5.4, 2.6.2, 2.7.2 and 3.2.2 with the same codebase

t is not iterable > > I don't know what to do to that. Replace *tuple(e) with *e.args (5 occurrences) and see how that works. Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this gro

Python 3 port - all tests now pass on 2.5.4, 2.6.2, 2.7.2 and 3.2.2 with the same codebase

3] to only get an exception object when actually needed (I missed a couple of cases). Regards, Vinay Sajip [1] https://bitbucket.org/vinay.sajip/django/ [2] https://gist.github.com/1412432 [3] http://groups.google.com/group/django-developers/msg/3f2dd22295ff1555 -- You received this message becaus

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

and the tests are running now on 2.5.4, 2.6.2, 2.7.2 and 3.2.2 :-) Regards, Vinay Sajip -- 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 fro

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

'foo' and order of dictionary keys in doctest output. Summaries follow. Python 2.5.4 == Ran 4490 tests in 481.852s FAILED (failures=1, skipped=91, expected failures=3) Python 2.6.2 == Ran 4490 tests in 449.179s OK (skipped=89, expected failures=3) Regards, Vinay

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

ges need to be made to django/utils/py3.py to accommodate this - it shouldn't be too much work, hopefully :-) Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

On Dec 3, 8:50 pm, Karen Tracey wrote: > On Fri, Dec 2, 2011 at 10:55 AM, Vinay Sajip wrote: > > > The Python 3 port now has all tests passing on 2.7.2 and 3.2.2 with > > the same codebase: > > What about Pythons 2.5 and 2.6? I've done nothing intentionally that prev

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

ack. I can't do any testing at the moment with an Oracle backend, unfortunately - but I can certainly look at test failures under 3.x which succeed under 2.x to try and eyeball fixes to problems. Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Gr

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

But don't all rush at once ;-) Regards, Vinay Sajip -- 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

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

is the area I am working on currently - working in a virtualenv with distribute and a PIL port installed. You can certainly try helping with a PostgreSQL backend, I believe py- postgresql can be used as a PostgreSQL driver under Python 3. Ian Kelly mentioned on this thread that he'll be look

Re: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

On Dec 2, 6:03 pm, Jacob Kaplan-Moss wrote: > > I'll try to spend the weekend writing/porting an app or two. If I can, > I'll let you know how it goes. That would be very useful feedback, thanks. Regards, Vinay Sajip -- You received this message because you are subsc

Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase

incorporates the very latest changes in Django SVN trunk (r17165). Regards, Vinay Sajip -- 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

Python3 port now applied to default branch, with promising progress

mirror at https://bitbucket.org/django/django - happy reviewing! Regards, Vinay Sajip -- 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

Re: I've made good progress in porting Django to Python 3, and could use some help!

On Nov 28, 7:14 pm, Vinay Sajip wrote: > suite is a boon in this regard. Though having worked through the > tests, it doesn't seem like the DRY principle is followed as much as > it could be ... for example, the same literals being used over and > over again in copy/paste f

Re: I've made good progress in porting Django to Python 3, and could use some help!

le, the same literals being used over and over again in copy/paste fashion, requiring patches in multiple locations to add u() and b() wrappers, for example. I didn't have time to rationalise this, as I was focused more on identifying and fixing failures and errors. Regards, Vinay Sajip -

Re: I've made good progress in porting Django to Python 3, and could use some help!

s are acceptable to the core devs. > Anyway, I'm trying to get into making the tests run and if I see some > result from my work, will try to figure out some sync between github and > bitbucket. Great, we'd like to see what you find. Regards, Vinay Sajip -- You receiv

Re: I've made good progress in porting Django to Python 3, and could use some help!

dling esp. in regexes is another area where closer inspection would be worthwhile. The test codebase contained a lot of Unicode literals (i.e. Unicode literals in the source code, which would have been encoded in UTF-8 in the files actually stored on disk) and I have converted these to use Unicode e

Re: I've made good progress in porting Django to Python 3, and could use some help!

/GitHub), compared to the real work still to be done in getting Django production-ready on 3.x. Regards, Vinay Sajip -- 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@googlegr

Re: I've made good progress in porting Django to Python 3, and could use some help!

Sorry the formatting of the post got mangled - not sure what happened there! Regards, Vinay Sajip -- 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 u

I've made good progress in porting Django to Python 3, and could use some help!

approached it just from the point of trying to get the tests to pass, and not (yet) focused on actually running realistic scenarios. Perhaps some of my fixes need changing - having other devs' eyeballs on the code can definitely help. Please let me have your comments! Regards, Vinay Sajip

Re: Logging configuration and handle_uncaught_exception

27;: 'django.utils.log.ConditionFilter', 'condition': not DEBUG, } This will allow the filter to be used in more places, e.g. you could use a more complex settings-time condition. Regards, Vinay Sajip -- You received this message because you are subscribed to the Go

Re: Logging configuration and handle_uncaught_exception

can then use in the logging configuration using something like 'require_debug_false': { '()': 'django.utils.log.ConditionFilter', 'condition': not DEBUG, } This will allow the filter to be used in more places, e.g. you could use a more complex sett

Re: Logging configuration and handle_uncaught_exception

configured to be as verbose (or not) as you like, independently of logging calls in the code. Regards, Vinay Sajip -- 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@googlegroup

Re: Problems with logging and Python 2.4

On Oct 6, 3:19 pm, Russell Keith-Magee wrote: > something to be said for Luke's position of encouraging people to get > away from older Python versions by withholding nice features :-) Amen to that! Regards, Vinay Sajip -- You received this message because you are subscribed to

Re: Problems with logging and Python 2.4

On Oct 6, 2:29 pm, Russell Keith-Magee wrote: > On Wed, Oct 6, 2010 at 9:23 PM, Vinay Sajip wrote: > > > On Oct 6, 11:53 am, Russell Keith-Magee > > wrote: > >> On Wed, Oct 6, 2010 at 6:46 PM, Luke Plant wrote: > >> > On Wed, 2010-10-06 at 12:24 +0800,

Re: Problems with logging and Python 2.4

#x27;django' logger. Regards, Vinay Sajip -- 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 django-devel

Re: #12012 Logging: Final call for comments

omponents/ libraries used. That's usually what you need for development, though sometimes you also have files fed by just one component (e.g. SQL queries) . For production, of course, you have e.g. email handlers for critical stuff as well, plus files just to catch errors, and so on. Regards, Vina

Re: #6735 -- Class based generic views: call for comment

iew instance from just randomly assigning to self.X, unless X were named in __slots__. Likewise, __setattr__ can be used to check for assignments to self. Of course, both might be capable of being subverted, but could be helpful in catching inadvertent mistakes. Regards, Vinay Sajip -- You r

Re: #12012 Logging: Final call for comments

nternally (not under a site developer's control) and the 'null' handler should be removed from the examples (as it won't be needed any more). That should make the configuration dictionary even simpler :-) Regards, Vinay Sajip -- You received this message because you are subs

Re: #12012 Logging: Final call for comments

use of the convention with LOGGING_CONFIG: the site developer is effectively telling Django to add those handlers, albeit in a declarative way. Hope that's clear! Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers"

Re: #6735 -- Class based generic views: call for comment

h as template names, output mimetype configuration etc. This would be quite safe, ISTM. For mutable state during request processing, I'd vote for sticking it all in the request. Then your method signatures need only include the request - not unreasonable - and if for some reason you couldn

Re: #6735 -- Class based generic views: call for comment

attr = x surely will? It seems better to stress thread-safety dos and don'ts in the documentation. Regards, Vinay Sajip -- 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...@

Re: #12012 Logging: Final call for comments

duce schema changes in future Python versions without breaking backwards compatibility. It's best to leave it in, it's just an extra line after all. Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" group. To

Re: #12012 Logging: request for comments

d-party code, the design of which you generally don't have much influence over. By and large, I think we're in agreement: I just think that thread- locals have their place, but must be used with care and under the guidance of experienced practitioners. Regards, Vinay Sajip -- You

Re: #12012 Logging: request for comments

tion, that would settle things right away :-) Even then, the answer would be to fix the hole in Python. Also - even if Django itself doesn't use thread-locals, can you be sure that any third-party library you are using doesn't do so under the covers? Regards, Vinay Sajip -- You received

Re: Proposal: modular django configuration

#x27;t understand what's "hardly a > stretch" neither from context nor from dictionary. "Hardly a stretch" == "Not exactly difficult" Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django develop

Re: Proposal: modular django configuration

a general principle, hardwired connections between specific databases and apps sounds broken to me, too. Regards, Vinay Sajip -- 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

Re: Logging in Django

our comment about avoiding the model loading race condition is > certainly a valid one, and that's probably enough to get me over the > line on the need for this signal. My only concern is whether there is > anything else that a "models_loaded" signal should be 'after

Re: www.djangoproject.com down?

27;s accessible now, but a lot slower than usual. Thanks for the response, sorry for the noise. Regards, Vinay Sajip -- 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...@googlegr

www.djangoproject.com down?

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 because you are subscribed to the Google Groups "Django developers" group. To post to this gr

Re: Logging in Django

and - that's a personal preference and there's no point in trying to sway anyone from their personal style preferences. But in terms of meeting the functional requirement (both logging configuration and the more general "do stuff on start-up once and once only") and bang for bu

Re: Logging in Django

h has the dictconfig code) on a machine running Ubuntu Dapper, with Python 2.4, as that's the minimum Python version requirement for Django now :-) Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post

  1   2   3   >