Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

app version retrieving the wrong version #4323

Closed
pitosalas opened this issue Jul 27, 2021 · 5 comments
Closed

app version retrieving the wrong version #4323

pitosalas opened this issue Jul 27, 2021 · 5 comments

Comments

@pitosalas
Copy link

A script managed by poetry:

 import pkg_resources
    return(pkg_resources.get_distribution('otproject').version)

seems to be returning the "wrong version". Here's what I mean:

  1. in the toml file, I have 0.1.1 (this was edited from an earlier time when it was 0.1.0)
  2. when I run my code from a. poetry shell, I get the right version
  3. if I run it with a [tool.poetry.scripts] I get the "older" version

It's as if there's some cache or other left over that is coming into play. Any clue? Thanks!

@finswimmer
Copy link
Member

Hello @pitosalas,

can you check if this happens with the latest preview release (1.2.0a1)? I thinks this is a duplicate of #3289 which is already fixed in master by #3900.

fin swimmer

@finswimmer finswimmer added the status/waiting-on-response Waiting on response from author label Jul 28, 2021
@pitosalas
Copy link
Author

pitosalas commented Jul 28, 2021 via email

@pitosalas
Copy link
Author

pitosalas commented Jul 28, 2021 via email

@finswimmer
Copy link
Member

By the way, if I want to launch a specific script that relies on the poetry venv from crontab, how do I do that?

You could activate the venv first before running any other command e.g. source /path/to/venv/bin/activate && python script.py

@mkniewallner mkniewallner removed the status/waiting-on-response Waiting on response from author label Jun 11, 2022
Copy link

github-actions bot commented Mar 2, 2024

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants