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://groups.go

Re: Python 3 port status

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. To post to this group, send email to django

Re: Python 3 port status

]. 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://github.com/vsajip/django/issues/new

Re: json vs simplejson

.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').getvalue() 'a\x00b\x00c\x00' >>> Fun and games ... I'm not

Re: admin_changelist failing on Oracle

this case, the offending name is '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&

admin_changelist failing on Oracle

;ADMIN_CHANGELIST_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 suggest wh

Re: Python 3 port - now available on GitHub

and I 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 emai

Re: Python 3 port - now available on GitHub

o's version, which was 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 Goog

Re: Python 3 port - now available on GitHub

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 further findings there. Regards, Vinay Sajip [1] https://github.com/vsajip/django

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 subscribe

Re: GitHub migration done!

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 message because you are subscribed to

Re: GitHub migration done!

o see how it works (as time permits). Thanks and 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 e

Re: GitHub migration done!

low-maintenance, 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 d

Re: GitHub migration done!

the official BitBucket 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

Django use of stdlib HTMLParser "internals"

uld 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" g

Re: Errors in tests

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.djangoproject.com/ticket/18103 Regards, Vinay Sajip -- You received

Errors in tests

4:~/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 instance of django.template.context.RequestContext. I

Django and dictionary ordering

D: {'username': 'adrian', 'password1': 'secret', 'password2': 'secret'} - VALID: {'username': 'adrian', 'password2': 'secret', 'password1': 'secret'} + VALID: {'username': 'adrian', 'password1': 'secret', 'password2': 'secret'} There are no corresponding failures with Python 3.2. The Django 3.x branc

Python 3 port updated for 2.6 compatibility

nfigurations, 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-developers@googlegrou

Re: Proposal: drop Python 2.5 support in Django 1.5

as just an example. 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@goog

Re: Proposal: drop Python 2.5 support in Django 1.5

stem Python is 2.6.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 from this group, send email to django-develope

Re: Django 1.4 alpha on December 22nd

ept X as e:", and removal 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-dev

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 <aymeric.augus...@polytechnique.org> 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, Vi

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

r: '¿¿ ¿¿¿' != '林原 めぐみ' - ¿¿ ¿¿¿ + 林原 めぐみ 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 believe is all of the backends which ship with Django - have I missed a

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

ks as 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

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

/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 developers" grou

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

t; > The timing is very good 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 :-) Regard

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

out of the way. I know it's not 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" gr

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

ve experience installing it on Ubuntu 64- bit? I have an Oracle forum post[3] which gives the installation procedure, but it appears somewhat involved ... Regards, Vinay Sajip [1] http://groups.google.com/group/django-developers/t/ad4e980c8cde49f [2] http://groups.google.com/group/django-d

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

be runnable without 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

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

sting to see if a 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,

Re: Adding Support for PyMySQL (for Python 3)

hed Django - so it might 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?

Re: Adding Support for PyMySQL (for Python 3)

I can't 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@goog

Re: Adding Support for PyMySQL (for Python 3)

implicitly 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

Re: Adding Support for PyMySQL (for Python 3)

o with my MySQL configuration. 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-

Re: Adding Support for PyMySQL (for Python 3)

e further into these issues. Details 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&q

Re: Adding Support for PyMySQL (for Python 3)

the 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. Regards, Vinay Sajip

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

ilures 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 email to djang

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

ith {} rather than %s, so it doesn't seem that I can use it. 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 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

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 I sho

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

as never > 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

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

s/postgresql-performance.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 r

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

error; everything else passes. 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

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

I suspect 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 Groups

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

ely results. 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+unsubsc

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

ther 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 to django-developers@google

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

uld 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 subscribed to th

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

ffectively RAMdisk) and 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

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 <anssi.kaariai...@thl.fi> 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 > __i

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 <f.apollo...@gmail.com> 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 -

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

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 <jdu...@gmail.com> 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 "Djan

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

posted upthread: >  - 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 mes

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

or 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 group, send e

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

Error: 'IntegrityError' object 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

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

] 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 because you

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

patch in my branch, 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@googlegro

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

u'foo' vs. '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, Vi

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

