Closed emretezel closed 1 year ago
I believe this issue has been fixed in develop branch but not in master.
Correct. So why are you opening another issue for it?
If this is urgent for you, it should be safe to download the develop branch. I've been using it for several days with no issues.
We should all treat master as the production branch in my opinion and keep it stable.
Agreed, but also see A note on support
Thank you, I will wait until Rob merges latest develop changes into master, just being a little paranoid. Closing the issue.
Thanks for closing. Sorry if I was a bit harsh there.
Also, for anyone else seeing my comment about develop being good at the moment...there is one change in there that might cause problems for some people.
PR #1095 will cause config files to be read from the PYSYS_CODE directory if you have the environment variable defined. If your config files there are different from the config files installed in your python environment, you definitely do not want that.
I've recommended that Rob revert that pull request. I did not realize at the time that config files were being read from the Python environment (and that some people are even editing them directly in the Python environment).
Hi Everyone,
I believe this issue has been fixed in develop branch but not in master. Could the fix be pleased merged into master. We should all treat master as the production branch in my opinion and keep it stable.
The below messages pop out when running update_sampled_contracts in standard out