Releases: ironfroggy/feet
Python Feet 0.6.0
v0.6.0 Tag v0.6.0
Python Feet 0.7.0 RC2
v0.6.0rc2 Fixing tests
Feet v0.6.0rc1
- EXE command is temporarily deprecated
- Consistently will produce both 32-bit and 64-bit builds now
- Smaller bootloader binary
- Feet builds now include metadata that will help upcoming packaging features
- ZIP command now auto-includes relavent files safely
Feet v0.5.0
Added -a flag to control architecture (amd64 or win32) when building python distribution or feet.exe
Integrated python build process with new command, feetmaker.py python
, which downloads and compiles Python.
New Python step requires Visual Studio installation.
If you only want to use Feet, just download the pre-built binaries attached to this release! Available in 32-bit and 64-bit versions now.
Please submit feedback, questions, and bug reports through the issue tracker.
Feet 0.4.0 - October 6, 2019
Feet 0.4.0 expands support for packages that require setuptools, and reworks the location of project dependencies inside the runtime. Dependencies are now installed inside the portable Python runtime included with Feet, rather than as part of your project. This gives you a cleaner workspace. The setuptools improvements also means support for more modern packages, like Pyglet for games.
Feet 0.4.0 also switches from x86 to x86_64 architecture.
You can download the attached Zip to get version 0.4.0 of feet.exe to run your Python games and applications. The use is simple:
- place feet.exe in a directory with a main.py script
./feet.exe library NAME
for each library from PyPI your project depends on./feet.exe
or double-click the EXE to run your project!
You can rename feet.exe
to anything appropriate for your project, if you want.
You may generate distributable copies with the exe
command:
./feet.exe exe my-game-1.0.exe
New changes in 0.4.0 include:
- Support for packages that use setuptools in setup.py
- Dependencies are now inside the
feet_data
directory, rather than in our project itself - EXE distributables generated will include your project files by default, instead of requiring an explicit include list
- The project now has a test suite ensuring better and improving stability
- Binaries are now 64-bit
Feet 0.3.0 - Ready to Run
This is the first version that I'm ready to say "this is ready to use maybe"!
You can download the attached Zip to get version 0.3.0 of feet.exe
to run your Python games and applications. The use is simple:
- place
feet.exe
in a directory with amain.py
script ./feet.exe library NAME
for each library from PyPI your project depends on./feet.exe
or double-click the EXE to run your project!
New changes in 0.3.0 include:
- The
feet.exe
file can now be renamed - The runtime is extracted to a directory based on the EXE name,
feet_data
by default - The runtime is much smaller, and has many fewer files, and unpacks much, much faster!
- There is a new
feet.exe bundle
command.feet.exe bundle my-game-1.0.0.exe
to pack up your script and the Feet runtime into a single self-extracting EXE feet.exe bundle my-game-1.0.0.exe main.py mygame/*
if you need to include more files than the default script
Feet 0.2.0 - Smaller, Faster, Smarter Feet
This update to Feet includes several runtime improvements and changes, as well as an improved build with a slimmer runtime package that should start up much quicker!
Runtime changes include:
- On the first run, if a project has a
requirements.txt
file but noLib/
folder, the requirements will be installed - On the first run, Feet will make sure its not being run on itself (and has been copied to a project instead) for safety
- There is more concise output during the startup
- The requirements file is only updated if a new library install is successful
- The build includes some required bits that weren't always available on target machines, particularly for package management
- If you download a new version of Feet, the next run will replace the runtime folder with updates
Download Feet 0.2.0 below!
Feet 0.1.1 - Runtime Dependency Fixes
Feet has replaced its dependency on PyInstaller with a custom Rust bootloader.
The bootloader is used exactly the same as the previous feet.exe, but is no longer produced by PyInstaller. Instead, it is a self-extracting EXE that creates a feet/ runtime directory, only if one does not already exist, and proceeds to run the Feet commands you invoke. The unpack is only one-time, for performance reasons. This includes a full build of Python. Work will come in the future to reduce the size of this build, but priority for now is to run any program someone wants to use.
This new version still supports the run, library, and shell commands.
To use Feet, download feet-0.1.0.zip and extract the feet.exe file. Put it in a directory with your main.py script. If you need any Python libraries, like pygame or ppb, install them like ./feet.exe library ppb
Just double-click the feet.exe file to run your game or app!
Feet 0.1 - "A Little Bit Rusty"
Feet has replaced its dependency on PyInstaller with a custom Rust bootloader.
The bootloader is used exactly the same as the previous feet.exe
, but is no longer produced by PyInstaller. Instead, it is a self-extracting EXE that creates a feet/
runtime directory, only if one does not already exist, and proceeds to run the Feet commands you invoke. The unpack is only one-time, for performance reasons. This includes a full build of Python. Work will come in the future to reduce the size of this build, but priority for now is to run any program someone wants to use.
This new version still supports the run
, library
, and shell
commands.
To use Feet, download feet-0.1.0.zip
and extract the feet.exe
file. Put it in a directory with your main.py
script. If you need any Python libraries, like pygame
or ppb
, install them like ./feet.exe library ppb
Just double-click the feet.exe
file to run your game or app!
Python Feet 0.0.2, with the Library Experiment
This build removes the built-in pygame, and instead adds the library
subcommand to install packages from PyPI into a project. See the README for new expanded documentation.