somewhere else. So some changes 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, s

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 <kmtra...@gmail.com> wrote: > On Fri, Dec 2, 2011 at 10:55 AM, Vinay Sajip <vinay_sa...@yahoo.co.uk>wrote: > > > The Python 3 port now has all tests passing on 2.7.2 and 3.2.2 with > > the same codebase: > > What about Pyt

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

I look forward to the feedback. 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 th

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

/wishlist/2CJGJ3I4HEIK5 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, se

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

that he'll be looking at the Oracle backend. 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 em

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 <ja...@jacobian.org> 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

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

) This 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

://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 this group,

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 <vinay_sa...@yahoo.co.uk> 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 >

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

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 -- You received this message bec

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

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 received this message be

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

. 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 escapes, as this is more portable. Regards, Vinay Sajip -- You received this

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

hem (BitBucket/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@g

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!

unning 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 -- You received this message because you are subscribed to the Google Groups "Django developers"

Re: Logging configuration and handle_uncaught_exception

Filter', '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 Google Groups "Django developers" group. To post

Re: Logging configuration and handle_uncaught_exception

ndition which you 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 settings-time condition. Regards, Vinay Sajip -- You re

Re: Logging configuration and handle_uncaught_exception

ls on handlers can be 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

Re: Problems with logging and Python 2.4

On Oct 6, 3:19 pm, Russell Keith-Magee <russ...@keith-magee.com> 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

Re: Problems with logging and Python 2.4

On Oct 6, 2:29 pm, Russell Keith-Magee <russ...@keith-magee.com> wrote: > On Wed, Oct 6, 2010 at 9:23 PM, Vinay Sajip <vinay_sa...@yahoo.co.uk> wrote: > > > On Oct 6, 11:53 am, Russell Keith-Magee <russ...@keith-magee.com> > > wrote: > >> On Wed

Re: #12012 Logging: Final call for comments

pture events from all components/ 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

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

: it would prevent a user of a view 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. Reg

Re: #12012 Logging: Final call for comments

er needs to happen internally (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 subscr

Re: #12012 Logging: Final call for comments

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" group. To pos

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

's always thread locals for the requests (duck ;-)) 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

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

stance.container_attr.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 ema

Re: #12012 Logging: Final call for comments

e can introduce 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" gro

Re: #12012 Logging: request for comments

erally 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 received this message because you are subscribed t

Re: #12012 Logging: request for comments

mentation, 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 receive

Re: Proposal: modular django configuration

native speaker. Can'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 "

Re: Proposal: modular django configuration

uri's apps, but as 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

Re: Logging in Django

ern is whether there is > anything else that a "models_loaded" signal should be 'after'. If > we're going to introduce a "we've finished setup" signal, I want to > make sure that the place we emit it is a point at which we can > guarantee that we've actually fi

Re: www.djangoproject.com down?

s that explains it. It'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-de

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 group,

Re: Logging in Django

meeting the functional requirement (both logging configuration and the more general "do stuff on start-up once and once only") and bang for buck, what I've proposed is simpler, involves less code than a separate infrastructure of startup.py files, and provides for more advanced usag

Re: Logging in Django

pad branch (which 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" gro

Re: Logging in Django

en interspersed with everything else that writes to stderr - not ideal. 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 fr

Re: Logging in Django

modify their logging behaviour through this mechanism. 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, s

Re: Logging in Django

g (lifted from simon's > initial proposal). > Likewise in my Launchpad branch, though a little different in the details from Simon's, though the effect is much the same. Regards, Vinay Sajip -- You received this message because you are subscribed to the Google Groups "Django developers&q

Re: Logging in Django

lies that all the startup.py importing would be done in a separate loop after all the model loading is done - i.e. the equivalent of my POST_MODEL_CALLBACKS hook. If so, how could you hook into class_prepared, as per my example? Can you confirm that's the intention? Thanks for your feedback!

Re: DjangoCon.eu is on right now

uch simpler configuration is possible, and no doubt we'll come up with one as the recipe gets baked. As far as the IRC thing goes - I'll try to be around Thursday and Friday so that I can hook up with you on #django-sprint. Regards, Vinay Sajip -- You received this message because you are subscr

  1   2   3   >