Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Using the raw Python installation method only installs 1.0.0
See original GitHub issueDescribe the bug I am unable to use PyFunceble, because trying to install or update PyFunceble, through the “pure Python” methods that are described in the installation and update guides, isn’t going all that well. This is because it only installs 1.0.0 instead of 1.8.0, and then refuses to run due to a message that tells me to update PyFunceble, which I can’t.
Modifications under .PyFunceble.yaml
No changes that I know about.
To Reproduce Steps to reproduce the behavior:
- cd into a PyFunceble folder (Presumably one that has been set up with the “pure Python” installation method).
- Run
git checkout master && git fetch origin && git merge origin/master - See that it gets updated, or that it says that it’s fully updated already.
- Run
pyfunceble -v - See that it says
pyfunceble 1.0.0. (Blue Bontebok)
Expected behavior A clear and concise description of what you expected to happen.
Screenshots
Versions (please complete the following information):
- OS: Windows 10 October 2018 Update (Last installed update: KB4487044)
- Python Version: 3.6.4
- PyFunceble Version: 1.0.0 (in use), 1.8.0 (the one that I can’t update to)
Additional context
I am unable to test with either of the pip3 methods, because of something of some sort:
I have absolutely no idea how to get the new GitHub compressed-archive download method to work either, with this incomprehensible error being shown:
Issue Analytics
- State:
- Created 5 years ago
- Comments:21 (10 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Okay that System is not registered into the source Code that’s why you got that
CURRENT_DIRECTORY not founderror 😃Have to document myself about it and will include it 😃 Might be faster than Fixing for PowerShell !
Anyway, I’m going to bed (Berlin Time). Will look at those when I have some spare time in the coming days.
Thanks again for creating/maintaining/updating this issue.
Cheers, Nissar
To conclude my last comment (Did Ctrl+Enter by mistake). I thought that Windows was 100% supported but it is not the case. I’ll dig around that in the coming days now that I have a Windows 10 Partition.
Thanks for taking the time to report this @DandelionSprout. Will do my best to fix all the Windoof issues asap.
Cheers, Nissar