Issue2282

classification
Title: No compilation step to produce $py.class files for stdlib for nondev targets
Type: Severity: normal
Components: Versions: Jython 2.7
Milestone:
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: zyasoft Nosy List: zyasoft
Priority: urgent Keywords:

Created on 2015-03-09.17:41:04 by zyasoft, last changed 2015-03-29.05:37:39 by zyasoft.

Messages
msg9594 (view) Author: Jim Baker (zyasoft) Date: 2015-03-09.17:41:04
$py.class files are not generated for the standard library (Lib/) under release targets, unlike when built under a dev target. Naturally developers like me do not see this issue :)

This was recently raised on jython-dev, http://sourceforge.net/p/jython/mailman/message/33546082/, although there's still more work to do to fix the problems with web start.

Note that this problem manifests itself as cannot import site.py, but that's just a red herring. The standard library should always be importable for Jython, even if it's possible to run it with some smaller subset (possibly even none).

Related issue is #2281, as well as a number of modjy workarounds.

Blocker for RC1
msg9628 (view) Author: Jim Baker (zyasoft) Date: 2015-03-11.23:39:17
This same problem was raised in #1403
msg9694 (view) Author: Jim Baker (zyasoft) Date: 2015-03-21.04:56:44
Fixed as of https://hg.python.org/jython/rev/72cf10235676 - a simple change once I realized what was happening in the extra erroneous work done by jarjar task, vs just using a jar task
History
Date User Action Args
2015-03-29 05:37:39zyasoftsetstatus: pending -> closed
2015-03-21 04:56:44zyasoftsetstatus: open -> pending
resolution: fixed
messages: + msg9694
2015-03-11 23:39:17zyasoftsetmessages: + msg9628
2015-03-09 17:41:05zyasoftcreate