v0.2.1

Linux execution fix: the requirements installation step was previously not working, but it is now accessible.

Additionally, improvements were made to the "PIP" path verification, among other things...

Full Changelog: v0.2.0...v0.2.1

v0.2.0

Release Summary

Important

This executable is not the installer; I will come back and upload the installer with an update. For now, this is the actual programme itself, which means you must add it to the system PATH (in Windows) if you want to avoid using the full path every time you run it. I will upload this update in the coming weeks.

This release introduces major improvements focused on Linux compatibility and cross-platform stability. Linux support has been added after multiple testing and refinement iterations, ensuring reliable behaviour alongside existing Windows functionality.

The tool now recognises several commonly used virtual environment names (such as venv, .venv, env, and .env), improving flexibility across different development setups.

In addition, the codebase was cleaned up and refined by removing unnecessary comments, fixing previously broken or removed command methods, and improving platform-specific handling. Project configuration files were updated to explicitly include Linux support.

This release consolidates multiple development commits into a stable merge. For a detailed breakdown of changes, please refer to the individual commits and the merged pull request.

Execution Linux-x64

test-linux-x64.mp4

What's Changed

• Add sponsor info by @tutosrive in #17
• Major updates to can acces it from Linux by @tutosrive in #18

Full Changelog: v0.1.0-beta...v0.2.0

v0.1.0-beta

InitVenv v0.1.0-beta

Automatic create, install requirements and activate venv only with one command: InitVenv

Requirements

• Have python installed and have the path in the PATH
• Initially it only works on Windows systems

Usage Instructions

Important

• If you want to use the program from CMD, make sure you pass a path, just one, like this: Initvenv "path". You can use absolute or relative paths.
• If you prefer to use it from Windows File Explorer, follow these steps.

Its main functionality, is:

1. Go to any directory (With File Explorer in Windows)
2. Make a requirements.txt file (Important, it must be with the written requirements, the program will not understand the requirements once the venv is created)
3. Press keys CTRL+L
4. Step 2 activates the explorer's path bar, so you must type the following command: InitVenv
5. The program will be start and execute automatically

Installation Process

I want to know what the installer does

1. Copy and paste the "InitVenv-{architecture}.exe" and "InnitVenv.bat" files to the installation directory you selected.
2. Use the `` command to add the installation directory to the system PATH.

That's all the installer does; it adds the path to the system PATH, allowing you to use the program with a simple call to InitVenv, which then calls InitVenv.bat.

Note

If you're unsure what the .bat file contains, it contains this:

@echo off
start "" "InitVenv-x64.exe" "%CD%"
exit

Screenshots

Description	Preview
Program startup error - missing working directory
Successful program initialization without requirements file
Console with virtual environment activated for user
Program execution with requirements file installation
User terminal session maintained after setup

Development History

What's Changed

• Initial commit by @tutosrive in #1
• New class method in Files class (ReadJSON<T>(string pathFile)) by @tutosrive in #2
• Update model classes and Utilities classes by @tutosrive in #3
• Update project SDK version and others by @tutosrive in #4
• Updates structures by @tutosrive in #5
• Update and refactorize something files and folder structure by @tutosrive in #6
• Update project, new validations and others by @tutosrive in #7
• Refactorice project and update, add new validations. by @tutosrive in #8
• Try catch missing requeriments in the .venv by @tutosrive in #9
• Update start script for windows, is functional right now! by @tutosrive in #10
• Add TODO file and refactorize files by @tutosrive in #11
• Fix some order validations by @tutosrive in #12
• TODO Add new bugs and features 'idea' by @tutosrive in #13
• Add project icon by @tutosrive in #14
• Update the project config by @tutosrive in #15

New Contributors

• @tutosrive made their first contribution in #1

Full Changelog: https://github.com/Dev2Forge/Init-Venv/commits/v0.1.0-beta

SourceForge.net