Still unable to upload the patch.  Error message states "You do not have permission to create file".


Josh Juneau
Twitter ID:  javajuneau

On Mon, Feb 15, 2010 at 10:30 PM, Anthony Kong <> wrote:
I think you are right! It's so obvious! :-)

From: Josh Juneau []
Sent: Tuesday, 16 February 2010 3:09 PM
To: Anthony Kong
Subject: Re: [Jython-users] [Jython-dev] Unable to Submit Patch


In looking at your test, it appears you named the file and this s causing the issue.  Try to rename it to and re-run.  I think you'll see the correct output in doing so.


Josh Juneau
Twitter ID:  javajuneau

On Mon, Feb 15, 2010 at 1:51 PM, Anthony Kong <> wrote:
Hi, Josh,

Sorry, for hijacking the thread. But I have a question related to issue 1551, and you probably already have some insight into the root cause.

For me, I just want to understand this issue a bit better.

If I repeated what is in the bug description, I can reproduce the SystemError

But if I have the same code in a script, says

def test():
        from java.util import ArrayList
        gList = ArrayList()

        import copy
        copyList = copy.copy(gList)
        print copyList

if __name__ == "__main__":

Then I got an entirely different exception:

Traceback (most recent call last):
  File "tests/python/", line 11, in <module>
  File "tests/python/", line 6, in test
    copyList = copy.copy(gList)
AttributeError: 'module' object has no attribute 'copy'

Why the difference in behavior?


On Tue, Feb 16, 2010 at 3:41 AM, Josh Juneau <> wrote:
I'm trying to submit a patch to for and I'm unable to create a file.  I believe that I used to be able to submit files via the bug tracker.  Is anyone else having issues or have privileges changed?



This e-mail and any attachments are confidential and may contain copyright material of Macquarie Group Limited or third parties. If you are not the intended recipient of this email you should not read, print, re-transmit, store or act in reliance on this e-mail or any attachments, and should destroy all copies of them. Macquarie Group Limited does not guarantee the integrity of any emails or any attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Macquarie Group Limited.