$$$$$$$$www.200836.com tell you Beijing/peking2008 Summer Olympic Games Briefing on the relocation project for Olympic venues

[200836]

$www.200836.com--- why we buy Peking 2008 Olympic Games―
souvenirs
1  low price
2  best quality-- licensed products by Peking Organizing Committee
3   many products to choose
4 most precious―limited circulation
5，we accept all payment methods,such as paypal,credit card,
telegraphic transfers. (T/T), western union ,Moneygram,visa-
card,master-card,moneybooker,ukash,enets,mydebit or face to face cash
transactions
if you want to know any information about 2008 beijing Olympic
games ,please contact me or visit :
my website--www.200836.com
MSN:[EMAIL PROTECTED]
e-mail:[EMAIL PROTECTED]
yahooID:feiallen
Skype:a200836
ICQ:391836515
or leave your e-mail or msn-number or other contact methods
we can e-mail our souvenirs-list to you



--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Adding a relative option to FilePathField

[Graham Carlyle]

I'd like to request that FilePathField should have an extra option that
causes it to only save a relative path (to the path parameter), say
called "relative". 

Having an absolute path stored makes it harder to move data between
machines that are set up differently (say development and production).
In this circumstance I would typically set the path parameter from the
settings file.

The "relative" argument could default to False to keep the current
behaviour by default. Actually i can't think when you would want
absolute paths but maybe someone does.

Shall I create a ticket (and possibly a patch) for this? or am I missing
something?

cheers,
Graham


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Adding a relative option to FilePathField

[Justin Lilly]

What would stop you from doing something akin to:
upload = model.FilePathField(path=RELATIVE_FIELD, match="foo.*",
recursive=True)

where RELATIVE_FIELD is defined in your settings.py file? Perhaps I've
missed the mark on this.. I'm relatively new to django-dev discussions.

-justin



On Fri, Feb 22, 2008 at 6:16 AM, Graham Carlyle <
[EMAIL PROTECTED]> wrote:

>
> I'd like to request that FilePathField should have an extra option that
> causes it to only save a relative path (to the path parameter), say
> called "relative".
>
> Having an absolute path stored makes it harder to move data between
> machines that are set up differently (say development and production).
> In this circumstance I would typically set the path parameter from the
> settings file.
>
> The "relative" argument could default to False to keep the current
> behaviour by default. Actually i can't think when you would want
> absolute paths but maybe someone does.
>
> Shall I create a ticket (and possibly a patch) for this? or am I missing
> something?
>
> cheers,
> Graham
>
>
> >
>


-- 
Justin Lilly
Web Developer

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Adding a relative option to FilePathField

[Graham Carlyle]

In your example I think RELATIVE_FIELD would be relative to the django
python process's current working directory which seems a bit arbitrary.
Having an absolute path parameter seems a good thing, but storing this
prefix for each record seems redundant and inflexible.

Graham

On Fri, 2008-02-22 at 09:05 -0500, Justin Lilly wrote:
> What would stop you from doing something akin to:
> 
> 
> upload = model.FilePathField(path=RELATIVE_FIELD, match="foo.*",
> recursive=True)
> 
> 
> where RELATIVE_FIELD is defined in your settings.py file? Perhaps I've
> missed the mark on this.. I'm relatively new to django-dev
> discussions.
> 
> 
> -justin
> 
> 
> 
> 
> On Fri, Feb 22, 2008 at 6:16 AM, Graham Carlyle
> <[EMAIL PROTECTED]> wrote:
> 
> I'd like to request that FilePathField should have an extra
> option that
> causes it to only save a relative path (to the path
> parameter), say
> called "relative".
> 
> Having an absolute path stored makes it harder to move data
> between
> machines that are set up differently (say development and
> production).
> In this circumstance I would typically set the path parameter
> from the
> settings file.
> 
> The "relative" argument could default to False to keep the
> current
> behaviour by default. Actually i can't think when you would
> want
> absolute paths but maybe someone does.
> 
> Shall I create a ticket (and possibly a patch) for this? or am
> I missing
> something?
> 
> cheers,
> Graham
> 
> 
> 
> 
> 
> 
> -- 
> Justin Lilly
> Web Developer
> 
> > 


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Adding a relative option to FilePathField

[Justin Lilly]

I would personally vote on making it an optional parameter if RELATIVE_FIELD
(or something like that) is present. If it isn't present, require it just
like always.
-justin

On Fri, Feb 22, 2008 at 9:46 AM, Graham Carlyle <
[EMAIL PROTECTED]> wrote:

