Message 58668 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	jgatkinsn
Recipients	jgatkinsn
Date	2007-12-16.01:19:17
SpamBayes Score	0.0646206
Marked as misclassified	No
Message-id	<1197767959.22.0.840307964309.issue1636@psf.upfronthosting.co.za>
In-reply-to

Content
I found this problem while using PySNMP and trying to load a custom MIB converted to python code. Inside the PySNMP, it uses execfile() to load the python MIBs, and I assume so it won't be put into a separate namespace. On one particular MIB, which I cannot modify because it's a company product MIB, this error of unable to take in more than 255 arguments occurs. The problem line is quite long, but surely in this day and age of 32 bit to 64 bit machines this 255 constraint could be done away with in the execfile function. I'm assuming the 255 constraint has something to do with unsigned 8 bit number.

I found this problem while using PySNMP and trying to load a custom MIB
converted to python code.  Inside the PySNMP, it uses execfile() to load
the python MIBs, and I assume so it won't be put into a separate
namespace.  On one particular MIB, which I cannot modify because it's a
company product MIB, this error of unable to take in more than 255
arguments occurs.  The problem line is quite long, but surely in this
day and age of 32 bit to 64 bit machines this 255 constraint could be
done away with in the execfile function.  I'm assuming the 255
constraint has something to do with unsigned 8 bit number.

History
Date	User	Action	Args
2007-12-16 01:19:19	jgatkinsn	set	spambayes_score: 0.0646206 -> 0.0646206 recipients: + jgatkinsn
2007-12-16 01:19:19	jgatkinsn	set	spambayes_score: 0.0646206 -> 0.0646206 messageid: <1197767959.22.0.840307964309.issue1636@psf.upfronthosting.co.za>
2007-12-16 01:19:18	jgatkinsn	link	issue1636 messages
2007-12-16 01:19:18	jgatkinsn	create