[Patches] [ python-Patches-677103 ] PYTHONBYTECODEBASE patch (PEP 304)

[SourceForge.net]

Patches item #677103, was opened at 2003-01-29 16:49
Message generated for change (Comment added) made by montanaro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=305470&aid=677103&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Core (C code)
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Submitted By: Skip Montanaro (montanaro)
Assigned to: Skip Montanaro (montanaro)
Summary: PYTHONBYTECODEBASE patch (PEP 304)

Initial Comment:
This is just a placeholder patch related to PEP 304.  Feel free to
comment on it.  It's far from complete at this point.  The first
patch is just to see if we can do all the proper detection at
startup.  These checks have to be performed before any .py
files are imported, otherwise you'd have some .pyc files dumped
out before the machinery is ready to go.

The first patch contains mods to sysmodule.c with next to
no concern for platform independence.  There is a small shell
script and a few expected output files which are used to
test setting of various values.  These should probably be
wrapped into regular PyUnit tests which popen() the interpreter
with different settings, but this seemed quicker as a start.

----------------------------------------------------------------------

>Comment By: Skip Montanaro (montanaro)
Date: 2005-12-16 10:15

Message:
Logged In: YES 
user_id=44345

I sorta lost interest (it was never really anything I
needed anyway) when the Windows problems were raised,
especially after nobody suggested fixes.  If you'd like to
update the patch and perhaps champion it, be my guest.

Skip


----------------------------------------------------------------------

Comment By: Steven Knight (stevenknight)
Date: 2005-12-16 09:15

Message:
Logged In: YES 
user_id=216109

Skip--

Is there any interest in this patch getting accepted into
core Python?  Are there any other known barriers apart from
the Windows issues?

If this would likely be accepted once the Windows issues are
worked out, I might be able to spend some time looking at
the Windows side.

        --SK

----------------------------------------------------------------------

Comment By: Skip Montanaro (montanaro)
Date: 2005-06-16 20:26

Message:
Logged In: YES 
user_id=44345

Update patch for current CVS (2.5a0)...


----------------------------------------------------------------------

Comment By: Skip Montanaro (montanaro)
Date: 2004-11-14 17:12

Message:
Logged In: YES 
user_id=44345

*sigh* - let's try again...


----------------------------------------------------------------------

Comment By: Skip Montanaro (montanaro)
Date: 2004-11-14 16:48

Message:
Logged In: YES 
user_id=44345

Patch updated for current CVS (~ 2.4b2).


----------------------------------------------------------------------

Comment By: Skip Montanaro (montanaro)
Date: 2003-01-31 11:37

Message:
Logged In: YES 
user_id=44345

Another patch.  This one fixes the problems of the one I withdrew yesterday.
There are still problems:

* A half dozen regression tests fail for various reasons which I haven't
completely investigated.

* Nothing has been done for Windows.  Someone will have to step up to
the plate for this.  I can't build on Windows.

----------------------------------------------------------------------

Comment By: Skip Montanaro (montanaro)
Date: 2003-01-30 16:51

Message:
Logged In: YES 
user_id=44345

While not technically broken, the patch I just posted is a bit bent.
Withdrawing for a little fixup...

----------------------------------------------------------------------

Comment By: Skip Montanaro (montanaro)
Date: 2003-01-30 16:33

Message:
Logged In: YES 
user_id=44345

Here's an updated context diff.  It seems to do the right thing on my
Mac OS X system.  It won't currently do anything on Windows ( need help
there).  No more test cases, but if PYTHONBYTECODEBASE points to
a valid directory, the .pyc files seem to get put in all the right places.

To get the behavior, you'll have to configure --with-bytecodebase.

Feedback, please...

----------------------------------------------------------------------

Comment By: Skip Montanaro (montanaro)
Date: 2003-01-29 16:52

Message:
Logged In: YES 
user_id=44345

second upload try - what the hell is with SF?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=305470&aid=677103&group_id=5470