Skip to content

Fix python::virtualenv to allow virtualenv to not require absolute path#592

Merged
bastelfreak merged 2 commits intovoxpupuli:masterfrom
treydock:virtualenv
Dec 13, 2020
Merged

Fix python::virtualenv to allow virtualenv to not require absolute path#592
bastelfreak merged 2 commits intovoxpupuli:masterfrom
treydock:virtualenv

Conversation

@treydock
Copy link
Copy Markdown
Contributor

Pull Request (PR) description

I maintain several modules where I might do something like virtualenv => 'virtualenv-3' and that works just fine and doesn't require me to know the full path on each OS. Also the default value if undef is just virtualenv so doesn't make sense to require the non-default values be more restrictive than the default.

@treydock treydock changed the title Fix python::virtualenv to allow virtualenv to require absolute path Fix python::virtualenv to allow virtualenv to not require absolute path Dec 12, 2020
@bastelfreak bastelfreak self-assigned this Dec 13, 2020
@bastelfreak bastelfreak added the bug Something isn't working label Dec 13, 2020
@bastelfreak
Copy link
Copy Markdown
Member

@treydock can you maybe add a test that enforces it's just a string? Otherwise I'm friend this gets changed to Stdlib::Absolutepath soonish again

@treydock
Copy link
Copy Markdown
Contributor Author

@bastelfreak Added unit tests for virtualenv.

@bastelfreak bastelfreak merged commit 7941a0c into voxpupuli:master Dec 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants