On 12/5/2009 8:27 AM, Terry Reedy wrote:
Victor Subervi wrote:
I'm not rude
To me, asking for help without providing sufficient information,
especially when requested, is a form of rudeness.
Think about that and don't be rude.
Why does this sounds familiar?
http://groups.google.com/group/c
Victor Subervi wrote:
I'm not rude
To me, asking for help without providing sufficient information,
especially when requested, is a form of rudeness.
Think about that and don't be rude.
Exactly.
Terry Jan Reedy
--
http://mail.python.org/mailman/listinfo/python-list
On Thu, Dec 3, 2009 at 7:07 PM, Steven D'Aprano <
st...@remove-this-cybersource.com.au> wrote:
> On Thu, 03 Dec 2009 10:13:14 -0500, Carsten Haese wrote:
>
> > Victor Subervi wrote:
> >> I believe I mentioned in my first post that the "print test" does print
> >> the exact fields being called from
On Thu, 03 Dec 2009 10:13:14 -0500, Carsten Haese wrote:
> Victor Subervi wrote:
>> I believe I mentioned in my first post that the "print test" does print
>> the exact fields being called from the referring page.
>
> Was any part of "What do the print statements actually print? Please
> copy and
On Thu, Dec 3, 2009 at 12:38 PM, Carsten Haese wrote:
> Victor Subervi wrote:
> > No, it doesn't, because you've only provided one third of what I
> asked
> > for. I also asked for the code and the inputs that go into it.
> >
> >
> > I provided those earlier.
>
> No, you didn't provide the
Victor Subervi wrote:
> No, it doesn't, because you've only provided one third of what I asked
> for. I also asked for the code and the inputs that go into it.
>
>
> I provided those earlier.
No, you didn't provide the exact code you're running. You provided a
selected snippet you deemed
On Thu, Dec 3, 2009 at 10:53 AM, Carsten Haese wrote:
> Victor Subervi wrote:
> > In order to help you diagnose the problem, we need to see the *exact*
> > code you're running, we need to see the *exact* inputs going into it,
> > and we need to see the *exact* output coming out of it.
Victor Subervi wrote:
> In order to help you diagnose the problem, we need to see the *exact*
> code you're running, we need to see the *exact* inputs going into it,
> and we need to see the *exact* output coming out of it.
>
>
> Let's see your answers and see if you're right that the
On Thu, Dec 3, 2009 at 10:13 AM, Carsten Haese wrote:
> Victor Subervi wrote:
> > I believe I mentioned in my first post that the "print test" does print
> > the exact fields being called from the referring page.
>
> Was any part of "What do the print statements actually print? Please
> copy and p
Victor Subervi wrote:
> I believe I mentioned in my first post that the "print test" does print
> the exact fields being called from the referring page.
Was any part of "What do the print statements actually print? Please
copy and paste their output." unclear to you in any way?
> Perhaps this
> i
On Thu, Dec 3, 2009 at 8:02 AM, Victor Subervi wrote:
> On Thu, Dec 3, 2009 at 6:07 AM, Victor Subervi wrote:
>
>> On Wed, Dec 2, 2009 at 4:08 PM, MRAB wrote:
>>
>>> Victor Subervi wrote:
>>>
Hi;
I have spent 2-3 hours trying to track this bug. Here's the code
snippet:
f
On Thu, Dec 3, 2009 at 6:07 AM, Victor Subervi wrote:
> On Wed, Dec 2, 2009 at 4:08 PM, MRAB wrote:
>
>> Victor Subervi wrote:
>>
>>> Hi;
>>> I have spent 2-3 hours trying to track this bug. Here's the code snippet:
>>>
>>> form = cgi.FieldStorage()
>>> fn = getattr(options, 'products')
>>> ou
On Wed, Dec 2, 2009 at 4:08 PM, MRAB wrote:
> Victor Subervi wrote:
>
>> Hi;
>> I have spent 2-3 hours trying to track this bug. Here's the code snippet:
>>
>> form = cgi.FieldStorage()
>> fn = getattr(options, 'products')
>> ourOptionsNames = []
>> optionsNames, doNotUse = fn('names')
>> f
Victor Subervi wrote:
Hi;
I have spent 2-3 hours trying to track this bug. Here's the code snippet:
form = cgi.FieldStorage()
fn = getattr(options, 'products')
ourOptionsNames = []
optionsNames, doNotUse = fn('names')
for name in optionsNames:
test = table + '-' + name
print t
14 matches
Mail list logo
