[EMAIL PROTECTED] wrote:
>
>>FWIW, always try to reduce code to the minimal runnable snippet
>>exhibiting the problem, so others have a chance to help you. As a
>>side-effect, one very often finds the problem while doing so !-)
>
>
> Sorry I can't post to much of the code. Some of what I'm using is
> grabbing infromation off of our internal database, and for compliance
> reasons I can't print enough code so that it would actually run.
"Reducing to the minimal runnable snippet exhibiting the problem"
actually implies not depending on any DB or whatever. Nothing prevents
you from replacing these parts with mock objects returning dummy data.
And this is exactly why this process very often reveals the problem...
> Thanks for you help anyways, I'll try and figure out what I can. If
> necessary I'll retool the whole thing
>
--
bruno desthuilliers
python -c "print '@'.join(['.'.join([w[::-1] for w in p.split('.')]) for
p in '[EMAIL PROTECTED]'.split('@')])"
--
http://mail.python.org/mailman/listinfo/python-list
