Re: Proposing the removal of Oracle from the Django supported backend databases

On Thu, Aug 3, 2023 at 6:26 PM Paolo Melchiorre wrote: > Hi all, > I wanted to share the frustration of seeing yet another great new ORM > feature blocked due to Oracle compatibility: > https://github.com/django/django/pull/16417 > > In the past, I too have had to put a lot of effort trying to ma

Re: Supporting Oracle's renamed cx_Oracle driver in Django

On Tuesday, June 7, 2022 at 7:36:38 PM UTC+10 f.apo...@gmail.com wrote: > Hi Chris, > > On Tuesday, June 7, 2022 at 11:30:46 AM UTC+2 christopher@gmail.com > wrote: > >> The question is how to add support cleanly so that both names are >> supported in

Re: Supporting Oracle's renamed cx_Oracle driver in Django

> I agree with Florian, I'd prefer adding support for *python-oracledb* in Django 4.1 and immediately deprecate using *cx_Oracle *(will be removed in Django 5.0). That sounds fair. The cx_Oracle namespace won't have any substantive changes; maybe some new wheels for Python 3.11, and any critic

Supporting Oracle's renamed cx_Oracle driver in Django

A new, major Python cx_Oracle driver release is available and it comes with a brand new name: *python-oracledb* . At run time, the module name of the p

Reactive frontend using Django templates?

or several reasons. Are there any efforts to which I can contribute, with the goal of adding reactivity to client-side templates generated with the Django template language? Best regards, Brylie Christopher Oxley -- You received this message because you are subscribed to the Google Group

Prevent DateRangeField overlap in model?

Now that Django supports the DateRangeField, is there a 'Pythonic' way to prevent records from having overlapping date ranges? # Hypothetical use case One hypothetical use case would be a booking system, where you don't want people to book the same resource at the same time. # Hypothetical exam

Re: Improving Windows users experience at the command line

Regarding venv and bash, I filed a ticket [1] three years ago to have the bash script included with the Windows venv installation, and it looks like that change is in from 3.5 on. So in any case we shouldn't need to suggest virtualenv any more. Although I personally use bash, I definitely agree

Re: Default to BigAutoField

I really like this idea. We created a custom BigAutoField for our systems with sharded databases, and fast growing data. I understand the desire to fix it for new projects moving forward, but this smells a little like what happened with custom User models - it was introduced for new projects, b

Re: change commit message format to present tense?

If anyone's put off by the hectoring tone of the imperative mood, it might be better to think of it as the indicative mood. That is: (This will) "add password validation to prevent the usage of...". rather than (You must) "add password validation to prevent the usage of..."! In English they're

GitHub Issues for DEP repository?

Hello, With all the talk of DEPs flying around I thought I'd finally take a look at one in detail. I wanted to make a suggestion about it and realized that there wasn't really a good place to do so. The issue was too minor for a mailing list discussion, and there was no open pull request to co

Re: Django 1.9 - JSONField

Postgres' jsonb has some pretty unique features that I'm not sure any other databases are going to implement anytime soon, and even if they did, it would probably be in a fairly incompatible way, yeah? It would be nice to get this included into Django itself, and have it noted as a Postgres-only f

Re: Allow deferral of ModelSignal callback invocation until after transaction commit

o help on that if you guys need help. Pretty excited to get a post-commit hook into core in 1.9, no matter how that ends up happening. Best, Chris On Saturday, May 2, 2015 at 9:18:42 AM UTC-4, Shai Berger wrote: > > Hi, > > On Saturday 02 May 2015 07:20:00 Christopher Adams wrote:

Re: Allow deferral of ModelSignal callback invocation until after transaction commit

Hey guys, Thanks for the great feedback and replies. Generally agree with everyone that post-commit hooks shouldn't be strictly coupled to the signals framework philosophically speaking. I disagree with Carl's premise that using `connection.on_commit` in your signal handler is simpler than add

Re: Allow deferral of ModelSignal callback invocation until after transaction commit

Hey guys, Thanks for the great feedback and replies. Generally agree with everyone that post-commit hooks shouldn't be strictly coupled to the signals framework philosophically speaking. I disagree with Carl's premise that using `connection.on_commit` in your signal handler is simpler than add

Allow deferral of ModelSignal callback invocation until after transaction commit

