On Tuesday, 4 December 2012 14:25:22 UTC+10, Russell Keith-Magee wrote:
>
>
> Now, I'll completely grant that the same "private" interpretation doesn't
> apply to dictionary keys in the Python context, but:
>
> 1) From a Django template language perspective, there's no syntactic
> difference
On Tue, Dec 4, 2012 at 10:08 AM, Ryan Stuart wrote:
> Hi All,
>
> I recently discovered that there is no way in the Django template syntax
> to access all valid items of a dict. For example, as I understand it, it is
> impossible to access the only item of this dict:
>
>
вторник, 4 декабря 2012 г., 0:48:04 UTC+2 пользователь Ivan написал:
>
>
>1. Allows to use both, Django-ORM + SQLAlchemy. Single connection.
>SQLAlchemy's models are generated automatically form Django's models.
>https://github.com/Deepwalker/aldjemy
>
>
Sorry for bad link. This is
Hi All,
I recently discovered that there is no way in the Django template syntax to
access all valid items of a dict. For example, as I understand it, it is
impossible to access the only item of this dict:
my_dict = {"_key": "value"}
This is despite this dict being perfectly valid and not
Hi all,
I've viewed a few interesting solutions.
1. Allows to use both, Django-ORM + SQLAlchemy. Single connection.
SQLAlchemy's models are generated automatically form Django's models.
https://github.com/Deepwalker/aldjemy
2. Uses only Django's ORM, but allows to use 4 SQLBuilders
See also syntax evolution of peewee ORM, which initially was Django's
lightweight clone.
http://peewee.readthedocs.org/en/latest/peewee/upgrading.html#goals-for-the-new-api
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this
On Fri, Nov 30, 2012 at 7:04 PM, Harry Percival wrote:
> Hi Russell, thanks for getting back to us. Here's our info:
>
>
Hi Harry,
I've just posted those updates, and done the cleanups you suggested.
Yours,
Russ Magee %-)
--
You received this message because you are