On Tue, May 6, 2008 at 10:45 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
>
> On Tue, May 6, 2008 at 8:21 PM, Waylan Limberg <[EMAIL PROTECTED]> wrote:
> >
> > Yeah, we probably should mention this in the docs, along with an
> > explanation of how to enable Markdown's safe_mode. Sure, it's
>
Sort of, although I'm going to go against Adrian on the hide() method (I'd
rather be explicit than implicit).
On Tue, May 6, 2008 at 8:46 PM, Russell Keith-Magee <[EMAIL PROTECTED]>
wrote:
>
> On Wed, May 7, 2008 at 11:35 AM, David Cramer <[EMAIL PROTECTED]> wrote:
> >
> > I'd like to present
On Wed, May 7, 2008 at 11:35 AM, David Cramer <[EMAIL PROTECTED]> wrote:
>
> I'd like to present my concept for partial models, which would be an
...
> When the proxy is instanced, we would identify which fields are
> currently available, and map those in. We would also similarly make
> sure
I'd like to present my concept for partial models, which would be an
attempt to replace the use of .values() returning a dictionary
(although .values() still has uses if you dont actually want an
instance). Keep in mind, the way I'm presenting this would keep #17
working :)
values, values_tuple,
On Tue, May 6, 2008 at 8:21 PM, Waylan Limberg <[EMAIL PROTECTED]> wrote:
>
> On Tue, May 6, 2008 at 7:30 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> >
> >
>
> > I think there should be a branch checking the markdown version, and
> > passing in a unicode object if markdown.version_info
On Tue, May 6, 2008 at 7:30 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
>
>
> I think there should be a branch checking the markdown version, and
> passing in a unicode object if markdown.version_info >= (1,7,0,'').
Um, what about lines 71-74 [1] does not do this? Yeah the check is the
other
Here is the patch i was talking about:
http://code.djangoproject.com/ticket/5309
On Apr 28, 5:02 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Mon, 2008-04-28 at 13:49 +0200, David Danier wrote:
> > > For this particular case it saves a whole line. One concern I have is
> > > that if
On Tue, May 6, 2008 at 6:30 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> Markdown 1.7, released February 17, 2008, has a backwards-incompatible change.
>
> "
> Additionally, the encoding argument has been removed from both
> markdown and Markdown. Markdown expects unicode (or ascii) input and
Markdown 1.7, released February 17, 2008, has a backwards-incompatible change.
"
Additionally, the encoding argument has been removed from both
markdown and Markdown. Markdown expects unicode (or ascii) input and
it is the users responsibility to ensure that's what is provided.
"
The current
No. Not `tests.py`, but `tests` module - that can be a package of many
other modules/files
On May 7, 12:21 am, Steve <[EMAIL PROTECTED]> wrote:
> Hi, we're just getting started using Django unit tests, and it looks
> like the documentation says you can only have unit tests in two files:
>
Hi,
you can always define your own test runner which will look not only in
tests and models, but in every module.
This question is more suited for the django-users mailing list, this
list is intended for discussing development of django internals.
On Tue, May 6, 2008 at 10:21 PM, Steve <[EMAIL
Hi, we're just getting started using Django unit tests, and it looks
like the documentation says you can only have unit tests in two files:
models.py and tests.py. We would prefer to put our unit tests in many
different files, with, say, each main-line .py file having a
corresponding unit-test
I am using FB 2 and am planning on going on to 2.1.
Any overly complex queries I will probably hand code, as I am pretty
familiar with pleasing FB's optimizer.
This project won't be ready for production for some time, probably going to
wait for Django to go 1.0 first anyway.
Thanks for all your
13 matches
Mail list logo