So wrote an RFC and a prototype

Re: Unneeded index created with unique=True and db_index=False in TextField

This issue was the subject of https://code.djangoproject.com/ticket/24082. There, the accepted (but not implemented) solution is the same as suggested here: allowing the user to opt out of the creation of the additional index with `db_index=False`. On Wednesday, April 15, 2015 at 2:11:25 PM UTC

Re: [GSoC] Switching to Jinja2 proposal

n jinja2? or whats on our mind? If you > guide me with some direction then I might go for the ticket. looking > forward to hear from you. > > Regards > > On Sunday, March 23, 2014 at 5:24:05 PM UTC+6, Christopher Medrela wrote: >> >> On Sunday, March 23, 2014 11:51:06 A

SchemaEditor + DatabaseConnection

Hi All, I'm working on https://code.djangoproject.com/ticket/56 for the EuroPython sprint. There was a PR for it (https://github.com/django/django/pull/1156) but it was rejected by Tim Graham because the code should apparently be in the SchemaEditor instead of the DatabaseCreation class. As I

Re: [GSoC] Switching to Jinja2 proposal

On Sunday, March 23, 2014 11:51:06 AM UTC+1, Gwildor Sok wrote: > > So, there won't be a GSoC project for this, but it would be a shame to let > the lengthy discussion and momentum generated go to waste. Can a decision > on this matter be made and implemented regardless of the GSoC projects? > I

Re: [GSoC] Switching to Jinja2 proposal

Hello! I'm sorry for such long time without any feedback. Unfortunately, I'm not going to send Django proposal. My original plan was to send two proposals: one for Django and one for Breeze (Scala numerical processing library) but I lack time and I will focus on Breeze. Therefore, I won't have eno

Re: [GSoC] Switching to Jinja2 proposal

> > What kind of support do you except for third-party template tags? Suppose, > that > `cycle` tag is not builtin. Would it be acceptable to write sth like that: > > dtl cycle '1' '2' as rows > > It could be quite easily implemented as a Jinja2 extensions. Of course, I > guess > that you'd

Re: [GSoC] Switching to Jinja2 proposal

The link is here: http://pastebin.com/DWjE1axV It times only rendering -- templates are parsed and cached in the setup. On Tuesday, February 25, 2014 8:34:14 AM UTC+1, Curtis Maloney wrote: > > Did I miss the link to your benchmark code? > Does it time just rendering, or parsing also? > -- > Sen

Re: [GSoC] Switching to Jinja2 proposal

n speedup is in executing for loop (19x), not it's body. On Friday, February 21, 2014 11:07:30 PM UTC+1, Kevin Christopher Henry wrote: > > Hi Christopher, > > >> ... checks the template extension and dispatch to >> corresponding function from `django.dtl` or `ji

Re: [GSoC] Switching to Jinja2 proposal

Hi Christopher, > ... checks the template extension and dispatch to > corresponding function from `django.dtl` or `jinja2`. > The mechanism for distinguishing the two kinds of template needs to be more flexible. For example, let's say I want to override a third-party templat

Re: [GSoC] Switching to Jinja2 proposal

I'm sorry for such long time without any reply, but I was investigating possible approaches of mixing Django and Jinja2 templates. On Sunday, February 16, 2014 1:08:49 AM UTC+1, Russell Keith-Magee wrote: > > > On Sun, Feb 16, 2014 at 12:43 AM, Christopher Medrela > wrote: >

Re: [GSoC] Switching to Jinja2 proposal

ox means introducing dependencies. Are we ready for this? On Tuesday, February 11, 2014 2:07:19 PM UTC+1, Aymeric Augustin wrote: > > 2014-02-11 13:42 GMT+01:00 Christopher Medrela : > > >> What did Armin said about Python 3 exactly? > > > He wrote an extensive ar

Re: [GSoC] Switching to Jinja2 proposal

I'm really astonished how much feedback I got! On Sunday, February 9, 2014 1:11:19 AM UTC+1, Russell Keith-Magee wrote: > > On Sun, Feb 9, 2014 at 6:16 AM, Christopher Medrela > wrote: > >> Hello! GSoC 2014 is coming and I'm thinking about issue to work on. >>

Re: [GSoC] Switching to Jinja2 proposal

