Esky

Latest version: v0.9.9

Safety actively analyzes 638388 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 5

0.9.3

* Preliminary support for a "callback" argument to Esky.auto_update,
which is called with a dict of status info as update progresses.
* esky.patch: preserve file mode when patching a file.
* DefaultVersionFinder.open_url: ensure that f.size is always an int.

0.9.2

* Restore compatability with python2.5, via __future__ imports.
* esky.winres: use ctypes.WinError throughout, to make inlining of
code from this module more reliable.

0.9.1

* Fix some build issues on OSX:
* varname typo in f_py2app.
* undo py2app's changes to env["MACOSX_DEPLOYMENT_TARGET"] after
it has finished its work.
* don't let get_platform() change its value due to changes in the
build environment; if it does the build files get corrupted.
* correctly handle dots etc in sys.executable
* Fix some built issues on win32:
* the py2exe custom chainloader tried to use 'nt' module before
it was imported, giving an UnboundLocalError.

0.9.0

THIS RELEASE INTRODUCES A NEW ON-DISK FILE LAYOUT - SEE BELOW FOR NOTES

* Move the version directories, updates directory etc into an "appdata"
subdirectory, to avoid user confusion in the top-level directory. The
hope is that users will be much less inclined to poke around inside a
generic "appdata" directory than inside directories named after the app.
* to be clear, the new layout looks like this:
myapp.exe
appdata/
myapp-X.Y.X.win32/
myapp.exe
esky-files/
updates/
* the "bdist_esky" command still generates zipfiles using the old
layout, so they can be unpacked correctly by previous versions of
esky. To get the new layout, pass the "enable-appdata-dir" option.
This option will become the default (and will be removed) at the
end of the 0.9.* series.
* there are compatability hooks that upgrade the old file layout to
the new layout. They will be removed at the end of the 0.9.* series.
* therefore, if you have deployed applications using esky 0.8.* or
lower, you MUST deploy an update using the 0.9.* series before
migrating to any newer versions of esky.
* Remove compatability hooks for pre-0.8.0 on-disk layout.
* Add ability to compile the bootstrapping exes with the pypy translation
toolchain, to reduce distribution size and increase loading speed:
* pass the option "--compile-bootstrap-exes" to bdist_esky to
enable the compilation step.
* any custom bootstrapping code must be valid RPython; check the
variable __rpython__ to determine whether you're being compiled.
* obviously this only works if a recent version of the "pypy" package
is installed and configured correctly.
* Add verify() function to the bootstrap env, which is called to verify
files before they are chainloaded. The default implementation is empty,
but it could be overridden to perform e.g. signature checking.
* py2exe: never bundle the python dll into the bootstrap executable
unless it was bundled into the frozen app, it caused too many issues
with unsuspecting third-party libraries.
* Add utility functions "really_rename" and "really_rmtree", which retry
the operation in response to certain bogus errors on win32.

0.8.5

* FSTransaction: better error handling, and better detection of cases
where native transactions will fail (e.g. on a FAT32 USB device).
* FSTransaction: accept an optional "root" parameter, and enforce all
operations to be inside this root.
* bdist_esky: accept wider variety of objects for bootstrap_code option
and Executable.script attribute. Lists are concatenated, files are read,
strings are raw code, and all else is passed to inspect.getsource().
* Made bdist_esky.Executable a subclass of unicode rather than str.

0.8.4

* changed to a decorator-based syntax for declaring lazy imports, it's
cleaner and simpler.

Page 2 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.