By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
432,490 Members | 1,417 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 432,490 IT Pros & Developers. It's quick & easy.

PEP 304 "Controlling Generation of Bytecode Files" - patch updated

P: n/a

I updated the patch that supports PEP 304, "Controlling Generation of
Bytecode Files" to apply cleanly against current CVS. I've tested it on Mac
OS X (straight Unix build only). I'd appreciate it if some Linux, Windows
and Mac framework folks could apply the patch, rebuild, then run the tests
(there is a "testbcb" target in the Makefile that should give Windows people
an idea what to do). The patch is attached to

http://python.org/sf/677103

Now that I think about it, there is probably a file in the Windows build
tree (equivalent of pyconfig.h?) that still needs to be updated.

The text of the PEP has not been updated in awhile. I will try to look at
that in the next couple of days. I'd appreciate some critical review by
people with Windows filesystem experience. There was a comment ages ago
about problems with this scheme due to Windows multi-rooted directory tree
that I can no longer find (and failed to record in the PEP at the time).
I'd like to see if the problem can be resurrected then addressed.

Thanks,

Skip

Jul 19 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Skip Montanaro <sk**@pobox.com> writes:
I updated the patch that supports PEP 304, "Controlling Generation of
Bytecode Files" to apply cleanly against current CVS. I've tested it on Mac
OS X (straight Unix build only). I'd appreciate it if some Linux, Windows
and Mac framework folks could apply the patch, rebuild, then run the tests
(there is a "testbcb" target in the Makefile that should give Windows people
an idea what to do). The patch is attached to

http://python.org/sf/677103

There's no patch attached.

Thoas
Jul 19 '05 #2

P: n/a
Skip> http://python.org/sf/677103

Thomas> There's no patch attached.

*sigh*

Thanks for noticing the problem. Apparently, since I last updated the
patch, SF implemented a 250kbyte limit on file uploads. This one is big
because it includes a suitably modified configure script that was generated
with a slightly different version of autoconf than what's in the current
Python distro so people don't need to have autoconf installed to work with
the patch. I've attached a gzipped version of the patch (bcb.diffs.gz).

Skip

Jul 19 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.