You can subscribe to this list here.
Showing
3
results of 3
On 6
> saying.
>
> For example: In \Lib\tokenize.py the statement:
>
> from __future__ import generators
>
> is never subsequently used (e.g. generators is never instantiated)...
> So I am not sure if this is a bug. The jython runtime itself seems to
> silently ignore such things.. is there a way to do that for jythonc ??
Generators do not work at all with jythonc in 2.2 (They do work with
regular Jython, but not jythonc. There are fundamental problems with
the current implementation. To get generators in the next Jython
release (after 2.2 is out) we will have to re-write jythonc. For most
use cases, you can avoid the use of jythonc (for example see:)
The one use case that cannot be worked around is working with a locked
down security manager (for example, in an unsigned applet.) for this
you will still need jythonc.
-Frank
I did search (via nabble) for (mail list) threads about (execution)
threads, and saw other posts describing what seem to be exactly the same
thing:
One of the replies mentioned using a separate PySystemState instance for
each interpreter object, but as is also mentioned in these threads, it
doesn't seem to help (it doesn't help us either). And one of them
mentions that restricting to a single thread makes the errors go away
(as we observe as well). They don't mention which platform they're
using, but I don't know that it's necessarily a platform-specific
problem, unless it's an issue with certain JVMs. What seems certain is
that ease of reproduction of the problem depends on your hardware, but
that doesn't mean that the problem doesn't always exist. It seems like
either we're all doing something wrong on Windows and you're doing it
correctly on Linux, or Linux is just a platform where it is hard to
reproduce the problem. Maybe I should try other JVMs or OSs...
Andy
olivier merlin wrote:
> Hello,
>
> don't you fall under win32 specific OS issues ? I saw several threads
> on problem with many threads on windows.
> i ran last week complex scripts with 2048 threads under Linux . I have
> to do some adjustments on the 32bit kernel and the JVM parameters.
>
> regards,
> Olivier
>
> 2007/6/2, Oti <ohumbel@...>:
>> Michael,
>>
>> our team switched the machine a few days ago. It is now a 64-bit 'i do
>> not know how many core' machine (sorry I have to check that first).
>>
>> The strange coincidence is: Now I get error reports nobody can
>> explain, like:
>>
>> 1)
>> A method call (calling a method of the Java super class) succeeds on
>> one line of a script, and the exact same method call fails on the next
>> line (with an AttributeError). It is a simple one-line getter method
>> returning a reference to a private member.
>>
>> 2)
>> 'instance' has no attribute X, on a line where X isn't involved at
>> all. But X is imported on top of the script.
>>
>> Poeple say these scripts have been running successfully for a long
>> time on the old machine. These effects might have a completely
>> different reason, but who knows ?
>>
>> I'll try to run your example on this machine, but I can't promise any
>> time frame.
>> I will post my findings here.
>>
>> best wishes,
>> Oti.
>>
>> On 5/22/07, Michael Chisholm <chisholm@...> wrote:
>> >@...
>> > >>
>> > >>
>> > >
>> >
>> >
>> >.
>> >
>> > _______________________________________________
>> > Jython-users mailing list
>> > Jython-users@...
>> >
>> >
>> >
>> >
>>
>> -------------------------------------------------------------------------
>>
>> This SF.net email is sponsored by DB2 Express
>> Download DB2 Express C - the FREE version of DB2 express and take
>> control of your XML. No limits. Just data. Click to get it now.
>>
>> _______________________________________________
>> Jython-users mailing list
>> Jython-users@...
>>
>>
>
On 6
In Python import statements are procedural not declarative. That is
import statement causes initialization of respective module. So
strictly speaking this is not a bug.
However optimisation that allows import features just in case would
probably be useful.
--
Petr Gladkikh