; Curtis > > > > On 9 February 2014 11:11, Russell Keith-Magee > > > wrote: > >> >> On Sun, Feb 9, 2014 at 6:16 AM, Christopher Medrela >> >> > wrote: >> >>> Hello! GSoC 2014 is coming and I'm thinking about issue to work on.

[GSoC] Switching to Jinja2 proposal

Hello! GSoC 2014 is coming and I'm thinking about issue to work on. The template system is one of the components that are of special interest to me. One of the major issues is that rendering templates is slow. The problem could be solved by compiling template to Python bytecode, but it seems to

Re: GSoC query

There is a list of ideas [1] and both improving aggregates and annotations as well as improving error messages are listed there, so I suppose these ideas are still open. Google doesn't allow you to submit your proposal before March 10, but the submission is only a formality and this doesn't me

Re: Renaming apps.has_app

+1 for "is_installed" I don't find the grammar objectionable here, just think of it as "is_(each one of these apps)_installed" On Sunday, January 5, 2014 3:50:45 PM UTC-6, Aymeric Augustin wrote: > > On 5 janv. 2014, at 22:38, Raffaele Salmaso > > > wrote: > > > Should it takes a list of app

TestCase can produce surprising failures

I recently upgraded one of my projects to 1.6 and was surprised to find that some of my tests were failing. I filed a ticket [1], and the subsequent discussion with Aymeric makes me think that there is a tricky issue here, worth discussing. The basic problem is that when using TestCase you can

Re: Proposal to end the war with flake8 warnings

I've used autopep8 to make some additional cleanup -- see this pull request: https://github.com/django/django/pull/1875 -- 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

Re: Django 1.6 and migrating to the new test runner: note on user experience

I was working at system check framework [1] during this holiday. I've done some changes that will solve all problems considered in this thread. Maybe I'm a careless kind of guy, but when I test out new versions of > Django, reading all of the release notes is rarely the first thing that > I do...

Re: Revert 165f44aa?

To summarize the possible approaches here: 1) Combine multiple with statements into one wherever possible. This seems to be the approach of the commit in question. 2) Group with statements based on whether they logically belong together, regardless of line length. This will involve backslashes,

Re: [GSoC] Revamping validation framework and merging django-secure once again

In order to get more attention, I've created a new thread [1]. [1] https://groups.google.com/forum/#!topic/django-developers/_sde4eoNRyQ -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emai

System check framework

Hello! This summer I'm a student of Google Summer of Code. I was working at introducing a new system check framework (merging django-secure was a part of my proposal, but I didn't manage to do it due to my time overestimation). The project is coming to the end and there is a pull request [1] tha

Re: [GSoC] Revamping validation framework and merging django-secure once again

> > 4. More important changes in code: >> >> - Introduced RAW_SETTINGS_MODULE [1]. I use it in compatibility checks to >>> test >> >> if `TEST_RUNNER` setting was overriden [2]. >> >> > > Have a look at the internals of the diffsettings management command -- I'm >> not sure RAW_SETTINGS_MODU

Re: [GSoC] Revamping validation framework and merging django-secure once again

> > > We probably cannot move checks of `primary_key` and `unique` living in > `FileField.__init__`. We test if one of these two parameters was passed; we > don't check their values. Consider that an user passes unique=False. This > is > the default value, but nevertheless, this should result in

Re: [GSoC] Revamping validation framework and merging django-secure once again

I've written four more tests. I've moved some of checks out of `__init__` methods. I've changed `tag` to `register`. I've rebased against master. I've improved documentation (added sections about filtering and silencing system checks), but I'm still polishing it. Code is ready for final review exce

Re: Order of INSTALLED_APPS

; Marc > On 1 Sep 2013 21:31, "Kevin Christopher Henry" > > > wrote: > >> Sorry to be late to this thread, I just came across it. >> >> There's another place where the order of INSTALLED_APPS matters: >> management commands. Management commands a

Re: [GSoC] Revamping validation framework and merging django-secure once again

1. Progress: I've made improvements to admin checks. I've also finished implementing filtering and silencing checks. I've rebased my branch against master again. 2. I'm afraid that there is too little time to merge django-secure. September 16 is suggested 'pencils down' date, so there are only le

Re: Order of INSTALLED_APPS

