Differences between revisions 5 and 6
Revision 5 as of 2007-08-04 22:33:15
Size: 1173
Editor: PhilipJenvey
Comment: mention mkstemp investigations
Revision 6 as of 2007-08-04 22:34:20
Size: 1171
Editor: PhilipJenvey
Comment: meant java, not jython
Deletions are marked like this. Additions are marked like this.
Line 16: Line 16:
  - This is somewhat problematic because even the best Jython mkstemp implementation won't return a file descriptor (No raw file descriptors in jython), but setuptools can possibly be patched to use NamedTemporaryFile instead   - This is somewhat problematic because even the best Jython mkstemp implementation won't return a file descriptor (No raw file descriptors in java), but setuptools can possibly be patched to use NamedTemporaryFile instead

Setuptools requirements:

  • PEP 302: added in Jython 2.2

We don't have:

  • PEP 273 (the zipimport module)
    • - Jython's ZipFileImporter is somewhat different that the CPython zipimport module -- it's not a module, and it does not maintain its own _zip_importer_cache (which setuptools utilizes) apart from sys.path_importer_cache

      - The Jython zipimport machinery is different: ZipFileImporter only imports zips if they're SyspathArchives: currently .zips and .jars. How does CPython zipimport identify .eggs in sys.path as .zips? (needed for the ez_setup bootstrap process)

  • distutils
  • tempfile.mkstemp
    • - I've begun taking a look at implementing mkstemp/NamedTemporaryFile with Java's secure File.createTempFile
  • os.open is used for a small hack having to do with usage of tempfile.mkstemp
    • - This is somewhat problematic because even the best Jython mkstemp implementation won't return a file descriptor (No raw file descriptors in java), but setuptools can possibly be patched to use NamedTemporaryFile instead

  • imp.acquire/release_lock

SetuptoolsOnJython (last edited 2010-01-02 16:58:16 by AndrewKuchling)