Issue2019

Hi,

Can you tell me if there is any workaround for the bug mentioned in bugs.jython.org/issue1885 ? As in - is there any was of pr-empting it? Is there any change that I can make to the file system etc to prevent it happening?

Regards,
Dónal

What version of Jython on what platform are you seeing this? Also can you provide the code that you are using when you see a problem?

Ah all of this is in the other bug description. I'm not sure it helps to have another bug open on this. If you want to start a discussion you could post to the jython-user mailing list.

So it should be fixed on 2.5.4rc1 and 2.7b1 - is it not for you?

Hi Frank,

Thanks. I was hoping there might be a way to avoid the issue without upgrading! 

Is there a way?!?

Regards,
Dónal

The only way that I can think of is to do a system call for chmod so:

from os import system
system('chmod 660 file.txt')

If that's not good enough then upgrading is probably your only option.

thks.

Will that work on Solaris 10? I don't recognise the syntax...

ignore my last text - my bad - tried it in jpython shell and it worked. Thanks for that!

OK, glad I could help.

Hi Frank,

I'm back again.
Is Jython 2.5.3 backward comatible with 2.5.2?

Regards,
Dónal

In general yes 2.5.3 should be backwards compatible with 2.5.2. We don't tend to make big changes in point releases - though I will say we expect to have some bending of this rule for the first few 2.7 releases. Having said that, there have been bug fixes which in rare cases might cause some trouble. In particular we may be changing the default command line code as there have been some bugs with our current default on windows machines. The RC does not have this change yet (so there will be another RC before a final).

Also note that the command line handling is easy to change. If we do go forward with that the release will contain pointers to change it back.

Hi Frank, Thanks. Does the same go for 2.5.2 versus 2.5.4rc1?
Also - is it safe to take an rc build, or, should we wait for the final build?

Regards,
Dónal

In principle I'd wait for a final - there will be an RC2 first and then a final 2.5.4 pretty soon. If we find a fix for this on Solaris it would be in a 2.5.5 I think, since I doubt this will be fixed in the timeframe for a a 2.5.4 final (I expect to be done with that in a little over a week).

Have you considered using

os.system("chmod ...")

as a workaround?