Sorry to be late to this thread, I just came across it. There's another place where the order of INSTALLED_APPS matters: management commands. Management commands associated with apps that come later in INSTALLED_APPS will replace those with the same name that are listed earlier. I can't find th

Re: [GSoC] Revamping validation framework and merging django-secure once again

1. One of my questions left unanswered on the pull request [1] (I mean this one about documentation and `__str__` use.). 2. I've finished rewriting admin checks. I've renamed `admin_validation` to `admin_checks`. I would like you to have a deep look at `fk_name` and `exclude` checks [2] as well a

Re: [GSoC] Revamping validation framework and merging django-secure once again

Progress: - Converted `BaseCommand.verbosity` from bytestring into an unicode. - Integrated compatibility checks. - Deprecated "validate" command. This command delegates to "check" command now. Changed "check" command -- it performs all system checks, including model validation and compatib

Re: [GSoC] Revamping validation framework and merging django-secure once again

*Progress.* - Deprecated `requires_model_validation` flag and `validate` method (both `BaseCommand` members) in favour of new `requires_system_checks` flag and `check` method. - Finished working at `contenttypes` tests. - Improved code thanks to Preston Holmes comments. Deleted dead code and

Re: [GSoC] Revamping validation framework and merging django-secure once again

I'm still working at polishing after reviewing. I've deprecated `requires_model_validation` and `validate`. I've started at adding tests for contenttype fields: `GenericForeignKey` and `GenericRelation`. I've updated gsoc2013-checks-review branch [1]. Now it's the same as gsoc2013-checks branch [2

Re: [GSoC] Revamping validation framework and merging django-secure once again

Unfortunately, I'm a bit late. I didn't suspected that polishing code after review takes so much time. Lots of my work from last Wednesday was small improvements, but there are some vital changes: The API will be consistent with API of logging module or message framework. Being consistent means th

Re: Avoid unbounded memory consumption when running `manage.py test`

Hi Matt, But I'm interested to know if others run into similar problems and how you > solve them. > We hit the same problem and used a similar tearDownClass solution http://chrisbailey.blogs.ilrt.org/2013/05/19/pythons-leaky-testcase-aka-hidden-gotchas-using-self/ Chris. -- You received this

Re: [GSoC] Revamping validation framework and merging django-secure once again

