On 7/17/06, Jyrki Pulliainen <[EMAIL PROTECTED]> wrote:
Anyway, Twill's been an ideal tool for web testing, because you cangive follow links, fill forms etc.Much like the unittest vs py.test vs nose discussion earlier, I think we should be avoiding discussions about what to bless as the 'official
2006/7/17, gabor <[EMAIL PROTECTED]>:
>
> Jeroen Ruigrok van der Werven wrote:
> > On 7/12/06, Julian 'Julik' Tarkhanov <[EMAIL PROTECTED]> wrote:
> >> This is handled by Unicode standard and is called transliteration.
> >
> >
> > Also, for Japanese, are you going to follow kunrei-shiki or rather
On 7/13/06, Malcolm Tredinnick <
[EMAIL PROTECTED]> wrote:I know Malcolm said he was going to step away from this discussion, so this is mostly for the benefit of everyone else.
Initially, I think it will be hard to have the views entirely divorcedfrom the model framework. To do that (separate the
On 7/17/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
>
>
> On 7/13/06, Simon Willison <[EMAIL PROTECTED]> wrote:
> >
> > The best way of running tests against a Django application, to my
> > mind, is to run a "fake" web server (i.e. one that doesn't actually
> > bind to a port) around the ap
Hi,
Am 17.07.2006 um 06:26 schrieb Russell Keith-Magee:
> On 7/13/06, Simon Willison <[EMAIL PROTECTED]> wrote:
> > The best way of running tests against a Django application, to my
> > mind, is to run a "fake" web server (i.e. one that doesn't actually
> > bind to a port) around the application
On 7/13/06, Simon Willison <[EMAIL PROTECTED]> wrote:
The best way of running tests against a Django application, to mymind, is to run a "fake" web server (i.e. one that doesn't actuallybind to a port) around the application.Agreed; although I'm not sure that you actually need to run a server in th
On 7/16/06, Bryan Kyle <[EMAIL PROTECTED]> wrote:
> This solution seemed to be only half a solution. While the solution
> will work for applications that only need to connect to one database at
> a time, it will not work for me where I need to have multiple
> connections (for multiple documents)
On 7/16/06, Bryan Kyle <[EMAIL PROTECTED]> wrote:
> This solution seemed to be only half a solution. While the solution
> will work for applications that only need to connect to one database at
> a time, it will not work for me where I need to have multiple
> connections (for multiple documents)
On 7/16/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> What does this add?
> ---
> (1) An "autoescape" template tag that turns automatic escaping on or off
> throughout its scope.
OK.
> (2) A "noescape" filter that marks its result as safe for use without
> further escaping
Hi All,
I'm interested in pulling the ORM out of Django so that I can use it in
a multi-document client application.
Since starting my search for information about modularizing the ORM
out, I came across Ticket 1321
(http://code.djangoproject.com/ticket/1321). Reading through the
ticket lead me
Hi,
I just recently found out that if you use the 'include' feature to
refer to a external URl config file the default parameter dict is
silently ingored, e.g.:
urlpatterns = patterns \
( ""
, ( r"^lce/guestbook", include ("lce_at.blog.urls"), dict
(weblog_slug = "guestbook"))
### t
On Sun, 2006-07-16 at 21:30 +0200, Michael Radziej wrote:
> Hi,
>
> I really appreciate your work, it goes all along my wishes--thanks a
> *lot*, Malcolm!
>
> I'll try to find some time in the next few days to test how my
> existing stuff would look using autoescape.
>
> I have looked in yo
On 7/16/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> As far as I can tell when you add USE_I18N = False in your settings.py
> it will result in the admin interface of the site to be stripped of
> atleast the datetime javascript helper.
Hi avansant,
I believe I fixed this a couple of days a
On Sun, 2006-07-16 at 23:31 +0200, [EMAIL PROTECTED] wrote:
> Hi django-developers,
>
> I had the need for a field type similar to USStateField: an
> OlympicNationField which takes 3 uppercase letters to the official olympic
> nation abbrevation.
>
> Maybe this is generic enough to go into dja
On 7/16/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hi django-developers,
>
> I had the need for a field type similar to USStateField: an
> OlympicNationField which takes 3 uppercase letters to the official olympic
> nation abbrevation.
I would feel better using ISO 3166-1 country codes
As far as I can tell when you add USE_I18N = False in your settings.py
it will result in the admin interface of the site to be stripped of
atleast the datetime javascript helper.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Goo
Hi,
Am 16.07.2006 um 23:53 schrieb Martina Oefelein:
> Hi Malcolm,
>
>> (3) Auto-escaping inherits down through template inclusions. That
>> is, if
>> you extend a template that has auto-escaping enabled, you get
>> auto-escaping enabled (obviously the autoescape template tag can
>> control
>> t
On Jul 16, 2006, at 5:53 PM, Martina Oefelein wrote:
>
>> (3) Auto-escaping inherits down through template inclusions. That
>> is, if
>> you extend a template that has auto-escaping enabled, you get
>> auto-escaping enabled (obviously the autoescape template tag can
>> control
>> this). Anybody h
Hi Malcolm,
> (3) Auto-escaping inherits down through template inclusions. That
> is, if
> you extend a template that has auto-escaping enabled, you get
> auto-escaping enabled (obviously the autoescape template tag can
> control
> this). Anybody have a strong reason not to do this?
>
Hi django-developers,
I had the need for a field type similar to USStateField: an OlympicNationField
which takes 3 uppercase letters to the official olympic nation abbrevation.
Maybe this is generic enough to go into django.db.models.fields ?
I attach my solution.
Regards,
Dirk
--
"Feel free
Note: I originally posted part of the following to the users list,
but I realized today that it's probably better posted here because it
deals with a potential bug and developer rationale behind some
generic view behavior that I find very odd. Sorry for the cross-post!
---
Using the latest
Hi,
I really appreciate your work, it goes all along my wishes--thanks a
*lot*, Malcolm!
I'll try to find some time in the next few days to test how my
existing stuff would look using autoescape.
I have looked in your patch only cursory, so my comments refer to the
general approach and no
Jeroen Ruigrok van der Werven wrote:
> On 7/12/06, Julian 'Julik' Tarkhanov <[EMAIL PROTECTED]> wrote:
>> This is handled by Unicode standard and is called transliteration.
>
>
> Also, for Japanese, are you going to follow kunrei-shiki or rather the
> more widely used hepburn transliteration? Or
Jeremy Dunck wrote:
> On 7/15/06, dan <[EMAIL PROTECTED]> wrote:
> >
> > I need to access MS SQL Server from our Linux host. Is there currently
> > a way to do this? If not, any idea how many hours it would take an
> > experienced programmer to add it? And what would be the best way? ODBC?
> > I l
On 7/16/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
> I have put an initial version of the auto-escaping patch I mentioned
> yesterday into ticket #2359. I'll briefly describe what it does below.
> The patch includes changes to the core and a test suite for the
> auto-escaping changes (whi
I have put an initial version of the auto-escaping patch I mentioned
yesterday into ticket #2359. I'll briefly describe what it does below.
The patch includes changes to the core and a test suite for the
auto-escaping changes (which is about half the patch).
My reason for posting this first pass
26 matches
Mail list logo
