[EMAIL PROTECTED] wrote:
> Like i want the
> key 170 to take either the name 'dataPackageID' or the name
> 'LocalId'.I use this in my code,and hence if either comes it should
> work .
It should work to do what exactly? Cause a perturbation in the orbit of
Mars, or something else entirely?
James
On Mon, 2007-05-07 at 06:06 -0700, John Machin wrote:
> Unlikely. "Turning it around" produces one key ('subfunction') with
> *FIVE* different values.
Whoops! I assumed the OP's problem was reasonably well-formed and didn't
actually check if any of the values were duplicated. I guess the OP will
j
On May 7, 10:59 pm, Carsten Haese <[EMAIL PROTECTED]> wrote:
> On Mon, 2007-05-07 at 04:03 -0700, [EMAIL PROTECTED] wrote:
> > Hi,
> >I have a dictionary which is something like this:
> > id_lookup={
> > 16:'subfunction',
> > 26:'dataId',
> > 34:'parameterId',
> > 39:'subfunction',
> > 44:'
On Mon, 2007-05-07 at 04:03 -0700, [EMAIL PROTECTED] wrote:
> Hi,
>I have a dictionary which is something like this:
> id_lookup={
> 16:'subfunction',
> 26:'dataId',
> 34:'parameterId',
> 39:'subfunction',
> 44:'dataPackageId',
> 45:'parameterId',
> 54:'subfunction',
> 59:'dataId',
> 165:'s
>I have a dictionary which is something like this:
> id_lookup={
> 16:'subfunction',
> 26:'dataId',
> 34:'parameterId',
> 39:'subfunction',
> 44:'dataPackageId',
> 45:'parameterId',
> 54:'subfunction',
> 59:'dataId',
> 165:'subfunction',
> 169:'subfunction',
> 170:'dataPackageId',
> 174:'co
On May 7, 7:03 am, [EMAIL PROTECTED] wrote:
> Hi,
>I have a dictionary which is something like this:
> id_lookup={
> 16:'subfunction',
> 26:'dataId',
> 34:'parameterId',
> 39:'subfunction',
> 44:'dataPackageId',
> 45:'parameterId',
> 54:'subfunction',
> 59:'dataId',
> 165:'subfunction',
> 1