Progress: I've implemented registering entry points. Now there is `django.core.checks.register(callable)` function. There is no `run_in_development` and `run_in_production` arguments. I've also rewritten mechanism of triggering checking framework -- `BaseCommand.validate` calls `django.core.checks.

Re: [GSoC] Revamping validation framework and merging django-secure once again

I've created a pull request [1] to make deep review easier. I've rolled out tests we were talking about and reverted `validate_field` -- there exist both `check_field` and `validate_field`, the first calling the second. [1] https://github.com/django/django/pull/1364 -- You received this messag

Re: [GSoC] Revamping validation framework and merging django-secure once again

Progress: I've implemented manager checks. The schedule for the next 4 weeks is: 1. Manager checks (ref 4.1.7)(done)(0.5 week). 2. Entry point registering (ref 4.1.5) & rewriting mechanism of triggering checking framework (ref 4.1.9)(1.5 week). 3. Moving custom User model checks (ref 4.1.6)(0.

Re: [GSoC] Revamping validation framework and merging django-secure once again

Finally, I've rewritten all model and field tests and checks. Some new tests were written. First draft of checking framework documentation was written. All tests passes (at least at my computer). I've rebased my branch (`gsoc2013-checks` [1]) against master. The branch is ready to deep review. [1

Re: [GSoC] Revamping validation framework and merging django-secure once again

I'm finishing making field tests green. I'm a bit late, because the schedule says that I should finish this job by the end of the previous week. My excuse is that I had exams in the previous week so I couldn't focus on GSoC. Fortunately, I passed all exams and now I can work full time on GSoC and

Re: [GSoC] Revamping validation framework and merging django-secure once again

Hello! I've deleted old `gsoc2013-verification` branch. Follow the new `gsoc2013-checks` branch [1]. [1] https://github.com/chrismedrela/django/tree/gsoc2013-checks What did I do? I've rewritten field tests living in `django.tests.invalid_models` package [2], inside `tests.py` file [3]. I've ren

Re: [GSoC] Revamping validation framework and merging django-secure once again

ovices. I considered alternatives: "check" is too general and "static_check" as well as "static_validate" are too long. **Disabling/enabling parts of verification** > Hi Christopher, > > Overall, this looks like a great project and I look forward to the more

[GSoC] Revamping validation framework and merging django-secure once again

Hello! I'm really happy that I've been accepted as a Google Summer of Code student. I will work at revamping validation framework and merging django-secure this summer. I created this thread to start discussion (especially about public API) and get some feedback as well as to share progress. Any

Re: [GSoC 2013] Revamping validation functionality proposal

> > On Mon, Apr 29, 2013 at 6:25 AM, Christopher Medrela > wrote: > > Jacob, as you said, I deleted django-updates part, but I ended with a > > proposal taking only 9 weeks. Did you mean also scheduling more than 6 > weeks > > for the first part of the propo

Re: [GSoC 2013] Revamping validation functionality proposal

> > 2. I think your proposal is a bit too big. I'd general prefer to see a > less ambitious proposal with a high probability of success over a high > risk/high reward. I'd like to see you drop the "django-updates" part > of the proposal, and focus on validation and django-secure. If you end >

Re: [GSoC 2013] Revamping validation functionality proposal

Thank you for your feedback. I really appreciate every comment because that let me improve my proposal. 1. First of all, I noticed that the license of django-secure is copyright. Google forces us to release code under one of approved license [1], so a question to Carl Meyer: do you mind changin

[GSoC 2013] Revamping validation functionality proposal

y *4.2 Second half -- new features* - *Milestone 2.* (2 weeks) *django-secure*. One week for writing tests and documentation and one for implementation. - *Milestone 3.* (3 weeks) *django-update*. Updating list of problems which may be predicted after upgrading Django, tests and d

Re: Ticket #17093 -- quarantine global state in django.template

Hello, I made all tests green finally (all commits are tested under Python 2.7.3 and 3.2.3). The problem that took a few days to solve was that the default engine should be recomputed after changing TEMPLATE_LOADERS setting since its _template_source_loaders internal needs to be recalculated. I

Re: Ticket #17093 -- quarantine global state in django.template

Hello. I would like to report progress of my work (not too much new things, rather cleaning and polishing), discuss some issues and propose an idea for next Google Summer Of Code. Progres from last time: - Solved problem with TemplateResponse -- it receives optional keyword argument call

Re: Ticket #17093 -- quarantine global state in django.template

Hello. I'm really astonished how fast I get feedback and I really appreciate that. I apologize that you had to wait for my reply so long, but I cannot push myself to stop programming and to share results. :) I did some progress since creating this topic: - Almost all tests doesn't rely on th

Ticket #17093 -- quarantine global state in django.template

Hello everybody. 1. I'm working on ticket #17093 [1]. You can see progress of work at github [2]. It's about rewritting django.template so it won't use global state. I wrote this post to tell you what I did so far, what issues I deal with and to discuss them. I hope that we will gain valuable

Ticket 18685

hanks! Christopher -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/-R05yw7x4NcJ. To post to this group, send email to django-developers@googl

Re: post messages to facebook wall

Hello, 2011/1/10 trương thế linh : > Hi every body, > I'm a newbie to django. > please suggest me an app to intergrate with django to do allow me to > post messages to facebook wall. This is the mainlinglist for the Django-Developers. If you have questions about django, please look at the django-

Re: Does anyone know how to create a Django installer for Installatron?

This is the Django Mailinglist for Developers, for Questions about using Django please ask at Django Users Am 05.01.2011 17:20 schrieb "Martijn" : Does anyone know how to create a Django installer for Installatron? I've two cheap providers and they both use Installatron. It would be great to star

Re: Pluggable encryption for django auth (design proposal)

On Tue, Nov 30, 2010 at 4:22 AM, Tom Evans wrote: > First comment is that Django already has a pluggable authentication > stack, which already allows for this - simply define a new auth > backend that tests the password in the manner you wish. My understanding of the pluggable authentication sys

Spam attack on the Wiki

Just an FYI, but there's been hundreds of edits to add spam links in the last few hours. Might be worth locking it and rewinding the database. Chris -- | Chris Petrilli | petri...@amber.org -- You received this message because you are subscribed to the Google Groups "Django developers" group.

Re: Django's testing infrastructure

I can toss in a Core i7 w/12GB for testing as well, if someone can give me the VMs in either VirtualBox or Linux KVM format. I think this is a brilliant idea, and would even be willing to contribute some money to cover EC2/etc, if that's what it takes. Chris On Fri, Feb 26, 2010 at 11:49 AM, Stev

Re: DB optimization docs

Luke, I wonder if it's the right place, but one thing I have noticed most people don't realize is that they need to run something to do pooling between Django and the DB. I run pgpool, even when there is only one of each since it does the connection pooling for you. This can be a HUGE win in many

Re: Nipping projects in the butt

if it offended anyone, I'll retract the projects->HPV analogy :) Christopher Allan Webber <[EMAIL PROTECTED]> writes: > So, by now the primary problem with Django is not the lack of good > applications. There are tons of good applications. The primary problem > is that almos

Nipping projects in the butt

So, by now the primary problem with Django is not the lack of good applications. There are tons of good applications. The primary problem is that almost none of them work together. There are a few reasons for this... some of it has to do with templating, some of it has to do with people not usi

Re: Rethinking silent failures in templates

I'm just going to chime in here that a lot of our older apps at our work use Zope Page Templates. Largely we've found ZPT pages to be less pleaseant in all regards *excepting* the fact that they never, ever silently fail. Just as your code fails when there's a problem, so do your templates. It'

Re: Allow bypassing validation in newforms (#5153)

Am 17.09.2007 um 04:17 schrieb Malcolm Tredinnick: > On Mon, 2007-09-17 at 00:23 +0200, Christopher Lenz wrote: >> Hey all, >> >> I've created a ticket which has been closed as wontfix, and was told >> to bring it here. So here I am. >> >><htt

Allow bypassing validation in newforms (#5153)

gt; I personally think it'd be a good idea to apply. Thanks, Chris -- Christopher Lenz cmlenz at gmx.de http://www.cmlenz.net/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers&

Re: Django, Components, and Interfaces

Am 07.09.2007 um 21:07 schrieb Christopher Lenz: > Am 07.09.2007 um 20:40 schrieb Yuri Baburov: >>> Or if I'm using Satchmo and I've written an excellent CRM system >>> in Django, >>> I want Satchmo to use the shipping and contact information that >&

Re: Django, Components, and Interfaces

a design against uninformed comments; I'm also not saying that the design is in anyway perfect; there's definitely room for improvement). Cheers, Chris -- Christopher Lenz cmlenz at gmx.de http://www.cmlenz.net/ --~--~-~--~~~---~--~~ You re

Re: A question about manage.py validation

le reluctant, but I don't have enough > experience with memory optimization to counter your reasoning. It > seems cleaner to me to have these done in each Field's __init__, but > that would indeed force that to happen every time the server starts, > regardless of development

[ANN] Babel/Django integration

ing me on #python-babel on freenode, or the Babel mailing list. Oh, and kudos to Ramiro Morales and Massimo Scamarcia for contributing the middleware and extraction code! Cheers, Chris -- Christopher Lenz cmlenz at gmx.de http://www.cmlenz.net/ --~--~-~--~~~---~

Re: Shouldn't _ be ugettext instead of gettext?

ers: > > _('some message: %s').someModel.name > > Shouldn't _ better evaluate to ugettext? See also <http://code.djangoproject.com/ticket/5056> (I still don't see why you'd ever want the bytestring variants of gettext, but don't want to waste any more ti

Re: Ned Batchelder's hyphenate

on aren't even web applications, so including the functionality in Django would be rather inconvenient for those. And doing this stuff as a separate project does not in any way preclude using it in a Django app. Just my 2 cents. Cheers, Chris -- Christopher

Improperly Configured

I have no idea what has gone wrong but here is what I have. Python 2.5 Django (latest from SVN) Psycopg 2.0.5.1 (for Python 2.5) PostgreSQL 8.2 Windows XP Professional I am trying to run Manage.py syncdb and keep getting: django.core.exceptions.ImproperlyConfigured: Error loading psycopg module:

Re: Django site: Trac e-mails not including comments

m various projects that use 0.10 are working rather nicely, so I'd be surprised if this was an actual bug in Trac. Cheers, Chris -- Christopher Lenz cmlenz at gmx.de http://www.cmlenz.net/ --~--~-~--~~~---~--~~ You received this message because you are

Re: ANN: Django's Trac installation has been upgraded

acInterfaceCustomization> Cheers, Chris -- Christopher Lenz cmlenz at gmx.de http://www.cmlenz.net/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group

Re: Ticket spam

Am 27.10.2006 um 00:35 schrieb Christopher Lenz: > FYI: Akismet has been having a really high rate of false positive > lately, we've seen the same problems with it at trac.edgewall.org. > I've filed a support request but haven't heard back. > > Anyway, this

Re: Ticket spam

Am 25.10.2006 um 17:22 schrieb Christopher Lenz: > Am 25.10.2006 um 11:24 schrieb Michael Radziej: >> Adrian Holovaty schrieb: >>>> Also, I've been mulling over the idea of requiring an account >>>> signup >>> in order to post tickets and comments.

Re: DecimalField

of DecimalField would require the decimal.py module, same as ImageField requires PIL. Cheers, Chris -- Christopher Lenz cmlenz at gmx.de http://www.cmlenz.net/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups

Re: Ticket spam

e plug) and add stuff to BadContent in a more timely manner. The SpamFilter plugin has optional IP-blacklisting which can help reduce many kinds of spam, too. I have no idea whether that's enabled on code.djangoproject.com. BTW, is the Akismet filter disabled now? Hope that helps

Re: Integrating Django and SQLAlchemy

he documentation gets harder. It's definitely a good idea to develop SQLAlchemy support as an optional alternative to the built-in ORM for now. But if the project works out, replacing the built-in DB code with SQLAlchemy is going to make a *lot* of sense IMO. Chee

Re: [Fw]The Python Web Framework

Am 22.08.2006 um 21:49 schrieb Christopher Lenz: > Am 22.08.2006 um 18:22 schrieb James Bennett: >> Some things that occur to me on other points: >> >> * Admin, auth and comments using Django's own ORM, template system, >> etc.: well... what are we supposed to use

Re: [Fw]The Python Web Framework

rovide a full > settings file[1]. Or did I misunderstand that? That change improved the situation, but you still need the "from django.conf import settings; settings.configure(...)" before *importing* any other part of Django. That improves the situation, but doesn't fee

Re: [Fw]The Python Web Framework

rovide a full > settings file[1]. Or did I misunderstand that? That change improved the situation, but you still need the "from django.conf import settings; settings.configure(...)" before using any other part of Django. That works, but still doesn't feel clean. > * Esc

Re: "allow tags" attribute. stays/vanishes? :)

set [3358]. Thanks for the reminder! You may want to manually escape the first_name/last_name in that example ;-) Cheers, Chris -- Christopher Lenz cmlenz at gmx.de http://www.cmlenz.net/ --~--~-~--~~~---~--~~ You received this message because you are subscr

Re: Proposal: default escaping

t the Django template engine being output-type agnostic is a problem in this context. But then again, I'm not happy with Django templating in general, so I'll just shut up now :-P Cheers, Chris -- Christopher Lenz cmlenz at gmx.de http://www.cmlenz.net/ --~--~-~--~---

Re: More specific CSS rules for the admin

solution. > Also, nothing should be preventing you from copying the admin styles > and modifying them to be specific to your own needs. Sure, but that'll leave me with merging headaches when I want to upgrade Django and the style-sheets have been modified :-P Cheers, Chris -- Christ

Re: More specific CSS rules for the admin

s, widgets etc? Then I could simply drop the reference to the layout style sheet from the base.html template, but still keep the other stuff. Or is that already possible with your recent changes? Thanks, Chris -- Christopher Lenz cmlenz at gmx.de http://www.cmlenz.net/ --~--~---

Re: More specific CSS rules for the admin

min style sheets use "p" as a selector, and not ".django-admin p". Thus, the admin styles also affect stuff outside the admin itself, which was exactly my point. Cheers, Chris -- Christopher Lenz cmlenz at gmx.de http://www.cmlenz.net/ --~--~-~--~~~-

More specific CSS rules for the admin

e, "#admin-content" instead of "#content"). Those changes would make it a lot simpler to embed the admin app in an existing layout. Thanks, Chris -- Christopher Lenz cmlenz at gmx.de http://www.cmlenz.net/ --~--~-~--~~~---~--~~ You received

  1   2   >