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

the function convert_old_input_files.py still does not work #130

Open
Stevogallo opened this issue Apr 11, 2024 · 4 comments
Open

the function convert_old_input_files.py still does not work #130

Stevogallo opened this issue Apr 11, 2024 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@Stevogallo
Copy link
Collaborator

the function to create excel files, still reads in its "own memory", but not the input files in a specific path (try with a input_file_4.py and you'll see it does not recognize it)

@Bachibouzouk
Copy link
Collaborator

Meanwhile, if you need to produce excel file you can add

from ramp import UseCase
UseCase(users=User_list).save("<output fname of your wish>")

at the end of the .py files

(I used User_list as it is the name of the list of users in the example input files, but change it to whatever name this variable has in your code)

@FLomb
Copy link
Contributor

FLomb commented Jun 5, 2024

Thanks for the feedback @Stevogallo. I wonder, @Bachibouzouk, could this be because we fixed it in v0.5.1 but we didn't release it on Pypi?

Anyhow, we are about to make a new release that should solve all such issues (if I'm right that is just a problem of not having uploaded the release to Pypi)

@FLomb FLomb added the bug Something isn't working label Jun 5, 2024
@FLomb
Copy link
Contributor

FLomb commented Jun 5, 2024

Actually, this is still the case in the upcoming v0.5.2, so we'll need to make sure to fix it before we make the release. Thanks for spotting this, @Stevogallo. We'll keep you posted about the new release!

@FLomb
Copy link
Contributor

FLomb commented Jun 18, 2024

@Stevogallo, we should've fixed this in v0.5.2; would you like to test it on your machine?

From our tests, it seems like the issue may occasionally still occur depending on which Python version one uses or in which folder one tries to perform the operation (more precisely, there seems to be, in some rare cases, a difference between doing it within the RAMP folder, or outside of it). We have some ideas about how to work around this issue if it persists, but it would be good to know whether that's still the case for you. Thanks!

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

No branches or pull requests

3 participants