>
> In your example I think RELATIVE_FIELD would be relative to the django
> python process's current working directory which seems a bit arbitrary.
> Having an absolute path parameter seems a good thing, but storing this
> prefix for each record seems redundant and inflexible.
>
> Graham
>
> On Fri, 2008-02-22 at 09:05 -0500, Justin Lilly wrote:
> > What would stop you from doing something akin to:
> >
> >
> > upload = model.FilePathField(path=RELATIVE_FIELD, match="foo.*",
> > recursive=True)
> >
> >
> > where RELATIVE_FIELD is defined in your settings.py file? Perhaps I've
> > missed the mark on this.. I'm relatively new to django-dev
> > discussions.
> >
> >
> > -justin
> >
> >
> >
> >
> > On Fri, Feb 22, 2008 at 6:16 AM, Graham Carlyle
> > <[EMAIL PROTECTED]> wrote:
> >
> > I'd like to request that FilePathField should have an extra
> > option that
> > causes it to only save a relative path (to the path
> > parameter), say
> > called "relative".
> >
> > Having an absolute path stored makes it harder to move data
> > between
> > machines that are set up differently (say development and
> > production).
> > In this circumstance I would typically set the path parameter
> > from the
> > settings file.
> >
> > The "relative" argument could default to False to keep the
> > current
> > behaviour by default. Actually i can't think when you would
> > want
> > absolute paths but maybe someone does.
> >
> > Shall I create a ticket (and possibly a patch) for this? or am
> > I missing
> > something?
> >
> > cheers,
> > Graham
> >
> >
> >
> >
> >
> >
> > --
> > Justin Lilly
> > Web Developer
> >
> > >
>
>
> >
>


-- 
Justin Lilly
Web Developer

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Hi Friend.........Tips 4u

[raja vathani]

   Interior Design Ideas Episode 

Hi friends here u learn about interior design and how to make in AutoCAD u
want any details please comments have a nice day enjoy and Learn

This site provides great tutorials / lessons for the student of
AutoCAD.
These lessons are designed to be as compatible with as many versions of AutoCAD
as possible. They are based on AutoCAD
2007, but can be easily adapted to other
versions. The lesson format was used in my CAD classes I have been teaching
previously. Any feedback would be used to make these as useful as possible.
Please note that these lessons are for private, individual use as well as
public schools.


AutoCAD Training - 2007 

   - AutoCAD Shortcut
Keys
   - start creating
drawings
   - Drawing & Editing Design
Geometry
   - Creating & Using
Layers
   - Creating & Placing
Blocks
   - Inserting Blocks From One
Drawing
   - Creating Dimensions &
Dimension
   - Scaling & Overriding
Dimensions
   - Dimensioning Smarter with
Associative
   - Plot Drawings to
Scale
   - Creating Plot Style
Tables
   - Creating 3D
Architectural
   - 3D Geometry into 2D Geometry
Edit
   - Creating 3D Doors and
Windows
   - Creating Lights,
Cameras


AutoCad 2005 For Architects Training 1-10

   - Introduction A
   - Introduction
B
   - Architectural
Visualization
   - Architectural
Film
   - Drawing and Scale
Ffactor
   - Externally Referenced
Files
   - Plotting Monochrome
Drawing
   - Plotting Color
Drawing
   - Creating Presentation
Drawings
   - Plotting Eps
File



 Training 11 - 20

   - Introducing
Llustrator
   - Intoducing
Photoshop
   - Defining Blocks and
Wblocks
   - Cut and Paste
Options
   - Introduction to Design
Center
   - Introduction to Tool
Palettes
   - External Reference
Defining
   - Insert Xref
   - Xclip Command -
pt1
   - Xclip Command -
pt2



 Training 21- 30

   - Xref Manager
   - Use External
References

Don't Miss It ................

[raja vathani]

Adobe photoshop cs3  [image: Adobe
photoshop cs3]


Foreground 
Lighting
mprove
your portraits with this easy and effective foreground lighting
effect.In
this Photoshop tutorial, you will learn how to darken the background
to
create a less-busy background. This effect may seem simple, but it works
exceptionally well for portraits with a busy background.


Step 1: Open a portrait photo

First, open an image of a portrait with a busy background that you would
like to apply this effect to. This effect will make the background darker to
add focus to the subject.


MORE> 

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Adding a relative option to FilePathField

[[EMAIL PROTECTED]]

I agree with Graham because you don't know where python will be
executed from what would the path be relative to?

On Feb 22, 9:33 am, "Justin Lilly" <[EMAIL PROTECTED]> wrote:
> I would personally vote on making it an optional parameter if RELATIVE_FIELD
> (or something like that) is present. If it isn't present, require it just
> like always.
> -justin
>
> On Fri, Feb 22, 2008 at 9:46 AM, Graham Carlyle <
>
>
>
> [EMAIL PROTECTED]> wrote:
>
> > In your example I think RELATIVE_FIELD would be relative to the django
> > python process's current working directory which seems a bit arbitrary.
> > Having an absolute path parameter seems a good thing, but storing this
> > prefix for each record seems redundant and inflexible.
>
> > Graham
>
> > On Fri, 2008-02-22 at 09:05 -0500, Justin Lilly wrote:
> > > What would stop you from doing something akin to:
>
> > > upload = model.FilePathField(path=RELATIVE_FIELD, match="foo.*",
> > > recursive=True)
>
> > > where RELATIVE_FIELD is defined in your settings.py file? Perhaps I've
> > > missed the mark on this.. I'm relatively new to django-dev
> > > discussions.
>
> > > -justin
>
> > > On Fri, Feb 22, 2008 at 6:16 AM, Graham Carlyle
> > > <[EMAIL PROTECTED]> wrote:
>
> > > I'd like to request that FilePathField should have an extra
> > > option that
> > > causes it to only save a relative path (to the path
> > > parameter), say
> > > called "relative".
>
> > > Having an absolute path stored makes it harder to move data
> > > between
> > > machines that are set up differently (say development and
> > > production).
> > > In this circumstance I would typically set the path parameter
> > > from the
> > > settings file.
>
> > > The "relative" argument could default to False to keep the
> > > current
> > > behaviour by default. Actually i can't think when you would
> > > want
> > > absolute paths but maybe someone does.
>
> > > Shall I create a ticket (and possibly a patch) for this? or am
> > > I missing
> > > something?
>
> > > cheers,
> > > Graham
>
> > > --
> > > Justin Lilly
> > > Web Developer
>
> --
> Justin Lilly
> Web Developer
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Adding a relative option to FilePathField

