-
Notifications
You must be signed in to change notification settings - Fork 13
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
installing distgen from PyPi failed with six traceback #149
Comments
@frenzymadness Do you have any idea, what's going on? Even the system is clear from pypi package, then it failed with traceback. Or should we replace six with something different? |
The problem is during building manual pages which I think @praiskup knows more about. We should release universal wheels on PyPI so when users install distgen, they don't have to build their own. |
Hello! I believe this is due to using a legacy build system and not having a Worth giving it a shot, just add wheel as a requirement, and add
More here this is just a quick poetry version. UPDATE: The error message is probably OR instead of AND, therefore either add wheel as a requirement, OR add |
After further analysis with @duzda it seems that this happens in newer versions of pip, when required packages are not installed before calling pip install (including the This is very possibly due to new sandboxing of pip install. Due to how It tries to install this man page, regardless of whether it is installed via pip or RPM, but in case of pip it doesn't make sense. At least not anymore, since pip shouldn't be used to install system-wide packages, and mostly should be used inside virtual environments. The only possible purpose for man page would be in case of the RPM package, but that can be dealt with when building the RPM itself, and it shouldn't be done for PyPi. The ideal fix here would be to add Since this project is supposed to be onboarded to packit, there will be changes to RPM building process anyway and man page generation can be included. After discussing this issue with @phracek it is not an immediate concern as it still works on GitHub workflows and mac, supposedly because of an outdated version of pip, but that is only temporary. I will be making PR with a fix that will disable man page generation for now, and will solve this issue. |
I think we are mixing a lot of stuff here together. |
Could we stop using six? |
This drops the compatibility with Python 2.7, this should be OK (EPEL 7 is EOL). Fixes: devexp-db#149
This drops the compatibility with Python 2.7 which should be OK (EPEL 7 is EOL). Fixes: devexp-db#149
This drops the compatibility with Python 2.7 which should be OK (EPEL 7 is EOL). Fixes: devexp-db#149
If we don't have to support Python 2 anymore, yes, sure. |
I'm all for removing support for python 2, which is potentially not needed anymore. There is no reason to hold onto it. At the same time I am not particularly happy calling that a solution to this problem, because the problem seems to be in dependencies not being available during parts of the build and that is probably due to bad configuration of Removing the dependency that isn't available despite it should be will very probably resolve the error message, but I feel like it doesn't really fix the issue. |
Yeah, I'm not personally interested in the build-system cleanup work now (even though it might be worth it, thank you for taking a look). I want to make it installable (fixing the original report). As for the switch to Poetry, my (not important, really) vote is -1. Setuptools always seemed to be more powerful to me. Yet I'm +1 for moving the project from |
I think it was only supposed to be an example of I have this in my backlog and would like to address this issue together with the packit migration, just not sure when I will be able to do so. Also, I agree that the package should be installable asap, and is a more pressing matter right now. Is the solution of removing |
Yes, I didn't mean to propose Other than that, this is imo the correct solution.
|
Reopening because merging #150 didn't fix the issue, package is still not installable via pip. We just replaced it failing on dependency |
Yeah, we are probably unable to specify build deps. This code movement would probably fix the installation problem itself, don't you want to submit that as a separate pull-request? |
I feel like all the changes are kinda linked together. That code move will remove support for using I feel like the migration to |
I meant the move of the argument parser into a separate file; that would itself fix the overall problem (IOW no jinja2 or any other third-party is needed when generating the manual page). Also, there's |
On Fedora host machine, I would like to install distgen by 'pip3 install distgen --upgrade' but it failed
with
The text was updated successfully, but these errors were encountered: