[issue1636] Execfile unable to take arguments beyond 255!

Martin v. Löwis added the comment: Closing it as "won't fix": nobody is really interested in working on the problem. -- resolution: -> wont fix status: open -> closed ___ Python tracker __

[issue1636] Execfile unable to take arguments beyond 255!

Alexander Belopolsky added the comment: I don't have much to contribute other than a simple test to reproduce the issue: >>> code = """ >>> >>>

[issue1636] Execfile unable to take arguments beyond 255!

Martin v. Löwis added the comment: While you can't modify the MIB, I'm sure it would be possible to change the generator code that compiles the MIB into Python source code, to work around the restrictions in the byte code. __ Tracker <[EMAIL PROTECTED]>

[issue1636] Execfile unable to take arguments beyond 255!

Guido van Rossum added the comment: This comes from line 1845 in ast.c. It has nothing to do with execfile(), it's just a constraint on the generated bytecode. Fixing this would be quite complex, and referring to "this day and age" isn't going to raise its priority. However, I'd be happy to ac

[issue1636] Execfile unable to take arguments beyond 255!

Jack Atkinson added the comment: Error message from ipython console: In [28]: mibBuilder2 = builder.MibBuilder().loadModules('ADTRAN-TC') --- Traceback (most recent call last) C:\Documents and Settings\Jack Atkinson\

[issue1636] Execfile unable to take arguments beyond 255!

Martin v. Löwis added the comment: Can you please be more specific? What code exactly are you executing, and what is the exact error message that you get? In the entire Python source code, the error message "Execfile unable to take arguments beyond 255!" is never produced. Very few error message

[issue1636] Execfile unable to take arguments beyond 255!

New submission from Jack Atkinson: 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 mo