[Justin Lilly]

Fair enough. Forget I mentioned it :-/

On Fri, Feb 22, 2008 at 1:20 PM, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:

>
> I agree with Graham because you don't know where python will be
> executed from what would the path be relative to?
>
> On Feb 22, 9:33 am, "Justin Lilly" <[EMAIL PROTECTED]> wrote:
> > I would personally vote on making it an optional parameter if
> RELATIVE_FIELD
> > (or something like that) is present. If it isn't present, require it
> just
> > like always.
> > -justin
> >
> > On Fri, Feb 22, 2008 at 9:46 AM, Graham Carlyle <
> >
> >
> >
> > [EMAIL PROTECTED]> wrote:
> >
> > > In your example I think RELATIVE_FIELD would be relative to the django
> > > python process's current working directory which seems a bit
> arbitrary.
> > > Having an absolute path parameter seems a good thing, but storing this
> > > prefix for each record seems redundant and inflexible.
> >
> > > Graham
> >
> > > On Fri, 2008-02-22 at 09:05 -0500, Justin Lilly wrote:
> > > > What would stop you from doing something akin to:
> >
> > > > upload = model.FilePathField(path=RELATIVE_FIELD, match="foo.*",
> > > > recursive=True)
> >
> > > > where RELATIVE_FIELD is defined in your settings.py file? Perhaps
> I've
> > > > missed the mark on this.. I'm relatively new to django-dev
> > > > discussions.
> >
> > > > -justin
> >
> > > > On Fri, Feb 22, 2008 at 6:16 AM, Graham Carlyle
> > > > <[EMAIL PROTECTED]> wrote:
> >
> > > > I'd like to request that FilePathField should have an extra
> > > > option that
> > > > causes it to only save a relative path (to the path
> > > > parameter), say
> > > > called "relative".
> >
> > > > Having an absolute path stored makes it harder to move data
> > > > between
> > > > machines that are set up differently (say development and
> > > > production).
> > > > In this circumstance I would typically set the path
> parameter
> > > > from the
> > > > settings file.
> >
> > > > The "relative" argument could default to False to keep the
> > > > current
> > > > behaviour by default. Actually i can't think when you would
> > > > want
> > > > absolute paths but maybe someone does.
> >
> > > > Shall I create a ticket (and possibly a patch) for this? or
> am
> > > > I missing
> > > > something?
> >
> > > > cheers,
> > > > Graham
> >
> > > > --
> > > > Justin Lilly
> > > > Web Developer
> >
> > --
> > Justin Lilly
> > Web Developer
> >
>


-- 
Justin Lilly
Web Developer

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

GenericRelations reverse accessors

[Michael Elsdörfer]

class Feature(models.Model):
 content_object = generic.GenericForeignKey()

class Review(models.Model):
 features = GenericRelation(Feature)

class Person(models.Model):
 features = GenericRelation(Feature)

>> Person.objects.create() # id = 1
>> Review.objects.create() # id = 1
>> Feature.objects.filter(review__id=1)
[, ]

i.e. both the ``Person`` and ``Review`` objects are returned, even
though the query only requests reviews.

I just realized that the docs (at
http://www.djangoproject.com/documentation/models/generic_relations/)
don't mention querying a generic relation like that at all: Is this not
supposed to be supported, or is it a bug?

Michael


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: GenericRelations reverse accessors

[Malcolm Tredinnick]

On Sat, 2008-02-23 at 05:14 +0100, Michael Elsdörfer wrote:
[...]
> i.e. both the ``Person`` and ``Review`` objects are returned, even
> though the query only requests reviews.

Because it doesn't consider content_type in the query, only object_id.

> I just realized that the docs (at
> http://www.djangoproject.com/documentation/models/generic_relations/)
> don't mention querying a generic relation like that at all: Is this not
> supposed to be supported, or is it a bug?

It's a bug (#5937). I'm wanting to fix it in a fashion that is a bit
more holistic than the patch in that ticket, though. It's the first case
where we have a single Django model field mapping to multiple database
fields. It won't be the only one (e.g. dates with timezones mapping to
MySQL), so a proper solution is called for.

Regards,
Malcolm

-- 
How many of you believe in telekinesis? Raise my hand... 
http://www.pointy-stick.com/blog/


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---