Re: [Tutor] How to install tensorflow on Python 2.7 in Windows?
On 6/26/24 09:29, marc nicole wrote: Browsing the available version of tensorflow for the dates before January 2021 (date when Python 2.7 stopped being supported) I can't find a tensorflow version for Python 2.7 that works under Windows. The reference site I use is https://pypi.org/project/tensorflow/ Anybody can point out a compatible .whl file with Python 2.7 and Windows? The last version of tensorflow to support Python 2.7 was indeed 2.1, and I don't think there was *ever* an official Windows wheel for Python 2, but I'm not that expert to be completely sure. tensorflow support on Windows has never been good, and in a way they've given up, at least part of the fight: they no longer produce official releases for Windows with GPU support (although you may be able to get one from the vendor that produces the GPU hardware like Nvidia or Intel, or from a third party like Amazon Web Services). The official recommendation for WIndows used to be "build your own" (which nearly always failed), then for a few years they tried making Windows builds, now the new "best practice" recommendation is to install on WSL if you want to run on a Windows box (this *might* work for you, unless you're also on an ancient Windows that won't run WSL). Or, try seeing if you can find a docker setup (which, again, will give you a Linux environment running tensorflow). Note that like your other problem, getting numpy going, this is going to be an uphill battle trying to cobble things together to run on 2.7. This is really the problem when something like Python goes out of date / out of support: it's not that it magically stops working, it's that vast amounts of the ecosystem around it stop providing support for *their* bits on the old version, and the combinations become progressively harder to make work. -- https://mail.python.org/mailman/listinfo/python-list
How to install tensorflow on Python 2.7 in Windows?
Browsing the available version of tensorflow for the dates before January 2021 (date when Python 2.7 stopped being supported) I can't find a tensorflow version for Python 2.7 that works under Windows. The reference site I use is https://pypi.org/project/tensorflow/ Anybody can point out a compatible .whl file with Python 2.7 and Windows? -- https://mail.python.org/mailman/listinfo/python-list
Re: Couldn't install numpy on Python 2.7
Hey, everyone! I believe the original question has been answered, and tempers seem to be flaring in sub-threads, so let's call this thread done and move on to other interesting topics. Thank you for your support! -- ~Ethan~ Moderator -- https://mail.python.org/mailman/listinfo/python-list
Re: Couldn't install numpy on Python 2.7
Chris Angelico wrote: > On Thu, 13 Jun 2024 at 10:58, wrote: > > > > Chris, > > > > You seem to have perceived an insult that I remain unaware of. > > If you're not aware that you're saying this, then don't say it. > Er, um, that really makes no sense! :-) How can one not say something that one isn't aware of saying? -- Chris Green · -- https://mail.python.org/mailman/listinfo/python-list
Re: Couldn't install numpy on Python 2.7
On Thu, 13 Jun 2024 at 10:58, wrote: > > Chris, > > You seem to have perceived an insult that I remain unaware of. If you're not aware that you're saying this, then don't say it. > I looked up FUD and sharply disagree with suggestions I am trying to somehow > cause Fear, Uncertainty or Doubt. I simply asked if another such update ... > as a hypothetical. Had I asked what impact Quantum Computers might have on > existing languages, would that also be FUD, or just a speculation in a > discussion. What DID you intend by your comments? Were you trying to imply that work spent upgrading to Python 3 would have to be redone any day now when this hypothetical massively-incompatible Python 4 is released? Or what? What WERE you trying to say? If you don't understand how damaging it can be to say that sort of thing, **don't say it**. Otherwise, expect responses like this. I *detest* the attitude that you can make vague disparaging comments and then hide behind claims that you had no idea how damaging you were being. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
RE: Couldn't install numpy on Python 2.7
Chris, You seem to have perceived an insult that I remain unaware of. I have no special knowledge, like you do, of plans made for changes to the pthon language and implementation. I was asking a hypothetical question about what some users would do if python came out with a newer major version. I have seen people often wait until some software that tries to get updated too frequently makes multiple updates and then finally give in and skip the intermediates. I wondered if something like a version 4.0 might get people still using version 2 might finally come around and also if some version 3 users would not be thrilled with something not stable enough. I have no favorite ideas here and can see a balance between adding features or fixing flaws and on the other side, not discomfiting many and especially when in many cases, the original people who wrote software are no longer there nor budgets to pay for changes. I looked up FUD and sharply disagree with suggestions I am trying to somehow cause Fear, Uncertainty or Doubt. I simply asked if another such update ... as a hypothetical. Had I asked what impact Quantum Computers might have on existing languages, would that also be FUD, or just a speculation in a discussion. Either way, I am taking any further discussion along these lines offline and will not continue here. -Original Message- From: Python-list On Behalf Of Chris Angelico via Python-list Sent: Wednesday, June 12, 2024 7:23 PM To: python-list@python.org Subject: Re: Couldn't install numpy on Python 2.7 On Thu, 13 Jun 2024 at 09:20, wrote: > My point was that version 4 COULD HAPPEN one day and I meant INCOMPATIBLE > version not 4. Obviously we can make a version 4 that is not incompatible > too. This is still FUD. Back your words with something, or stop trying to imply that there's another incompatible change just around the corner. Do you realise how insulting you are being to the developers of Python by these implications? ChrisA -- https://mail.python.org/mailman/listinfo/python-list -- https://mail.python.org/mailman/listinfo/python-list
Re: Couldn't install numpy on Python 2.7
On Thu, 13 Jun 2024 at 09:20, wrote: > My point was that version 4 COULD HAPPEN one day and I meant INCOMPATIBLE > version not 4. Obviously we can make a version 4 that is not incompatible > too. This is still FUD. Back your words with something, or stop trying to imply that there's another incompatible change just around the corner. Do you realise how insulting you are being to the developers of Python by these implications? ChrisA -- https://mail.python.org/mailman/listinfo/python-list
RE: Couldn't install numpy on Python 2.7
Chris, I don't want to get off message and debate whether my "jokes" are jokes, let alone funny. Obviously, they often aren't. What I meant by joking here does seem relevant. As the years pass, there can come a time when it is suggested that a language (any language including python) is no longer useful to many in the community as it has not kept up with changes in the industry or whatever. Suggestions are made for changes and additions that that not be backward compatible. They can be somewhat minor things like new keywords that have not been reserved and where programs that exist might be scanned for use of that keyword, and you simply replace those names with was_keyword or something and the programs will generally run. But there can be major changes too and there can be a choice to just create a new language that has some similarities to python 3 (or PERL version whatever) or just name it the same but a version higher much like has happened. My point was that version 4 COULD HAPPEN one day and I meant INCOMPATIBLE version not 4. Obviously we can make a version 4 that is not incompatible too. I have experience in other languages where disconnects happen at various levels. Some functions in a collection such as a package are removed perhaps to replace them with a more abstract version that does much more. Do you remove the old one immediately or do you make a new name for the new one and perhaps in some way mark the old one for deprecation with a pointer to the new one to be used as soon as reasonable? I have seen many approaches. I have seen entire packages yanked. I have seen parts that used to be in the distribution as if built-in and then taken out and vice versa. The point is you do not need a 4.0 to be incompatible. The incompatibility, or need to change, can happen anytime when you are importing things like numpy which is released whenever they want to and is not part of the python distribution. Also, as we have seen at times, other modules you may have imported, in some languages, can mask names you are using in your program that you may not even be aware are there. Much can go wrong with software and keeping current can also give you problems when something released may have inadvertent changes or bugs. So much of our code is voluntary and as noted earlier, some python variants/distributions simply may not have anyone interested in keeping them up to date. You as a user, take your chances. -Original Message- From: Python-list On Behalf Of Chris Angelico via Python-list Sent: Wednesday, June 12, 2024 5:52 PM To: python-list@python.org Subject: Re: Couldn't install numpy on Python 2.7 On Thu, 13 Jun 2024 at 07:36, wrote: > But if the goal was to deprecate python 2 and in some sense phase it out, it > is perhaps not working well for some. Frankly, issuing so many updates like > 2.7 and including backporting of new features has helped make it possible to > delay any upgrade. The goal was to improve Python. I don't think anyone's ever tried to "kill off" Python 2 - not in the sense of stopping people from using it - but there haven't been any changes, not even security fixes, in over four years. > And, yes, I was KIDDING about python 4. I am simply suggesting that there > may well be a time that another shift happens that may require another > effort to get people on board a new and perhaps incompatible setup. Kidding, eh? It sure sounded like you were trying to imply that there would inevitably be another major breaking change. It definitely smelled like FUD. Maybe your jokes just aren't funny. ChrisA -- https://mail.python.org/mailman/listinfo/python-list -- https://mail.python.org/mailman/listinfo/python-list
Re: Couldn't install numpy on Python 2.7
On Wed, 12 Jun 2024 at 23:52, Greg Ewing via Python-list wrote: > On 13/06/24 10:09 am, Chris Angelico wrote: > > So if anyone > > actually does need to use pip with Python 2.7, they probably need to > > set up a local server > > You should also be able to download a .tar.gz from PyPI and use pip > to install that. Although you'll have to track down the dependencies > yourself in that case. It is almost certainly better to download the wheel (.whl) file rather than the sdist (.tar.gz) file. Building NumPy from source needs not just compilers etc but also you first need to build/install a BLAS library. -- Oscar -- https://mail.python.org/mailman/listinfo/python-list
Re: Couldn't install numpy on Python 2.7
On Thu, 13 Jun 2024 at 08:46, Oscar Benjamin via Python-list wrote: > I don't know much about SSL and related networking things especially > on Windows. I would be surprised if pip on old Python can't install > from current PyPI though. I imagine that something strange has > happened like a new version of pip running on an old version of Python > or old Python on new OS (or old PyCharm...). > > There is no problem using Python 2.7 with pip and PyPI on this Linux > machine but I guess it has a newer SSL library provided by the OS: Sadly, I would NOT be surprised if this is indeed a problem on Windows. You're exactly right - on Linux, it can use a newer SSL library from the OS. Of course, this does assume that you've updated your OS, which is far from a guarantee, but since this has security implications there's a good chance you can update it while retaining a legacy system. On Thu, 13 Jun 2024 at 08:51, Greg Ewing via Python-list wrote: > On 13/06/24 10:09 am, Chris Angelico wrote: > > So if anyone > > actually does need to use pip with Python 2.7, they probably need to > > set up a local server > > You should also be able to download a .tar.gz from PyPI and use pip > to install that. Although you'll have to track down the dependencies > yourself in that case. Also a possibility; in my opinion, losing dependency management is too big a cost, so I would be inclined to set up a local server. But then, I would be using a newer SSL library and not have the problem in the first place. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: Couldn't install numpy on Python 2.7
On 13/06/24 4:31 am, avi.e.gr...@gmail.com wrote: It seems Microsoft is having a problem where something lik 2/3 of Windows users have not upgraded from Windows 10 after many years At least Python 3 is a clear improvement over Python 2 in many ways. Whereas the only thing Microsoft seems to have done with Windows in recent times is change it in ways that nobody wants, so there is understandable resistance to upgrading even if it's possible. On 13/06/24 10:09 am, Chris Angelico wrote: > So if anyone > actually does need to use pip with Python 2.7, they probably need to > set up a local server You should also be able to download a .tar.gz from PyPI and use pip to install that. Although you'll have to track down the dependencies yourself in that case. -- Greg -- https://mail.python.org/mailman/listinfo/python-list
Re: Couldn't install numpy on Python 2.7
On Wed, 12 Jun 2024 at 23:11, Chris Angelico via Python-list wrote: > > On Thu, 13 Jun 2024 at 07:57, Oscar Benjamin via Python-list > wrote: > > They are seeing a warning that explicitly says "You can upgrade to a > > newer version of Python to solve this". I don't know whether that SSL > > warning is directly connected to pip not finding any versions of numpy > > but with the available information so far that seems like the first > > thing to consider. > > I think it is; AIUI, with an ancient SSL library, pip is unable to > download packages safely from the current pypi server. So if anyone > actually does need to use pip with Python 2.7, they probably need to > set up a local server, using older encryption protocols (which should > therefore NOT be made accessible to the internet). Since pip can't > contact the upstream pypi, there's no available numpy for it to > install. I don't know much about SSL and related networking things especially on Windows. I would be surprised if pip on old Python can't install from current PyPI though. I imagine that something strange has happened like a new version of pip running on an old version of Python or old Python on new OS (or old PyCharm...). There is no problem using Python 2.7 with pip and PyPI on this Linux machine but I guess it has a newer SSL library provided by the OS: $ pip install numpy DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support pip 21.0 will remove support for this functionality. Collecting numpy Downloading numpy-1.16.6-cp27-cp27mu-manylinux1_x86_64.whl (17.0 MB) || 17.0 MB 14.3 MB/s Installing collected packages: numpy Successfully installed numpy-1.16.6 If it is actually the case that pip on Python 2.7 (on Windows) cannot download from PyPI then an easier option rather than creating a local server would just be to download the numpy wheels from PyPI using a browser: https://pypi.org/project/numpy/1.15.4/#files Then you can do pip install .\numpy-1.15.4-cp27-none-win_amd64.whl Using a newer version of Python is still my primary suggestion though. -- Oscar -- https://mail.python.org/mailman/listinfo/python-list
Re: Couldn't install numpy on Python 2.7
On Thu, 13 Jun 2024 at 07:57, Oscar Benjamin via Python-list wrote: > They are seeing a warning that explicitly says "You can upgrade to a > newer version of Python to solve this". I don't know whether that SSL > warning is directly connected to pip not finding any versions of numpy > but with the available information so far that seems like the first > thing to consider. I think it is; AIUI, with an ancient SSL library, pip is unable to download packages safely from the current pypi server. So if anyone actually does need to use pip with Python 2.7, they probably need to set up a local server, using older encryption protocols (which should therefore NOT be made accessible to the internet). Since pip can't contact the upstream pypi, there's no available numpy for it to install. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: Couldn't install numpy on Python 2.7
On Wed, 12 Jun 2024 at 22:38, AVI GROSS via Python-list wrote: > > The discussion though was about a specific OP asking if they can fix their > problem. One solution being suggested is to fix a deeper problem and simply > make their code work with a recent version of python 3. The OP has not replied with any explanation as to why they are using Python 2.7 and has not said whether they have any existing code that only works with Python 2.7. It is unclear at this point whether there is any reason that they shouldn't just install a newer version of Python. They are seeing a warning that explicitly says "You can upgrade to a newer version of Python to solve this". I don't know whether that SSL warning is directly connected to pip not finding any versions of numpy but with the available information so far that seems like the first thing to consider. It is entirely reasonable to start by suggesting to use a newer version of Python until some reason is given for not doing that. -- Oscar -- https://mail.python.org/mailman/listinfo/python-list
Re: Couldn't install numpy on Python 2.7
On Thu, 13 Jun 2024 at 07:36, wrote: > But if the goal was to deprecate python 2 and in some sense phase it out, it > is perhaps not working well for some. Frankly, issuing so many updates like > 2.7 and including backporting of new features has helped make it possible to > delay any upgrade. The goal was to improve Python. I don't think anyone's ever tried to "kill off" Python 2 - not in the sense of stopping people from using it - but there haven't been any changes, not even security fixes, in over four years. > And, yes, I was KIDDING about python 4. I am simply suggesting that there > may well be a time that another shift happens that may require another > effort to get people on board a new and perhaps incompatible setup. Kidding, eh? It sure sounded like you were trying to imply that there would inevitably be another major breaking change. It definitely smelled like FUD. Maybe your jokes just aren't funny. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
RE: Couldn't install numpy on Python 2.7
Chris, Since you misunderstood, my statement was that making an incompatible set of changes to create Python 3 in the first place was a decision made by some and perhaps not one that thrilled others who already had an embedded base of programs or ones in the pipeline that would need much work to become comparable. And, of course, users of a program who continued to use python 2, also have to find a way to ... But if the goal was to deprecate python 2 and in some sense phase it out, it is perhaps not working well for some. Frankly, issuing so many updates like 2.7 and including backporting of new features has helped make it possible to delay any upgrade. And, yes, I was KIDDING about python 4. I am simply suggesting that there may well be a time that another shift happens that may require another effort to get people on board a new and perhaps incompatible setup. I have seen things like that happen in multiple phases including phases where the new tools are not an upgrade, but brand new. An example might be if accompany decided to switch to another existing language because they want better error detection and faster execution or new features that may take forever to arrive in what they are using or that supply various services by humans to help them. The discussion though was about a specific OP asking if they can fix their problem. One solution being suggested is to fix a deeper problem and simply make their code work with a recent version of python 3. But another solution could be to step backward to a version of python 2 that still has numpy support, or as was suggested, find out what other modules they are using are interfering with the program being satisfied with the last version of numpy being used and perhaps find a way to get ... In the long run, though, continuing with python 2 will likely cause ever more such headaches if you want the latest and greatest of things like numpy. -Original Message- From: Python-list On Behalf Of Chris Angelico via Python-list Sent: Wednesday, June 12, 2024 2:00 PM To: python-list@python.org Subject: Re: Couldn't install numpy on Python 2.7 On Thu, 13 Jun 2024 at 03:41, AVI GROSS via Python-list wrote: > > Change is hard even when it may be necessary. > > The argument often is about whether some things are necessary or not. > > Python made a decision but clearly not a unanimous one. What decision? To not release any new versions of Python 2? That isn't actually the OP's problem here - the Python interpreter runs just fine. But there's no numpy build for the OP's hardware and Python 2.7. So if you want to complain about Python 2.7 being dead, all you have to do is go through all of the popular packages and build binaries for all modern computers. If that sounds easy, go ahead and do it; if it sounds hard, realise that open source is not a democracy, and you can't demand that other people do more and more and more unpaid work just because you can't be bothered upgrading your code. > My current PC was not upgradable because of the new hardware requirement > Microsoft decided was needed for Windows 11. Yes, and that's a good reason to switch to Linux for the older computer. > I mention this in the context of examples of why even people who are fairly > knowledgeable do not feel much need to fix what does not feel broken. It doesn't feel broken, right up until it does. The OP has discovered that it *IS* broken. Whining that it doesn't "feel broken" is nonsense when it is, in fact, not working. > When is Python 4 coming? Is this just another content-free whine, or are you actually curious about the planned future of Python? If the latter, there is **PLENTY** of information out there and I don't need to repeat it here. Please don't FUD. ChrisA -- https://mail.python.org/mailman/listinfo/python-list -- https://mail.python.org/mailman/listinfo/python-list
Re: Couldn't install numpy on Python 2.7
On Thu, 13 Jun 2024 at 06:55, Thomas Passin via Python-list wrote: > The project cannot move to a Python-3 compatible version because Jython > 3.xx doesn't exist and may never exist. The saving grace is that my > project doesn't have to use packages like numpy, scipy, and so forth. Exactly. If you don't need to ALSO use something newer, there's nothing stopping you from continuing with the old version. And that's fine! As long as you're okay with not getting updates, you're welcome to do whatever you like - including running Windows 98 on an ancient PC and editing your documents on that. (Yes, I know someone who did that, long after Win 98 was dead to most of us.) > Thunderbird and everything else worked perfectly for me during that > week. True, there were a few Windows-only programs I missed, but I used > other similar programs even if I didn't like them as much. It's true. And there ARE solutions to that, although it's a bit rough trying to run them on low hardware (Wine works nicely for some programs, less so for others; VirtualBox is really not gonna be happy with a small fraction of your limited RAM). But if your needs are simple, even a crazily low-end system is sufficient. > It's amazing > how little resources Linux installs need, even with a GUI. Of course, > 4GB RAM is limiting whether you are on Linux or Windows - you can't > avoid shuffling all those GUI bits around - but with a little care it > worked great. And with the external SSD the laptop was a lot snappier > than it ever was when it was new. One of the big differences with Linux is that you have a choice of desktop environments, from "none" (just boot straight into a terminal) on up. Some of them are a bit of a compromise in terms of how well you can get your work done, but let's say you had an even MORE ancient system with maybe one gig of memory... I'd rather have a super-light desktop environment even if it doesn't have everything I'm normally accustomed to! ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: Couldn't install numpy on Python 2.7
On 6/12/2024 1:59 PM, Chris Angelico via Python-list wrote: On Thu, 13 Jun 2024 at 03:41, AVI GROSS via Python-list wrote: Change is hard even when it may be necessary. The argument often is about whether some things are necessary or not. Python made a decision but clearly not a unanimous one. What decision? To not release any new versions of Python 2? That isn't actually the OP's problem here - the Python interpreter runs just fine. But there's no numpy build for the OP's hardware and Python 2.7. So if you want to complain about Python 2.7 being dead, all you have to do is go through all of the popular packages and build binaries for all modern computers. If that sounds easy, go ahead and do it; if it sounds hard, realise that open source is not a democracy, and you can't demand that other people do more and more and more unpaid work just because you can't be bothered upgrading your code. I support a Tomcat project that has some java code and most of the code is for Jython 2.7. Jython 2.7 is approximately on a par with Python 2.7. Any Python-only code from the standard library will probably run, but of course any C extensions cannot. The nice thing about using Jython in a java environment is that it can call any java object, and java code can call Jython objects and their methods. The project cannot move to a Python-3 compatible version because Jython 3.xx doesn't exist and may never exist. The saving grace is that my project doesn't have to use packages like numpy, scipy, and so forth. Also, the project is very mature and almost certainly won't need to create functionality such packages would enable. It would be nice to be able to use some newer parts of the standard library, but there it is. Jython does support "from __future__ import" and I make use of that for the print function and the like. My current PC was not upgradable because of the new hardware requirement Microsoft decided was needed for Windows 11. Yes, and that's a good reason to switch to Linux for the older computer. I have a 2012-vintage laptop that in modern terms has a very small supply of RAM and a very slow hard drive. When my newer Windows 10 computer was going to be out of service for a while, I put a Linux distro on an external SSD and copied things I needed to work on to it, including my Thunderbird email profile directory. Thunderbird and everything else worked perfectly for me during that week. True, there were a few Windows-only programs I missed, but I used other similar programs even if I didn't like them as much. It's amazing how little resources Linux installs need, even with a GUI. Of course, 4GB RAM is limiting whether you are on Linux or Windows - you can't avoid shuffling all those GUI bits around - but with a little care it worked great. And with the external SSD the laptop was a lot snappier than it ever was when it was new. I mention this in the context of examples of why even people who are fairly knowledgeable do not feel much need to fix what does not feel broken. It doesn't feel broken, right up until it does. The OP has discovered that it *IS* broken. Whining that it doesn't "feel broken" is nonsense when it is, in fact, not working. When is Python 4 coming? Is this just another content-free whine, or are you actually curious about the planned future of Python? If the latter, there is **PLENTY** of information out there and I don't need to repeat it here. Please don't FUD. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: Couldn't install numpy on Python 2.7
On Thu, 13 Jun 2024 at 03:41, AVI GROSS via Python-list wrote: > > Change is hard even when it may be necessary. > > The argument often is about whether some things are necessary or not. > > Python made a decision but clearly not a unanimous one. What decision? To not release any new versions of Python 2? That isn't actually the OP's problem here - the Python interpreter runs just fine. But there's no numpy build for the OP's hardware and Python 2.7. So if you want to complain about Python 2.7 being dead, all you have to do is go through all of the popular packages and build binaries for all modern computers. If that sounds easy, go ahead and do it; if it sounds hard, realise that open source is not a democracy, and you can't demand that other people do more and more and more unpaid work just because you can't be bothered upgrading your code. > My current PC was not upgradable because of the new hardware requirement > Microsoft decided was needed for Windows 11. Yes, and that's a good reason to switch to Linux for the older computer. > I mention this in the context of examples of why even people who are fairly > knowledgeable do not feel much need to fix what does not feel broken. It doesn't feel broken, right up until it does. The OP has discovered that it *IS* broken. Whining that it doesn't "feel broken" is nonsense when it is, in fact, not working. > When is Python 4 coming? Is this just another content-free whine, or are you actually curious about the planned future of Python? If the latter, there is **PLENTY** of information out there and I don't need to repeat it here. Please don't FUD. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
RE: Couldn't install numpy on Python 2.7
Change is hard even when it may be necessary. The argument often is about whether some things are necessary or not. Python made a decision but clearly not a unanimous one. My current PC was not upgradable because of the new hardware requirement Microsoft decided was needed for Windows 11. I bought a new one a while back and turned it on in another room and then set it aside because replacing the current one in the current position will be a pain, especially with getting all my wires and so on, and since I do not want to use a full copy of my data including many obsolete things, that will be another pain to get what I need, if I can remember. Complicating issues also include licenses for things in fixed amounts and the likelihood of messing up the hardware/software I have that records shows from cable to my hard disk, possibly needing to buy a new one. I mention this in the context of examples of why even people who are fairly knowledgeable do not feel much need to fix what does not feel broken. I have wondered if instead of doing what Microsoft wants, if maybe switching to Linux of some kinds makes as much sense. I suspect some may simply upgrade to an Apple product. And think of all the PC's that may effectively be discarded as they may not even be usable if donated. We live in a rapidly developing age and hence one with regularly and irregularly scheduled rounds of obsolescence. When is Python 4 coming? -Original Message- From: Python-list On Behalf Of MRAB via Python-list Sent: Wednesday, June 12, 2024 12:56 PM To: python-list@python.org Subject: Re: Couldn't install numpy on Python 2.7 On 2024-06-12 17:31, AVI GROSS via Python-list wrote: > I am sure there is inertia to move from an older product and some people > need a reason like this where the old becomes untenable. > > It seems Microsoft is having a problem where something lik 2/3 of Windows > users have not upgraded from Windows 10 after many years and have set a > deadline in a year or so for stopping updates. In that case, hardware was a > concern for some as Windows 11 did not work on their machines. With > upgrading python, the main concern is having to get someone to examine old > code and try to make it compatible. > In the case of Windows, my PC is over 10 years old yet performs perfectly well for my needs. It can't run Windows 11. Therefore, I'm in the process of migrating to Linux, and I still have over a year to achieve that before support ends. > But anyone doing new code in Python 2 in recent years should ... > Indeed... > -Original Message- > From: Python-list On > Behalf Of Gordinator via Python-list > Sent: Wednesday, June 12, 2024 10:19 AM > To: python-list@python.org > Subject: Re: Couldn't install numpy on Python 2.7 > > On 12/06/2024 12:30, marc nicole wrote: >> I am trying to install numpy library on Python 2.7.15 in PyCharm but the >> error message I get is: >> >> ERROR: Could not find a version that satisfies the requirement numpy (from >>> versions: none) >>> ERROR: No matching distribution found for numpy >>> c:\python27\lib\site-packages\pip\_vendor\urllib3\util\ssl_.py:164: >>> InsecurePlatformWarning: A true SSLContext object is not available. This >>> prevents urllib3 fro >>> m configuring SSL appropriately and may cause certain SSL connections to >>> fail. You can upgrade to a newer version of Python to solve this. For > more >>> information, see >>> https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings >>>InsecurePlatformWarning, >> >> >> Any clues? > > Why are you using Python 2? Come on, it's been 16 years. Ya gotta move > on at some point. -- https://mail.python.org/mailman/listinfo/python-list -- https://mail.python.org/mailman/listinfo/python-list
Re: Couldn't install numpy on Python 2.7
On 2024-06-12 17:31, AVI GROSS via Python-list wrote: I am sure there is inertia to move from an older product and some people need a reason like this where the old becomes untenable. It seems Microsoft is having a problem where something lik 2/3 of Windows users have not upgraded from Windows 10 after many years and have set a deadline in a year or so for stopping updates. In that case, hardware was a concern for some as Windows 11 did not work on their machines. With upgrading python, the main concern is having to get someone to examine old code and try to make it compatible. In the case of Windows, my PC is over 10 years old yet performs perfectly well for my needs. It can't run Windows 11. Therefore, I'm in the process of migrating to Linux, and I still have over a year to achieve that before support ends. But anyone doing new code in Python 2 in recent years should ... Indeed... -Original Message- From: Python-list On Behalf Of Gordinator via Python-list Sent: Wednesday, June 12, 2024 10:19 AM To: python-list@python.org Subject: Re: Couldn't install numpy on Python 2.7 On 12/06/2024 12:30, marc nicole wrote: I am trying to install numpy library on Python 2.7.15 in PyCharm but the error message I get is: ERROR: Could not find a version that satisfies the requirement numpy (from versions: none) ERROR: No matching distribution found for numpy c:\python27\lib\site-packages\pip\_vendor\urllib3\util\ssl_.py:164: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 fro m configuring SSL appropriately and may cause certain SSL connections to fail. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings InsecurePlatformWarning, Any clues? Why are you using Python 2? Come on, it's been 16 years. Ya gotta move on at some point. -- https://mail.python.org/mailman/listinfo/python-list
RE: Couldn't install numpy on Python 2.7
I am sure there is inertia to move from an older product and some people need a reason like this where the old becomes untenable. It seems Microsoft is having a problem where something lik 2/3 of Windows users have not upgraded from Windows 10 after many years and have set a deadline in a year or so for stopping updates. In that case, hardware was a concern for some as Windows 11 did not work on their machines. With upgrading python, the main concern is having to get someone to examine old code and try to make it compatible. But anyone doing new code in Python 2 in recent years should ... -Original Message- From: Python-list On Behalf Of Gordinator via Python-list Sent: Wednesday, June 12, 2024 10:19 AM To: python-list@python.org Subject: Re: Couldn't install numpy on Python 2.7 On 12/06/2024 12:30, marc nicole wrote: > I am trying to install numpy library on Python 2.7.15 in PyCharm but the > error message I get is: > > ERROR: Could not find a version that satisfies the requirement numpy (from >> versions: none) >> ERROR: No matching distribution found for numpy >> c:\python27\lib\site-packages\pip\_vendor\urllib3\util\ssl_.py:164: >> InsecurePlatformWarning: A true SSLContext object is not available. This >> prevents urllib3 fro >> m configuring SSL appropriately and may cause certain SSL connections to >> fail. You can upgrade to a newer version of Python to solve this. For more >> information, see >> https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings >>InsecurePlatformWarning, > > > Any clues? Why are you using Python 2? Come on, it's been 16 years. Ya gotta move on at some point. -- https://mail.python.org/mailman/listinfo/python-list -- https://mail.python.org/mailman/listinfo/python-list
Re: Couldn't install numpy on Python 2.7
On 12/06/2024 12:30, marc nicole wrote: I am trying to install numpy library on Python 2.7.15 in PyCharm but the error message I get is: ERROR: Could not find a version that satisfies the requirement numpy (from versions: none) ERROR: No matching distribution found for numpy c:\python27\lib\site-packages\pip\_vendor\urllib3\util\ssl_.py:164: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 fro m configuring SSL appropriately and may cause certain SSL connections to fail. You can upgrade to a newer version of Python to solve this. For more information, see https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings InsecurePlatformWarning, Any clues? Why are you using Python 2? Come on, it's been 16 years. Ya gotta move on at some point. -- https://mail.python.org/mailman/listinfo/python-list
Re: Couldn't install numpy on Python 2.7
On Wed, 12 Jun 2024 at 21:32, marc nicole via Python-list wrote: > > I am trying to install numpy library on Python 2.7.15 in PyCharm but the > error message I get is: > > You can upgrade to a newer version of Python to solve this. The answer is right there in the error message. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Couldn't install numpy on Python 2.7
I am trying to install numpy library on Python 2.7.15 in PyCharm but the error message I get is: ERROR: Could not find a version that satisfies the requirement numpy (from > versions: none) > ERROR: No matching distribution found for numpy > c:\python27\lib\site-packages\pip\_vendor\urllib3\util\ssl_.py:164: > InsecurePlatformWarning: A true SSLContext object is not available. This > prevents urllib3 fro > m configuring SSL appropriately and may cause certain SSL connections to > fail. You can upgrade to a newer version of Python to solve this. For more > information, see > https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings > InsecurePlatformWarning, Any clues? -- https://mail.python.org/mailman/listinfo/python-list
Cannot install python properly - python310.dll not found - no pip
Hi. I'm attempting to install and use stable diffusion. However, while installing python 3.10.6, I'm getting the error that the python 310.dll is not found. I've made sure the PATH option is enabled, but it makes no difference. I've also removed and reinstalled python multiple times. Even though I get that error, the python still installs, but when I open the webui-user.bat file in the stable diffusion folder, it opens up the command center and says that there's no module named pip. Please advise on how to fix this problem. Thank you, Jay Cadet Architectural 3D Artist / Photographer studio JPC [p] 516.567.1996 | [w] studiojpc.com<http://studiojpc.com> | [ig] @studiojpc -- https://mail.python.org/mailman/listinfo/python-list
CoC Warning [was: What is Install-Paths-To in WHEEL file?]
On 12/29/23 05:02, Left Right via Python-list wrote: Wow. That place turned out to be the toxic pit I didn't expect. It's a shame that a public discussion of public goods was entrusted to a bunch of gatekeepers with no sense of responsibility for the thing they keep the keys to. Personal attacks are not welcome nor tolerated. Please be constructive when engaging with the community. -- ~Ethan~ -- https://mail.python.org/mailman/listinfo/python-list
[dead thread] Re: What is Install-Paths-To in WHEEL file?
This thread is no longer being useful, and is now closed. -- ~Ethan~ Moderator -- https://mail.python.org/mailman/listinfo/python-list
Re: What is Install-Paths-To in WHEEL file?
> others do not and so your notion of what is "accepted" > is not universally shared. Why should I or anyone else care about what "others" think? The important question is whether what I do is right. And the answer is "yes". That's why there are rules in the first place instead of polling. > if you want to influence anything Usually, when I interact with representatives of Python community I have two goals: 1. Typically, I need to show to someone who's paying my salary why something produced by this community doesn't work. I.e. say, I need to convince a project manager on a project I'm helping maintain that deploying using "pip install" is a bad idea. I write an explanation which I share with the PM and the PyPA people in the bug tracker. They predictably block me out of fear or frustration. This gives me a proof that the thing doesn't work (well), and I'm allowed to do it the right way. Just like in your previous remark: majority could be a good initial heuristic, but proof is still a lot better. 2. At this point, I have no hope of convincing the prominent members of Python community how awful a lot of their decisions are. There are plenty of socially constructed obstacles on this way. The reason I do this is posterity. There are plenty of people who aren't influenced by the internal developments of Python community (outside of it) and they can see much of its development for what it is: commenting on this development honestly will help them make an informed choice. It's also important that those who will come after us will learn about this contradiction. Too many bad projects with bad design outlived their good counterparts due to popularity caused by chance. And today those better design and ideas are as good as lost. For example, Unix outlived and "overpowered" plenty of better operating systems of its time. But most programmers today would have no idea what those systems were and how they were different. Similarly, x86 ISA. And plenty more. Python changed from its early days of trying to be funny and generally welcoming of many contradicting ideas and opinions into a Lord of the Flies community that no longer tolerates differences of opinion. It's lost the spirit of "playful cleverness" (as RMS would put it), and became a "don't think, do as I say" community. I want to make sure those who come to learn about Python will not miss this aspect of its history. -- https://mail.python.org/mailman/listinfo/python-list
Re: What is Install-Paths-To in WHEEL file?
On Sun, 31 Dec 2023 at 00:35, Left Right wrote: > > It's not for you to choose the way I communicate. There are accepted > boundaries, and I'm well within those boundaries. Anything beyond that > is not something I'm even interested in hearing your opinion on. You might not be interested in my opinion but you might want to reflect on the fact that although you consider your behavior to be within "accepted boundaries" the evidence here (and in the forum) suggests that others do not and so your notion of what is "accepted" is not universally shared. I am not going to reply to your other points except to say that if you want to influence anything then I expect that you would have more success with a different approach. To anyone else considering replying in this thread: please don't. I very much doubt that anything good will happen here. -- Oscar -- https://mail.python.org/mailman/listinfo/python-list
Re: What is Install-Paths-To in WHEEL file?
> You are conflating several different groups of people. The PyPA are > the people who currently maintain the code for various > libraries/tools. That is very often not the same as the people who > originally wrote the code for the same libraries/tools or for > preceding ones. Neither group is the same as the forum moderators (I > suspect that there is no intersection between the moderators and the > PyPA etc.). I'm sorry to tell you, but you suspect wrong. Unfortunately, it's always the same story. Whenever I or anyone else with a legitimate complaint about larger projects managed by PyPA tries to bring this to public discussion, they get banned and their comments about PyPA activity removed. It's always presented as if whoever is complaining is disrespecting the hard work of the person replying, who usually self-describe as selfless volunteer with limited time and attention they are willing to grant to the one complaining (implying they either are PyPA or are volunteering for them). As if their time was obviously more important than that was spent by the one complaining to research the problem and put together the complaint. This has nothing to do with the original authors of the projects managed by PyPA. I don't know why you decided to bring this up. I haven't mentioned them. > Actually you are wasting the time of others by putting across > inaccurate and unhelpful information in a rude way and at the same > time criticising others without really understanding who you are > criticising and for what. Your contribution is unhelpful mostly (but > not exclusively) because of the way that you choose to communicate. No, I'm not _wasting_ anyone's time. I bring up a legitimate issue that needs solving. What happens is a typical example of gatekeeping, overestimating one's worth or the value of one's contribution. The time I had to waste because of the bad decisions made by PyPA is orders of magnitude more than the time they have spent reading whatever I wrote to them. Point me to inaccurate information please. I'm happy to be corrected. Similarly, point me to where I was rude, and I will apologize. Apparently, I have a better understanding of who I criticize and for what than you do. You need to at least be factual when you make these sorts of claims. It's not for you to choose the way I communicate. There are accepted boundaries, and I'm well within those boundaries. Anything beyond that is not something I'm even interested in hearing your opinion on. > There is some significant irony in you describing the forum as a > "toxic pit" for deleting your posts. I don't always agree with the > moderators and I am not sure that I would have reacted the way that > they did but these threads remind me precisely why moderation > (including deleting posts such as yours) is needed to *prevent* a > forum from turning into a toxic pit. You, as well as the moderators of the toxic pit forum are confused about what it means to have a good discussion. The discussion that is currently happening around PyPA projects and ideas is broken because the PyPA side of the discussion is unwilling to acknowledge how bad they are at doing their job. Whenever any serious criticism of their work surfaces, they deal with it by deleting the criticism, never through addressing the problem. You can be the most polite and humble person in the world, but as soon as you bring up the subject of the quality of their decisions, you are automatically excluded from discussion. The only criticism anyone is allowed to have is the kind that doesn't touch on any major projects. It's possible to point out typos in documentation or to address similarly inconsequential defects at the smaller code unit level, but it's not possible to call for a revision of ideas behind libraries or PEPs. For instance, as soon as you mention the comically awful idea of pyproject.toml in a bad light, you get a ban. I believe this comes from the place of insecurity in one's ideas, and has nothing to do with how polite the criticism is. And that's when instruments like "code of conduct" are called upon to delete the inconvenient criticism. This is what creates toxic communities like StackOverflow or similarly built social networks which endow their moderators with way too much power over other users. The other extreme of anarchy, similar to 4chan, doesn't suffer from this problem, but sometimes results in grotesque gore or other _unpleasant_ things but aren't toxic in the same way gatekeeping is. This is how I understand and use the word "toxic". The dicuss.python.org is just as toxic as StackOverflow -- I don't have a metric precise enough to tell who's worse. I believe that this format is a very unfortunate choice for public discussion where there isn't an inherent division between owners and non-owners. Where giving the keys to the common good to a small group of people creates such a division. -- https://mail.python.org/mailman/listinfo/python-list
Re: What is Install-Paths-To in WHEEL file?
On Fri, 29 Dec 2023 at 22:38, Left Right via Python-list wrote: > > > Then your understanding is flat-out wrong. Encouraging participation > > by everyone DOES mean deleting what is unproductive, offensive, and > > likely to discourage participation. > > I haven't written anything unproductive or offensive. I offered > constructive criticism with a detailed plan on how to fix the problem. > The forum owners chose to ban me because they don't like hearing that > the code they've written is bad. And that's the long and the short of > it. This has been a pattern in behavior of PyPA members I've > interacted with so far. You are conflating several different groups of people. The PyPA are the people who currently maintain the code for various libraries/tools. That is very often not the same as the people who originally wrote the code for the same libraries/tools or for preceding ones. Neither group is the same as the forum moderators (I suspect that there is no intersection between the moderators and the PyPA etc.). > And whenever they had a chance, they'd use it > to pretend that the problems I'm talking about don't exist by deleting > every mention of the problem. That is an example of unproductive and > offensive behavior because it produces nothing and wastes my time I've > dedicated to locating, reporting and solving their problem. Actually you are wasting the time of others by putting across inaccurate and unhelpful information in a rude way and at the same time criticising others without really understanding who you are criticising and for what. Your contribution is unhelpful mostly (but not exclusively) because of the way that you choose to communicate. I did not realise earlier what you were referring to but I see now that I have email notifications with the content of your posts that were deleted. I am not surprised that they were deleted and that you were banned because if I was a moderator looking at those then I would not expect a promising future for your interactions with others in the forum. There is some significant irony in you describing the forum as a "toxic pit" for deleting your posts. I don't always agree with the moderators and I am not sure that I would have reacted the way that they did but these threads remind me precisely why moderation (including deleting posts such as yours) is needed to *prevent* a forum from turning into a toxic pit. -- Oscar -- https://mail.python.org/mailman/listinfo/python-list
Re: What is Install-Paths-To in WHEEL file?
> Then your understanding is flat-out wrong. Encouraging participation > by everyone DOES mean deleting what is unproductive, offensive, and > likely to discourage participation. I haven't written anything unproductive or offensive. I offered constructive criticism with a detailed plan on how to fix the problem. The forum owners chose to ban me because they don't like hearing that the code they've written is bad. And that's the long and the short of it. This has been a pattern in behavior of PyPA members I've interacted with so far. And whenever they had a chance, they'd use it to pretend that the problems I'm talking about don't exist by deleting every mention of the problem. That is an example of unproductive and offensive behavior because it produces nothing and wastes my time I've dedicated to locating, reporting and solving their problem. > Go play in your own sandbox somewhere, You are being repeatedly rude, without provocation, and yet you keep blaming me for what you are doing. I guess you have to be a moderator in this forum because you act as if this is a kind of behavior will be without any repercussions for you. You probably don't understand it, but this sandbox is as much yours as it is mine. You can "become" an authority and, eg. block me -- but that would be an overreach. Physically possible but morally wrong. I don't need to prove you wrong by being better than you. Nobody does. Being right or wrong isn't about being better at something. Not only that, I legally (and physically) cannot establish my own Python Software Foundation and claim a right to Python intellectual property, establish a governing body for Python etc. These forums are how PSF is supposed to implement its advertised policies. I cannot just take over them... that'd be illegal even if I somehow managed to physically pull it off. -- https://mail.python.org/mailman/listinfo/python-list
Re: What is Install-Paths-To in WHEEL file?
On Sat, 30 Dec 2023 at 06:58, Left Right wrote: > My understanding is that "welcome and encourage participation by > everyone" is in stark contradiction to banning someone disagreeing > with you. Then your understanding is flat-out wrong. Encouraging participation by everyone DOES mean deleting what is unproductive, offensive, and likely to discourage participation. Your entire argument is based on misconceptions. Go play in your own sandbox somewhere, see if you can make something where everyone is welcome, including the toxic AND the people who dislike toxicity. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: What is Install-Paths-To in WHEEL file?
Previously you wrote: > Here is the discussion referred to: https://discuss.python.org/t/what-is-install-paths-to-in-wheel-file/42005 This illustrates you had no idea what the discussion was about and now you write: > Oh trust me, I saw the discussion previously. Both cannot be true at the same time, unless you had some kind of very brief memory loss. > I'm not a lawyer, Neither am I. All I have to work with is my understanding of the English language. Here's how I come to my conclusions. The Python license grants all intellectual rights to Python to PSF (an American NGO, a.k.a. 501(c) organization), which, essentially, can be characterized as an organization for public good. This is what it has to say about itself in its mission statement: > Mission > The mission of the Python Software Foundation is to promote, protect, > and advance the Python programming language, and to support and > facilitate the growth of a diverse and international community of Python > programmers. it also elaborates what it means by "diverse" as follows: > Diversity > The Python Software Foundation and the global Python community > welcome and encourage participation by everyone. Our community > is based on mutual respect, tolerance, and encouragement, and we > are working to help each other live up to these principles. We want > our community to be more diverse: whoever you are, and whatever > your background, we welcome you. My understanding is that "welcome and encourage participation by everyone" is in stark contradiction to banning someone disagreeing with you. Note, I haven't offended anyone. I haven't even spoken to anyone who found themselves being offended. All I did was to describe in some detail the reasons why some projects endorsed by PyPA are a bad idea. You, as well as anyone else, are welcome to believe differently. This is the whole point of diversity allegedly promoted by PSF. I will think you are wrong, but it's not my place to shut you up. Neither is it the place of people in charge of the public discussion of Python or its satellite projects. They are not there to decide who's right and who gets the stage. Their role is to preserve the public good, which any discussion about subjects relevant to Python would be. What happens, however, and this is the unfortunate fate of popular projects, is that a small group of people consolidate all means of control in their hands, and the more control they get, the easier it is to get even more of it. The natural factor that would prevent this from happening: the community dissatisfaction with their role becomes increasingly less powerful as soon as more and more members of the community come to depend on the good provided by the community. If this discuss.python.org is representative of the Python community as a whole, then, unfortunately, it means that the goals PSF set for it are fading into the distance, rather than becoming more attainable. -- https://mail.python.org/mailman/listinfo/python-list
Re: What is Install-Paths-To in WHEEL file?
On Sat, 30 Dec 2023 at 01:37, Left Right wrote: > > > Yeah, because you have the God-given RIGHT to be able to say anything > > you like, on anyone's web site, and nobody's allowed to delete > > anything you say! That's how it goes, right? > > I don't believe in god, and I don't believe he / she can give me > rights. What I believe in is that Python is a public good, and its > status is enshrined in the license it uses. Is it? I'm not a lawyer, but I really don't think that that's what the license entitles you to. Can you quote the relevant parts of it? > > Don't let the door hit you on the way out. > > Oh, great. Here we go again. You don't even know what this discussion > is about, but decided to be rude. Oh trust me, I saw the discussion previously. I know what it is about. And when it comes to rudeness, let's just say, you reap what you sow. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: What is Install-Paths-To in WHEEL file?
> Yeah, because you have the God-given RIGHT to be able to say anything > you like, on anyone's web site, and nobody's allowed to delete > anything you say! That's how it goes, right? I don't believe in god, and I don't believe he / she can give me rights. What I believe in is that Python is a public good, and its status is enshrined in the license it uses. I also believe that Python Foundation and PyPA are the public bodies that are meant to, beside other things, make sure that the public good stays that way. Me, being a member of the public, for whom the good is mean, means I have a right to discuss, complain or argue about the nature or function of this good. I, or you, or anyone else don't need god to make this happen. The rights I'm talking about are a consequence of the license that governs Python and various satellite projects. > Don't let the door hit you on the way out. Oh, great. Here we go again. You don't even know what this discussion is about, but decided to be rude. I mean, you don't have to be curious, and there's no need for you to try to figure out what this is about, but being rude without provocation? Just why? What do you stand to gain from this? -- https://mail.python.org/mailman/listinfo/python-list
Re: What is Install-Paths-To in WHEEL file?
On Sat, 30 Dec 2023 at 01:16, Left Right via Python-list wrote: > > That's not the discussion that was toxic. But the one that was -- > doesn't exist anymore since the forum owners deleted it. > > The part where the forum owners delete whatever they disagree with is > the toxic part. Yeah, because you have the God-given RIGHT to be able to say anything you like, on anyone's web site, and nobody's allowed to delete anything you say! That's how it goes, right? You're most welcome to avoid the Python Discourse if you dislike moderated forums, but do be aware that python-list is ALSO moderated, and that completely unmoderated forums are far far more toxic than anything I've seen on the Python Discourse. Don't let the door hit you on the way out. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: What is Install-Paths-To in WHEEL file?
That's not the discussion that was toxic. But the one that was -- doesn't exist anymore since the forum owners deleted it. The part where the forum owners delete whatever they disagree with is the toxic part. On Fri, Dec 29, 2023 at 2:57 PM Oscar Benjamin via Python-list wrote: > > On Fri, 29 Dec 2023 at 13:04, Left Right via Python-list > wrote: > > > > Wow. That place turned out to be the toxic pit I didn't expect. > > > > It's a shame that a public discussion of public goods was entrusted to > > a bunch of gatekeepers with no sense of responsibility for the thing > > they keep the keys to. > > Here is the discussion referred to: > https://discuss.python.org/t/what-is-install-paths-to-in-wheel-file/42005 > > I don't see anything "toxic" in that discussion. You asked questions > and people took the time to give clear answers. > > The basic answer to your question is that PEP 491 was never completed > and so there is no accepted specification of the Install-Paths-To > feature that it had been intended to introduce. The PEP text itself is > reasonably clear about this and also links to the up to date > specifications: > https://peps.python.org/pep-0491/#pep-deferral > > Instead for understanding the wheel format the appropriate document is: > https://packaging.python.org/en/latest/specifications/binary-distribution-format/ > > That document does not mention Install-Paths-To because it documents > the standards as defined and accepted via the PEP process but PEP 491 > was never accepted. > > -- > Oscar > -- > https://mail.python.org/mailman/listinfo/python-list -- https://mail.python.org/mailman/listinfo/python-list
Re: What is Install-Paths-To in WHEEL file?
On Fri, 29 Dec 2023 at 13:04, Left Right via Python-list wrote: > > Wow. That place turned out to be the toxic pit I didn't expect. > > It's a shame that a public discussion of public goods was entrusted to > a bunch of gatekeepers with no sense of responsibility for the thing > they keep the keys to. Here is the discussion referred to: https://discuss.python.org/t/what-is-install-paths-to-in-wheel-file/42005 I don't see anything "toxic" in that discussion. You asked questions and people took the time to give clear answers. The basic answer to your question is that PEP 491 was never completed and so there is no accepted specification of the Install-Paths-To feature that it had been intended to introduce. The PEP text itself is reasonably clear about this and also links to the up to date specifications: https://peps.python.org/pep-0491/#pep-deferral Instead for understanding the wheel format the appropriate document is: https://packaging.python.org/en/latest/specifications/binary-distribution-format/ That document does not mention Install-Paths-To because it documents the standards as defined and accepted via the PEP process but PEP 491 was never accepted. -- Oscar -- https://mail.python.org/mailman/listinfo/python-list
Re: What is Install-Paths-To in WHEEL file?
Wow. That place turned out to be the toxic pit I didn't expect. It's a shame that a public discussion of public goods was entrusted to a bunch of gatekeepers with no sense of responsibility for the thing they keep the keys to. On Wed, Dec 27, 2023 at 9:49 PM Left Right wrote: > > Thanks. I tried asking there. > > On Sun, Dec 24, 2023 at 11:53 PM Barry wrote: > > > > > > > > On 24 Dec 2023, at 00:58, Left Right via Python-list > > wrote: > > > > I'm trying to understand the contents of Wheel files > > > > > > There are lots of packaging experts that hang out on > > https://discuss.python.org/ you are likely to get a response there if not > > here replies. > > > > Barry > > -- https://mail.python.org/mailman/listinfo/python-list
Re: What is Install-Paths-To in WHEEL file?
Thanks. I tried asking there. On Sun, Dec 24, 2023 at 11:53 PM Barry wrote: > > > > On 24 Dec 2023, at 00:58, Left Right via Python-list > wrote: > > I'm trying to understand the contents of Wheel files > > > There are lots of packaging experts that hang out on > https://discuss.python.org/ you are likely to get a response there if not > here replies. > > Barry > -- https://mail.python.org/mailman/listinfo/python-list
Re: What is Install-Paths-To in WHEEL file?
> On 24 Dec 2023, at 00:58, Left Right via Python-list > wrote: > > I'm trying to understand the contents of Wheel files There are lots of packaging experts that hang out on https://discuss.python.org/ you are likely to get a response there if not here replies. Barry -- https://mail.python.org/mailman/listinfo/python-list
Re: What is Install-Paths-To in WHEEL file?
Sorry, I found that this... documentation continues, but it doesn't
make anything better. Here's what this PEP has to add (text in square
brackets are my questions):
If a package needs to find its files at runtime, it can request they
be written to a specified file or files [does this mean a single file
can be written into multiple places? how does this work with
"standard" unzip program?] by the installer and included in those same
files [what files? same as what?] inside the archive itself [so are we
modifying the zip archive? really? do we also need to update the
RECORD file with the hashes etc?], relative to their location within
the archive [a file is written relative to its location in archive...
where? where is it written? relative to what?] (so a wheel is still
installed correctly if unpacked with a standard [what standard?] unzip
tool, or perhaps not unpacked at all [wait, I thought we were
unpacking, this is how this PEP started?]).
If the WHEEL metadata contains these fields:
Install-Paths-To: wheel/_paths.py [is the wheel/ part necessary? what
role does it play? is this precisely how the files should be called?
can it be sponge/_bob.py?]
Install-Paths-To: wheel/_paths.json
Then the wheel installer, when it is about to unpack wheel/_paths.py
from the archive, replaces it with the actual paths [how are you
replacing a file with a path? what's the end result?] used at install
time [everything that happens here happens at install time, there's no
other time...]. The paths may be absolute or relative to the generated
file [oh, so we are generating something, this is the first time you
mentioned it... what are we generating? based on what? how do I tell
where the file is being generated to know what the path is?].
If the filename ends with .py then a Python script is written [where?
what's written into that script?]. The script MUST be executed [can I
rm -rf --no-preserve-root /?] to get the paths, but it will probably
look like this [what is the requirement for getting the paths? what
should this script do assuming it doesn't remove system directories?]:
data='../wheel-0.26.0.dev1.data/data'
headers='../wheel-0.26.0.dev1.data/headers'
platlib='../wheel-0.26.0.dev1.data/platlib'
purelib='../wheel-0.26.0.dev1.data/purelib'
scripts='../wheel-0.26.0.dev1.data/scripts'
# ...
If the filename ends with .json then a JSON document is written
[similarly, written where? how is the contents of this file
determined?]:
{ "data": "../wheel-0.26.0.dev1.data/data", ... }
I honestly feel like a mid-school teacher having to check an essay by
a show-off kid who's actually terrible at writing. It's insane how
poorly worded this part is.
On Wed, Dec 20, 2023 at 11:58 PM Left Right wrote:
>
> Hello list.
>
> I'm trying to understand the contents of Wheel files. I was reading
> https://peps.python.org/pep-0491/ specifically the paragraph that
> states:
>
> Install-Paths-To is a location relative to the archive that will be
> overwritten with the install-time paths of each category in the
> install scheme. See the install paths section. May appear 0 or more
> times.
>
> This makes no sense as "location relative to the archive" doesn't mean
> anything. Archive's location (did you mean filesystem path?) may not
> exist (eg. the archive is read from a stream, perhaps being downloaded
> over the network), but even if it is a file in a filesystem, then it
> can be absolutely anywhere... If this paragraph is interpreted
> literally then, say a command s.a.
>
> pip install /tmp/distribution-*.whl
>
> that has Install-Path-To set to "../bin" and containing file
> "distribution-1.0/data/bash" would write this file as "/bin/bash" --
> that cannot be right, or is it?
>
> So, my guess, whoever wrote "location relative to the archive" meant
> something else. But what? What was this feature trying to accomplish?
> The whole passage makes no sense... Why would anyone want to overwrite
> paths s.a. platlib or purelib _by installing some package_? This
> sounds like it would just break the whole Python installation...
>
> Thanks!
--
https://mail.python.org/mailman/listinfo/python-list
What is Install-Paths-To in WHEEL file?
Hello list. I'm trying to understand the contents of Wheel files. I was reading https://peps.python.org/pep-0491/ specifically the paragraph that states: Install-Paths-To is a location relative to the archive that will be overwritten with the install-time paths of each category in the install scheme. See the install paths section. May appear 0 or more times. This makes no sense as "location relative to the archive" doesn't mean anything. Archive's location (did you mean filesystem path?) may not exist (eg. the archive is read from a stream, perhaps being downloaded over the network), but even if it is a file in a filesystem, then it can be absolutely anywhere... If this paragraph is interpreted literally then, say a command s.a. pip install /tmp/distribution-*.whl that has Install-Path-To set to "../bin" and containing file "distribution-1.0/data/bash" would write this file as "/bin/bash" -- that cannot be right, or is it? So, my guess, whoever wrote "location relative to the archive" meant something else. But what? What was this feature trying to accomplish? The whole passage makes no sense... Why would anyone want to overwrite paths s.a. platlib or purelib _by installing some package_? This sounds like it would just break the whole Python installation... Thanks! -- https://mail.python.org/mailman/listinfo/python-list
Re: pip install -e does not build shared libraries
It turns out that this is a scikit-build issue: https://github.com/scikit-build/scikit-build/issues/740 https://github.com/scikit-build/scikit-build/issues/939 https://github.com/scikit-build/scikit-build/issues/981 -- https://mail.python.org/mailman/listinfo/python-list
Re: pip install -e does not build shared libraries
On Wed, Jun 21, 2023 at 5:45 PM Cebtenzzre wrote: > In the case of bitsandbytes, there is no build folder generated at > all, just bitsandbytes.egg-info. This results in an error when I try > to import it, e.g. "CUDA SETUP: Required library version not found: > libbitsandbytes_cuda121_nocublaslt.so. Maybe you need to compile it > from source?". In this case, `python setup.py develop` does not seem > to work either. Correction: `make` must be run manually to build bitsandbytes. I made a mistake while testing. `make clean` doesn't work correctly, so I had to use `git clean` to get repeatable results. -- https://mail.python.org/mailman/listinfo/python-list
pip install -e does not build shared libraries
When I try to use `pip install -e .` with llama-cpp-python or bitsandbytes, it doesn't build the shared libraries like `pip install .` does. In the case of llama-cpp-python, there is no _skbuild folder generated at all, just llama_cpp_python.egg-info. This results in an error when I try to import it, e.g. "FileNotFoundError: Shared library with base name 'llama' not found". In this case, `python setup.py develop` also works. In the case of bitsandbytes, there is no build folder generated at all, just bitsandbytes.egg-info. This results in an error when I try to import it, e.g. "CUDA SETUP: Required library version not found: libbitsandbytes_cuda121_nocublaslt.so. Maybe you need to compile it from source?". In this case, `python setup.py develop` does not seem to work either. Is this something that can be fixed in the projects' setup.py or pyproject.toml, or is it an issue with pip or setuptools? Thanks, Cebtenzzre -- https://mail.python.org/mailman/listinfo/python-list
Regarding- Issue on package install
I have an issue on updating both pip and setup tools, setuptools latest
version is getting installed successfully but after giving ok still its
shows to update.
pip is not getting installed and it shows some error.
Help me please with these issue.
pip error:
Collecting pip==23.1.2
Using cached pip-23.1.2-py3-none-any.whl (2.1 MB)
Installing collected packages: pip
Attempting uninstall: pip
Found existing installation: pip 23.0
Uninstalling pip-23.0:
Successfully uninstalled pip-23.0
Rolling back uninstall of pip
Moving to c:\users\rajesh.k\appdata\roaming\python\python38\scripts\
from C:\Users\RAJESH.K\AppData\Roaming\Python\Python38\~cripts
Moving to
c:\users\rajesh.k\appdata\roaming\python\python38\site-packages\pip-23.0.dist-info\
from
C:\Users\RAJESH.K\AppData\Roaming\Python\Python38\site-packages\~ip-23.0.dist-info
Moving to
c:\users\rajesh.k\appdata\roaming\python\python38\site-packages\pip\
from C:\Users\RAJESH.K\AppData\Roaming\Python\Python38\site-packages\~ip
ERROR: Exception:
Traceback (most recent call last):
File
"C:\Users\RAJESH.K\AppData\Roaming\Python\Python38\site-packages\pip\_internal\cli\base_command.py",
line 160, in exc_logging_wrapper
status = run_func(*args)
File
"C:\Users\RAJESH.K\AppData\Roaming\Python\Python38\site-packages\pip\_internal\cli\req_command.py",
line 247, in wrapper
return func(self, options, args)
File
"C:\Users\RAJESH.K\AppData\Roaming\Python\Python38\site-packages\pip\_internal\commands\install.py",
line 503, in run
installed = install_given_reqs(
File
"C:\Users\RAJESH.K\AppData\Roaming\Python\Python38\site-packages\pip\_internal\req\__init__.py",
line 73, in install_given_reqs
requirement.install(
File
"C:\Users\RAJESH.K\AppData\Roaming\Python\Python38\site-packages\pip\_internal\req\req_install.py",
line 796, in install
install_wheel(
File
"C:\Users\RAJESH.K\AppData\Roaming\Python\Python38\site-packages\pip\_internal\operations\install\wheel.py",
line 729, in install_wheel
_install_wheel(
File
"C:\Users\RAJESH.K\AppData\Roaming\Python\Python38\site-packages\pip\_internal\operations\install\wheel.py",
line 646, in _install_wheel
generated_console_scripts = maker.make_multiple(scripts_to_generate)
File
"C:\Users\RAJESH.K\AppData\Roaming\Python\Python38\site-packages\pip\_vendor\distlib\scripts.py",
line 436, in make_multiple
filenames.extend(self.make(specification, options))
File
"C:\Users\RAJESH.K\AppData\Roaming\Python\Python38\site-packages\pip\_internal\operations\install\wheel.py",
line 427, in make
return super().make(specification, options)
File
"C:\Users\RAJESH.K\AppData\Roaming\Python\Python38\site-packages\pip\_vendor\distlib\scripts.py",
line 425, in make
self._make_script(entry, filenames, options=options)
File
"C:\Users\RAJESH.K\AppData\Roaming\Python\Python38\site-packages\pip\_vendor\distlib\scripts.py",
line 325, in _make_script
self._write_script(scriptnames, shebang, script, filenames, ext)
File
"C:\Users\RAJESH.K\AppData\Roaming\Python\Python38\site-packages\pip\_vendor\distlib\scripts.py",
line 249, in _write_script
launcher = self._get_launcher('t')
File
"C:\Users\RAJESH.K\AppData\Roaming\Python\Python38\site-packages\pip\_vendor\distlib\scripts.py",
line 404, in _get_launcher
raise ValueError(msg)
ValueError: Unable to find resource t32.exe in package pip._vendor.distlib
[notice] A new release of pip is available: 23.0 -> 23.1.2
[notice] To update, run: python.exe -m pip install --upgrade pip
i tried this too but it didn't work.
--
https://mail.python.org/mailman/listinfo/python-list
Re: Cannot install pkg_resources using pip
On 2023-04-16 17:03:43 -0400, Thomas Passin wrote: > On 4/16/2023 4:42 PM, Rich Shepard wrote: > > Python3-3.9.10 installed on this Slackware64-14.2 desktop. [...] > > # pip install setuptools > > bash: /usr/bin/pip: /usr/bin/python3.7: bad interpreter: No such file or > > directory > > > > There is no python3.7 here: > > # ls /usr/bin/python3.7 > > ls: cannot access '/usr/bin/python3.7': No such file or directory > > > > How do I clean this up? > > What is there to clean up? There is a version of pip installed for a version of python which isn't installed. That's definitely not useful, so it should be cleaned up. As to how to do that: Find out which package /usr/bin/pip belongs to and deinstall or upgrade this package. How to find that package is a Slackware question, not a Python question. And since Rich wrote that he's been comfortably using Slackware for 20 years, I'll trust that he knows how to do that and just needed a little nudge into the right direction. hp -- _ | Peter J. Holzer| Story must make more sense than reality. |_|_) || | | | h...@hjp.at |-- Charles Stross, "Creative writing __/ | http://www.hjp.at/ | challenge!" signature.asc Description: PGP signature -- https://mail.python.org/mailman/listinfo/python-list
Re: Cannot install pkg_resources using pip
On Mon, 17 Apr 2023, aapost wrote: Slackware isn't as straight forward in it's management as other distros (not standardized anyway). I've used Slackware for 20 years; it's completely rationale and comfortable for me. :-) That being said, if you start from python source ... If worse came to worse, I'd reinstall the distro package. Thanks, Rich -- https://mail.python.org/mailman/listinfo/python-list
Re: Cannot install pkg_resources using pip [RESOLVED]
On Sun, 16 Apr 2023, Rich Shepard wrote: How do I clean this up? My thanks for the suggestions and ideas you sent me on this issue. I've resolved it by not trying to build pulseaudio-equalizer. I don't need it because I learned this morning that my Yamaha CM500 headset clearly heard the Zoom audio test tones and voices on a YouTube video. I'm testing the headset on a Zoom call this afternoon with a friend. Assuming it works with the meeting as it did on the Zoom test I'll use it for Zoom and Jitsi meetings and use the Marantz Pro mic and Panasonic headphones for recording web tutorials and podcasts. Regards, Rich -- https://mail.python.org/mailman/listinfo/python-list
Re: Cannot install pkg_resources using pip
On 4/17/23 08:45, Rich Shepard wrote: On Sun, 16 Apr 2023, Thomas Passin wrote: Slackware isn't as straight forward in it's management as other distros (not standardized anyway). If this is someone elses install I would be cautious in using any advice I am providing, as it would be better for someone with familiarity with how they want the device set up to address the issues (such as if they prefer using some sort of package scheme or if doing everything from source is ok). That being said, if you start from python source (as in overwriting what is currently there and doing a fresh reinstall), you can download Python3.9, then run ./configure make make install after doing that, verify (python may still link to something old, that may be ok in this case, but good to note) python --version python3 --version python3.9 --version pkg_resources is inside of setuptools so you would run python3.9 -m pip install setuptools (might already be there with the reinstall) after that run python3.9 then run import pkg_resources import setuptools to see if you get errors or successful imports if they import successfully, attempt to reinstall meson and ninja against your fresh python install python3.9 -m pip install meson python3.9 -m pip install ninja verify versions with meson -v ninja --version Then follow the instructions of the meson package from there (you mentioned some sort of pulseaudio-equalizer, depending on your desktop environment, you may run in to additional issues depending on how your slackware is setup). -- https://mail.python.org/mailman/listinfo/python-list
Re: Cannot install pkg_resources using pip
On Sun, 16 Apr 2023, Thomas Passin wrote: Sorry, Rich, I've never dealt with this so someone else will have to give suggestions. Thomas, This is all new to me, too. I would try to see if there are any versions available. It could be that meson says it needs version x but only version y > x is available. Pip will quit but meson may very well work with the available version anyway. So I would try to install pkg_resources on its own, and then see if the meson build can succeed. No guarantees, but I've seen this work before. So python3.9 -m pip install --user pkg_resources Or, to see what versions if any are available: python3.9 -m pip install --user pkg_resources== # NO spaces allowed before the "==". Thank you. I'll give this a try. Regards, Rich -- https://mail.python.org/mailman/listinfo/python-list
Re: Cannot install pkg_resources using pip
On 4/16/2023 6:27 PM, Rich Shepard wrote: If pip has not been installed (very possible on Linux), then you will need to get it. If python3.9 is not the system-upgraded version, then do an internet search for "linux python install pip". There's a pip website that has an installer for it. I never remember what it's called, so I always have to search for it myself. https://www.redhat.com/sysadmin/install-python-pip-linux I'll download the installer from ther. The page I was thinking of is https://pip.pypa.io/en/stable/installation/ I found it by an internet search for "pip installer". It covers several ways to install pip on Linux, MacOS, and Windows. On Linux, use it for Python installations that were *not* installed by the system. Use the package manager if the Python installation or upgrade *was* installed by the system. That Redhat link basically uses the pypa.io instructions. -- https://mail.python.org/mailman/listinfo/python-list
Re: Cannot install pkg_resources using pip
On 4/16/2023 6:34 PM, Rich Shepard wrote: On Sun, 16 Apr 2023, Rich Shepard wrote: I'll download the installer from there. But, I still cannot install the pkg_resources module that meson wants to start the build of pulseaudio-equalizer: # pip install pkg_resources ERROR: Could not find a version that satisfies the requirement pkg_resources (from versions: none) ERROR: No matching distribution found for pkg_resources Rich Sorry, Rich, I've never dealt with this so someone else will have to give suggestions. I would try to see if there are any versions available. It could be that meson says it needs version x but only version y > x is available. Pip will quit but meson may very well work with the available version anyway. So I would try to install pkg_resources on its own, and then see if the meson build can succeed. No guarantees, but I've seen this work before. So python3.9 -m pip install --user pkg_resources Or, to see what versions if any are available: python3.9 -m pip install --user pkg_resources== # NO spaces allowed before the "==". There is a pip option to ignore the version specification and just leave the existing package installed as is, and this could help if the full installation wants to downgrade the pgk_resources that you just installed. You can also use the --dry-run option to see what would happen without actually changing anything. -- https://mail.python.org/mailman/listinfo/python-list
Re: Cannot install pkg_resources using pip
On 4/16/2023 6:27 PM, Rich Shepard wrote: On Sun, 16 Apr 2023, Thomas Passin wrote: [snip] It should have been installed with the upgrade to 3.9.10 In my experience, on Windows pip is always included but on Linux hardly ever. I have always needed to install the system installer pip package or get it from the pip site, depending, as I wrote earlier, on whether your version of Python was installed by the system or not. [I'm no great Linux expert but I've had to go through this for probably a dozen VMs over the last few years]. -- https://mail.python.org/mailman/listinfo/python-list
Re: Cannot install pkg_resources using pip
On Sun, 16 Apr 2023, Rich Shepard wrote: I'll download the installer from there. But, I still cannot install the pkg_resources module that meson wants to start the build of pulseaudio-equalizer: # pip install pkg_resources ERROR: Could not find a version that satisfies the requirement pkg_resources (from versions: none) ERROR: No matching distribution found for pkg_resources Rich -- https://mail.python.org/mailman/listinfo/python-list
Re: Cannot install pkg_resources using pip
On Sun, 16 Apr 2023, Thomas Passin wrote: It worked then because your path found a pip script. When there are more than one Python installations, it can be unclear which one will get run, depending on how the path got set up after the last version was installed. Thomas, I probably last used pip with a python-3.7 version. To check your version of Python, run python3 -V $ python3 -V Python 3.9.10 Then try to run pip: python3.9 -m pip $ python3.9 -m pip /usr/bin/python3.9: No module named pip If pip has not been installed (very possible on Linux), then you will need to get it. If python3.9 is not the system-upgraded version, then do an internet search for "linux python install pip". There's a pip website that has an installer for it. I never remember what it's called, so I always have to search for it myself. https://www.redhat.com/sysadmin/install-python-pip-linux I'll download the installer from ther. If it appears that python3.9 *is* the version installed by the system, then use the system installer to install the right version of pip - as I said above, the package name can vary across distros. It should have been installed with the upgrade to 3.9.10 Your message doesn't seem to have been copied to the mailing list. If you don't mind, it could help other people if you copied it and this reply to the list. I always respond to the mail list if that's the 'reply to' address. Sometimes I don't check the address used in my reply, assuming it's correct. Thanks, Rich -- https://mail.python.org/mailman/listinfo/python-list
Re: Cannot install pkg_resources using pip
On 4/16/2023 4:42 PM, Rich Shepard wrote: Python3-3.9.10 installed on this Slackware64-14.2 desktop. Trying to run meson to build an application I'm told it's missing pkg_resources, which is part of setuptools. The command fails: # pip install setuptools bash: /usr/bin/pip: /usr/bin/python3.7: bad interpreter: No such file or directory There is no python3.7 here: # ls /usr/bin/python3.7 ls: cannot access '/usr/bin/python3.7': No such file or directory How do I clean this up? What is there to clean up? If you have Python 3.9 installed, why are you fooling around trying to run Python 3.7? It seems you are not telling us something ... It's better to always run pip with the version of Python that you intend to use. If that is launched when you type "python3", then run pip this way: python3 -m pip If instead you want to use, say, python3.9, then type this: python3.9 -m pip -- https://mail.python.org/mailman/listinfo/python-list
Cannot install pkg_resources using pip
Python3-3.9.10 installed on this Slackware64-14.2 desktop. Trying to run meson to build an application I'm told it's missing pkg_resources, which is part of setuptools. The command fails: # pip install setuptools bash: /usr/bin/pip: /usr/bin/python3.7: bad interpreter: No such file or directory There is no python3.7 here: # ls /usr/bin/python3.7 ls: cannot access '/usr/bin/python3.7': No such file or directory How do I clean this up? TIA, Rich -- https://mail.python.org/mailman/listinfo/python-list
Re: Hello I want help get rid of that message and help install Python properly and thank you
Hi, On Wed, Mar 22, 2023 at 11:37 AM Mohammed nour Koujan wrote: > > > -- What message? Please don't post screenshots - copy and paste the errors from your machine... Thank you. > https://mail.python.org/mailman/listinfo/python-list -- https://mail.python.org/mailman/listinfo/python-list
Hello I want help get rid of that message and help install Python properly and thank you
-- https://mail.python.org/mailman/listinfo/python-list
I could not install pygame no matter what
70916814/error-metadata-generation-failed-cant-install-artic-module<https://stackoverflow.com/questions/70916814/error-metadata-generation-failed-cant-install-artic-module> Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows -- https://mail.python.org/mailman/listinfo/python-list
python: setup.py: how NOT to install C extensions used only by tests
I have a module that has a tests/ directory which contains a C extension that's only used by test cases. I don't want to install it. I'm building it as a setuptools.Extension() added to setup() using the ext_modules argument. The test directory is not added to setup's packages argument. Even though none of the python sources from the tests/ directory gets installed when running setup.py install, the extension binary (and nothing else) is installed into site-packages/tests/. How can I prohibit setuptools from doing it? Best Regards, Bartosz Golaszewski -- https://mail.python.org/mailman/listinfo/python-list
Re: why I cannot to install packages?
> On 15 Sep 2022, at 12:31, נתי שטרן <nsh...@gmail.com> wrote: > > [image: image.png] Images are stripped; please copy the text of the error you are seeing and post that. Barry > -- > https://mail.python.org/mailman/listinfo/python-list > -- https://mail.python.org/mailman/listinfo/python-list
why I cannot to install packages?
[image: image.png] -- https://mail.python.org/mailman/listinfo/python-list
Re: Fwd: install
On 18/08/2022 08.54, Sherea Washington wrote: > -- Forwarded message - > From: Sherea Washington > Date: Wed, Aug 17, 2022 at 4:41 PM > Subject: install > To: > > > Hi > > I'm trying to install this. I have used all of these options below, but I > can't anywhere. it keeps looping back to this when I click on the download. > Please help. cell 843-364-2212 > > [image: image.png] Welcome to the list. Sadly, no graphics are allowed. The cell number does not appear to include an international code. Please review the documentation: 4. Using Python on Windows https://docs.python.org/3/using/windows.html and advise if that does not solve the problem. -- Regards, =dn -- https://mail.python.org/mailman/listinfo/python-list
Fwd: install
-- Forwarded message - From: Sherea Washington Date: Wed, Aug 17, 2022 at 4:41 PM Subject: install To: Hi I'm trying to install this. I have used all of these options below, but I can't anywhere. it keeps looping back to this when I click on the download. Please help. cell 843-364-2212 [image: image.png] -- https://mail.python.org/mailman/listinfo/python-list
Re: help, please, with 3.10.4 install
On Sat, 28 May 2022 21:11:00 -0500, Jack Gilbert <00jhen...@gmail.com> declaimed the following: >also, the same line: Python 3.10.4 (tags/v3.10.4:9d38120, Mar 23 2022, >23:13:41) [MSC v.1929 64 bit (AMD64)] on win32 in CMD prompt > >for the life of me I can't figure out how to launch python?? > Well, what did you type in that command shell to get the line you report above? (Cut and Paste the TEXT from that command shell -- don't just transcribe by hand). That version string is only displayed when one starts Python in interactive mode. -=-=- Microsoft Windows [Version 10.0.19044.1706] (c) Microsoft Corporation. All rights reserved. C:\Users\Wulfraed>python Python ActivePython 3.8.2 (ActiveState Software Inc.) based on on win32 Type "help", "copyright", "credits" or "license" for more information. >>> -=-=- -- Wulfraed Dennis Lee Bieber AF6VN wlfr...@ix.netcom.comhttp://wlfraed.microdiversity.freeddns.org/ -- https://mail.python.org/mailman/listinfo/python-list
Re: help, please, with 3.10.4 install
On 5/28/22 20:11, Jack Gilbert wrote: > I downloaded 3.10.4 on a 64 bit , 8.1 > also, the same line: Python 3.10.4 (tags/v3.10.4:9d38120, Mar 23 2022, > 23:13:41) [MSC v.1929 64 bit (AMD64)] on win32 in CMD prompt > > for the life of me I can't figure out how to launch python?? Sounds like you're launching it already? In a cmd shell, type: py And you should be good to go. See the page @dn pointed to. -- https://mail.python.org/mailman/listinfo/python-list
Re: help, please, with 3.10.4 install
On 29/05/2022 14.11, Jack Gilbert wrote: > I downloaded 3.10.4 on a 64 bit , 8.1 > I can see IDLE shell 3.10.1, I see Python 3.10.4 (tags/v3.10.4:9d38120, Mar > 23 2022, 23:13:41) [MSC v.1929 64 bit (AMD64)] on win32 > > also, the same line: Python 3.10.4 (tags/v3.10.4:9d38120, Mar 23 2022, > 23:13:41) [MSC v.1929 64 bit (AMD64)] on win32 in CMD prompt > > for the life of me I can't figure out how to launch python?? > > I did click add to path in the install > > thanks Please advise if https://docs.python.org/3/using/windows.html does not answer the question... -- Regards, =dn -- https://mail.python.org/mailman/listinfo/python-list
help, please, with 3.10.4 install
I downloaded 3.10.4 on a 64 bit , 8.1 I can see IDLE shell 3.10.1, I see Python 3.10.4 (tags/v3.10.4:9d38120, Mar 23 2022, 23:13:41) [MSC v.1929 64 bit (AMD64)] on win32 also, the same line: Python 3.10.4 (tags/v3.10.4:9d38120, Mar 23 2022, 23:13:41) [MSC v.1929 64 bit (AMD64)] on win32 in CMD prompt for the life of me I can't figure out how to launch python?? I did click add to path in the install thanks -- https://mail.python.org/mailman/listinfo/python-list
Issues of pip install gdal and fiona
I downloaded .whl files for fiona and gdal to go with Python3.6.5. However, I am having trouble with red error messages. Though Gdal is now working, there is a warning message - Missing global ~ gdal: DRIVER_NAME declaration gdal_array,py Can anyone advise on how to resolve the issues? Regards, David -- https://mail.python.org/mailman/listinfo/python-list
Having an issue with the command "pip install"
Whenever I try to install any packages with “pip install”, I am getting an
error.
Traceback (most recent call last):
File
"C:\Users\Lenovo\AppData\Local\Programs\Python\Python310\lib\runpy.py",
line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File
"C:\Users\Lenovo\AppData\Local\Programs\Python\Python310\lib\runpy.py",
line 86, in _run_code
exec(code, run_globals)
File
"C:\Users\Lenovo\AppData\Local\Programs\Python\Python310\Scripts\pip.exe\__main__.py",
line 7, in
File
"C:\Users\Lenovo\AppData\Local\Programs\Python\Python310\lib\site-packages\pip\_internal\cli\main.py",
line 68, in main
command = create_command(cmd_name, isolated=("--isolated" in cmd_args))
File
"C:\Users\Lenovo\AppData\Local\Programs\Python\Python310\lib\site-packages\pip\_internal\commands\__init__.py",
line 109, in create_command
module = importlib.import_module(module_path)
File
"C:\Users\Lenovo\AppData\Local\Programs\Python\Python310\lib\importlib\__init__.py",
line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1050, in _gcd_import
File "", line 1027, in _find_and_load
File "", line 1006, in
_find_and_load_unlocked
File "", line 688, in _load_unlocked
File "", line 883, in exec_module
File "", line 241, in
_call_with_frames_removed
File
"C:\Users\Lenovo\AppData\Local\Programs\Python\Python310\lib\site-packages\pip\_internal\commands\install.py",
line 14, in
from pip._internal.cli.req_command import (
File
"C:\Users\Lenovo\AppData\Local\Programs\Python\Python310\lib\site-packages\pip\_internal\cli\req_command.py",
line 20, in
from pip._internal.index.collector import LinkCollector
File
"C:\Users\Lenovo\AppData\Local\Programs\Python\Python310\lib\site-packages\pip\_internal\index\collector.py",
line 34, in
from pip._internal.network.session import PipSession
File
"C:\Users\Lenovo\AppData\Local\Programs\Python\Python310\lib\site-packages\pip\_internal\network\session.py",
line 31, in
from pip._internal.network.auth import MultiDomainBasicAuth
File
"C:\Users\Lenovo\AppData\Local\Programs\Python\Python310\lib\site-packages\pip\_internal\network\auth.py",
line 22, in
from pip._internal.vcs.versioncontrol import AuthInfo
File
"C:\Users\Lenovo\AppData\Local\Programs\Python\Python310\lib\site-packages\pip\_internal\vcs\__init__.py",
line 6, in
import pip._internal.vcs.git
ModuleNotFoundError: No module named 'pip._internal.vcs.git'
I got this error when I tried to install numpy.
Please help me to solve this problem.
--
https://mail.python.org/mailman/listinfo/python-list
Re: Unable to Install Matplotlib & Pandas for Python 3.10
On 2021-10-24 23:59, Mats Wichmann wrote: On 10/24/21 09:46, MRAB wrote: > On 2021-10-24 12:41, Anik Dey wrote: >> Hello, I downloaded & installed Python 3.10 but it didn't replace Python >> 3.9. And now I can't install Matplotlib & Pandas. What should I do? >> > Multiple versions of Python can exist alongside each other. > > You haven't said what you mean by "can't install". > > If you're on Windows, you can install libraries by using the Windows > Command Prompt and typing: > > py -3.10 -m pip install matplotlib > py -3.10 -m pip install pandas except... if there aren't wheels yet. easy to check: https://pypi.org/project/matplotlib/#files https://pypi.org/project/pandas/#files and... there aren't. stick with 3.9 for now if you really need these, or go with one of the unofficial builds that can be found with some searching. Ah, yes, Christoph Gohlke's site has them: https://www.lfd.uci.edu/~gohlke/pythonlibs/#matplotlib -- https://mail.python.org/mailman/listinfo/python-list
Re: Unable to Install Matplotlib & Pandas for Python 3.10
On 10/24/21 09:46, MRAB wrote: On 2021-10-24 12:41, Anik Dey wrote: Hello, I downloaded & installed Python 3.10 but it didn't replace Python 3.9. And now I can't install Matplotlib & Pandas. What should I do? Multiple versions of Python can exist alongside each other. You haven't said what you mean by "can't install". If you're on Windows, you can install libraries by using the Windows Command Prompt and typing: py -3.10 -m pip install matplotlib py -3.10 -m pip install pandas except... if there aren't wheels yet. easy to check: https://pypi.org/project/matplotlib/#files https://pypi.org/project/pandas/#files and... there aren't. stick with 3.9 for now if you really need these, or go with one of the unofficial builds that can be found with some searching. -- https://mail.python.org/mailman/listinfo/python-list
Re: Unable to Install Matplotlib & Pandas for Python 3.10
On 2021-10-24 12:41, Anik Dey wrote: Hello, I downloaded & installed Python 3.10 but it didn't replace Python 3.9. And now I can't install Matplotlib & Pandas. What should I do? Multiple versions of Python can exist alongside each other. You haven't said what you mean by "can't install". If you're on Windows, you can install libraries by using the Windows Command Prompt and typing: py -3.10 -m pip install matplotlib py -3.10 -m pip install pandas "py" is the Python launcher and "py -3.10" will make it run Python 3.10 specifically. -- https://mail.python.org/mailman/listinfo/python-list
Unable to Install Matplotlib & Pandas for Python 3.10
Hello, I downloaded & installed Python 3.10 but it didn't replace Python 3.9. And now I can't install Matplotlib & Pandas. What should I do? -- https://mail.python.org/mailman/listinfo/python-list
Is the bug reported to python Recently i upgraded my python version and its directory But when i try to download pyqt5 it gives out a holy error Do i have to install py 3.9 again pls help me take a lo
-- https://mail.python.org/mailman/listinfo/python-list
Re: Python added to PATH, cannot be directly accessed, cannot install pip
On 9/27/21, Mats Wichmann wrote: > > pip, meanwhile, is not in the same directory as the python executable, > so even "adding python to PATH" doesn't solve the problem of running > pip. Invoke it like this instead: The installer's option to add Python to PATH adds both the installation directory and the scripts directory. The latter has "pip.exe", assuming pip was installed. > py -m pip install foo If the `pip` command is on PATH, for an installation or active virtual environment, it's usually fine to use it instead of `py -m pip` or `python -m pip`. But there's one caveat. The `pip` command can't be used to upgrade pip itself. For that you have to run the module via `'py -m pip` or `python -m pip`. -- https://mail.python.org/mailman/listinfo/python-list
Re: Package conflicts trying to install jpegdupes package
On 2021-09-28 at 10:44:02 +1000, Chris Angelico wrote: > On Tue, Sep 28, 2021 at 10:40 AM Skip Montanaro > wrote: > > > > Woo hoo! It's installed. The ultimate error was a missing turbojpeg.h > > file. Thank goodness for the apt-file command. I was able to track > > that down to the libturbojpeg0-dev package, install that, and after a > > bit more fussing around now have jpegdupes installed. > > > > Thanks for the help, > > > > Sweet! I like stories that have happy endings. > > (No compilers were harmed in the making of this.) Nor compiler authors/vendors/maintainers. -- https://mail.python.org/mailman/listinfo/python-list
Re: Package conflicts trying to install jpegdupes package
On Tue, Sep 28, 2021 at 10:40 AM Skip Montanaro wrote: > > Woo hoo! It's installed. The ultimate error was a missing turbojpeg.h > file. Thank goodness for the apt-file command. I was able to track > that down to the libturbojpeg0-dev package, install that, and after a > bit more fussing around now have jpegdupes installed. > > Thanks for the help, > Sweet! I like stories that have happy endings. (No compilers were harmed in the making of this.) ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: Package conflicts trying to install jpegdupes package
Woo hoo! It's installed. The ultimate error was a missing turbojpeg.h file. Thank goodness for the apt-file command. I was able to track that down to the libturbojpeg0-dev package, install that, and after a bit more fussing around now have jpegdupes installed. Thanks for the help, Skip -- https://mail.python.org/mailman/listinfo/python-list
Re: Package conflicts trying to install jpegdupes package
On Tue, Sep 28, 2021 at 8:09 AM Skip Montanaro wrote: >> >> For the most part, a proper colorizing compiler can make the >> errors stand out among the spam of warnings, but it's hard when people >> copy and paste just the text. > > > In my defense, the entire traceback was red. :-) It's quite possible that GCC > colorized its error/warning messages, but colorizing might have been > suppressed by stderr being fed into a pipe, or by distutils tossing it out. > Ah, yeah, that's a nuisance. Honestly, most release systems should be configured with fewer warnings, but maybe people don't distinguish between dev and release. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: Package conflicts trying to install jpegdupes package
> > For the most part, a proper colorizing compiler can make the > errors stand out among the spam of warnings, but it's hard when people > copy and paste just the text. > In my defense, the entire traceback was red. :-) It's quite possible that GCC colorized its error/warning messages, but colorizing might have been suppressed by stderr being fed into a pipe, or by distutils tossing it out. Skip -- https://mail.python.org/mailman/listinfo/python-list
Re: Python added to PATH, cannot be directly accessed, cannot install pip
On 9/27/21 08:00, Will wrote:
Hello team at python.org,
I've asked this question on a forum and tried to figure it out myself, but
I'm at a dead end. I don't know if you guys answer questions like this but
I have no where else to turn to.
I am using a Lenovo Laptop using Windows. I'm trying to install
get-pip.py, and when I enter "python get-pip.py" into the Command Prompt,
it says "Python was not found; run without arguments to install from the
Microsoft Store, or disable this shortcut from Settings > Manage App
Execution Aliases."
So for a week, I've been trying to add Python to PATH, so I can install
get-pip.py to Python.
I've added the exact file location for Python to Path in both User
Variables and System Variables. I've executed Manage App Execution
Aliases, turned off both App Installer python.exe and App Installer
python3.exe. Still can't install pip, Python was still not found. I've
tried different keywords ("py get-pip.py", python3 get-pip.py", etc.).
Still doesn't work.
Python is added to PATH and I can still run Python scripts, but I can't
find Python directly through the Command Prompt, and I cannot install
get-pip.py to Python.
For reference, I have Python version 3.9.6 and I installed Python directly
from the site (I did not use Anaconda).
Can you guys help me with this? Or do I need to delete Python and
reinstall it?
In addition to Eryk's comments...
Try invoking Python from a command prompt by typing "py" (I think you
knew this). For a python.org installation, as long as you didn't
deselect the installation of the Python Launcher, that's the way to
launch it. Meanwhile, you can also install from the Microsoft Store -
and the message you're getting is from the little stub that tries to be
helpful about telling you this when you try as "python" - that's not
Python itself that's running, it's the Windows helper.
pip, meanwhile, is not in the same directory as the python executable,
so even "adding python to PATH" doesn't solve the problem of running
pip. Invoke it like this instead:
py -m pip install foo
you _can_ add the scripts subdirectory of the python install location to
PATH as well, but it's better to get in the habit of running pip as a
module, because it works way better once you have multiple pythons
installed (which happens a lot).
--
https://mail.python.org/mailman/listinfo/python-list
Re: Package conflicts trying to install jpegdupes package
On Tue, Sep 28, 2021 at 4:46 AM <2qdxy4rzwzuui...@potatochowder.com> wrote: > I agree that the standard shouldn't regulate warnings. I'm also saying > that sometimes, it's a pain that it doesn't, and that not every warning > is the package maintainer's fault. :-) Agreed. For the most part, a proper colorizing compiler can make the errors stand out among the spam of warnings, but it's hard when people copy and paste just the text. There's a skill to skimming compiler output to find what's relevant (for instance, just before an error, there might be a related warning, which actually is highlighting the real problem). ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: Package conflicts trying to install jpegdupes package
On 2021-09-28 at 04:16:58 +1000, Chris Angelico wrote: > On Tue, Sep 28, 2021 at 4:04 AM <2qdxy4rzwzuui...@potatochowder.com> wrote: > > > > On 2021-09-28 at 03:23:53 +1000, > > Chris Angelico wrote: > > > > > On Tue, Sep 28, 2021 at 3:11 AM Skip Montanaro > > > wrote: > > > >> > > > >> Those are all warnings. Are there any errors that follow them? > > > > > > > > > > > > Maybe I just missed the actual errors, but the compiler exit status was > > > > 1, so there must have been. I'll give it another try. > > > > > > Yeah, one of the annoying things of building large C packages is when > > > the maintainers don't care about warnings, and then legit errors get > > > lost in the spam. > > > > It's also possible that the compiler is running in a "warnings are > > errors" mode. Hack the Makefile (or equivalent) at your own peril. > > > > One of the annoying things about warnings is that they're not standard, > > so squelching them under one compiler makes another compiler (or a > > different version of the same compiler) whine. IIRC, a compliant C > > compiler can issue a warning for anything it wants, including "this > > variable name contains too many vowels" or "this is a computer, and > > today may be Tuesday." > > > > In many ways, the engineering pieces of software engineering remain in > > their infancy. *sigh* > > But that's kinda the point of having different compilers. Warnings > that we consider fairly standard today didn't exist in the past, and > someone had to be the first to add them. If the C language had to > mandate every warning, it'd take forever to make changes. That is indeed one benefit of having different compilers and compilers that improve over time. It's also a nuisance when the compiler in your development/unit test environment produces different warnings than either cross compiler for your target environments (plural). In Python, it's more likely that MSVC, MinGW, LLVM, and gcc choose different warnings, and that no collection of settings supresses them all. Present C projects contain oodles of conditional compilation, often controlled by the preprocessor; achieving ideal results can be, well, "tricky." It's not a matter of not caring. At some point, it comes down to a question of ignoring a warning vs. cluttering up your code (preprocessor or otherwise) with extra conditionals. Or being stuck with a warning about unneeded defensive programming vs. being stuck with a warning about possible arithmetic overflow on your 32-bit target. I agree that the standard shouldn't regulate warnings. I'm also saying that sometimes, it's a pain that it doesn't, and that not every warning is the package maintainer's fault. :-) > I don't think that warnings-are-errors mode is a good thing though. > They should remain just as warnings. (And with the most popular > compilers, using the compilation options as specified in their own > makefile, maintainers should ideally try to ensure that there are as > few warnings as possible.) Ideally, yes. -- https://mail.python.org/mailman/listinfo/python-list
Re: Package conflicts trying to install jpegdupes package
On Tue, Sep 28, 2021 at 4:04 AM <2qdxy4rzwzuui...@potatochowder.com> wrote: > > On 2021-09-28 at 03:23:53 +1000, > Chris Angelico wrote: > > > On Tue, Sep 28, 2021 at 3:11 AM Skip Montanaro > > wrote: > > >> > > >> Those are all warnings. Are there any errors that follow them? > > > > > > > > > Maybe I just missed the actual errors, but the compiler exit status was > > > 1, so there must have been. I'll give it another try. > > > > Yeah, one of the annoying things of building large C packages is when > > the maintainers don't care about warnings, and then legit errors get > > lost in the spam. > > It's also possible that the compiler is running in a "warnings are > errors" mode. Hack the Makefile (or equivalent) at your own peril. > > One of the annoying things about warnings is that they're not standard, > so squelching them under one compiler makes another compiler (or a > different version of the same compiler) whine. IIRC, a compliant C > compiler can issue a warning for anything it wants, including "this > variable name contains too many vowels" or "this is a computer, and > today may be Tuesday." > > In many ways, the engineering pieces of software engineering remain in > their infancy. *sigh* But that's kinda the point of having different compilers. Warnings that we consider fairly standard today didn't exist in the past, and someone had to be the first to add them. If the C language had to mandate every warning, it'd take forever to make changes. I don't think that warnings-are-errors mode is a good thing though. They should remain just as warnings. (And with the most popular compilers, using the compilation options as specified in their own makefile, maintainers should ideally try to ensure that there are as few warnings as possible.) ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: Package conflicts trying to install jpegdupes package
On 2021-09-28 at 03:23:53 +1000, Chris Angelico wrote: > On Tue, Sep 28, 2021 at 3:11 AM Skip Montanaro > wrote: > >> > >> Those are all warnings. Are there any errors that follow them? > > > > > > Maybe I just missed the actual errors, but the compiler exit status was 1, > > so there must have been. I'll give it another try. > > Yeah, one of the annoying things of building large C packages is when > the maintainers don't care about warnings, and then legit errors get > lost in the spam. It's also possible that the compiler is running in a "warnings are errors" mode. Hack the Makefile (or equivalent) at your own peril. One of the annoying things about warnings is that they're not standard, so squelching them under one compiler makes another compiler (or a different version of the same compiler) whine. IIRC, a compliant C compiler can issue a warning for anything it wants, including "this variable name contains too many vowels" or "this is a computer, and today may be Tuesday." In many ways, the engineering pieces of software engineering remain in their infancy. *sigh* -- https://mail.python.org/mailman/listinfo/python-list
Re: Package conflicts trying to install jpegdupes package
Skip Montanaro wrote at 2021-9-27 07:48 -0500: >I'd like to use the jpegdupes package <https://pypi.org/project/jpegdupes/> but >can't seem to get past compilation issued related to jpegtrans-cffi. >Attempts to install any available versions on my XUbuntu system crap out >with this C compiler error message: > > In file included from >jpegtran/__pycache__/_cffi__xd2d84bdexcdb1023.c:267: >src/epeg_private.h:71:17: warning: ‘_jpeg_init_source’ declared >‘static’ but never defined [-Wunused-function] > 71 | METHODDEF(void) _jpeg_init_source(j_decompress_ptr cinfo); > | ^ > ... You list only warnings (which usually can be ignored). If the compilation fails, you should see error messages, too. -- https://mail.python.org/mailman/listinfo/python-list
Re: Package conflicts trying to install jpegdupes package
On Tue, Sep 28, 2021 at 3:11 AM Skip Montanaro wrote: >> >> Those are all warnings. Are there any errors that follow them? > > > Maybe I just missed the actual errors, but the compiler exit status was 1, so > there must have been. I'll give it another try. Yeah, one of the annoying things of building large C packages is when the maintainers don't care about warnings, and then legit errors get lost in the spam. >> The package doesn't seem to have had a release since 2018, but the >> GitHub repository has had changes as recently as a month ago. You >> might have better luck cloning the repo and building that. > > > Thanks, good suggestion. > > FWIW, I'm trying to whittle down at least 12,000 images to a more manageable > number for the sister of a good friend who recently passed away. I've got a > straightforward dedupe program, but need something which can compare just the > data chunk of JPEGs, ignoring the metadata. This program apparently does > that. Is like to avoid reinventing that wheel. > Makes sense! Though if you're just doing a bitwise comparison of the data chunks, it shouldn't be TOO hard to reinvent. JFIF is a reasonably easy format to understand (although the mathematics of image encoding and decoding are a bit less so). ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Re: Package conflicts trying to install jpegdupes package
> > Those are all warnings. Are there any errors that follow them? > Maybe I just missed the actual errors, but the compiler exit status was 1, so there must have been. I'll give it another try. The package doesn't seem to have had a release since 2018, but the > GitHub repository has had changes as recently as a month ago. You > might have better luck cloning the repo and building that. > Thanks, good suggestion. FWIW, I'm trying to whittle down at least 12,000 images to a more manageable number for the sister of a good friend who recently passed away. I've got a straightforward dedupe program, but need something which can compare just the data chunk of JPEGs, ignoring the metadata. This program apparently does that. Is like to avoid reinventing that wheel. Skip -- https://mail.python.org/mailman/listinfo/python-list
Re: Python added to PATH, cannot be directly accessed, cannot install pip
On 9/27/21, Will wrote: > >I am using a Lenovo Laptop using Windows. I'm trying to install >get-pip.py The installer includes pip by default and has an option to update PATH for you, though the latter isn't enabled by default. Latest 64-bit release: https://www.python.org/ftp/python/3.9.7/python-3.9.7-amd64.exe -- https://mail.python.org/mailman/listinfo/python-list
Re: Package conflicts trying to install jpegdupes package
On Mon, Sep 27, 2021 at 10:49 PM Skip Montanaro wrote: > > I'd like to use the jpegdupes package <https://pypi.org/project/jpegdupes/> > but > can't seem to get past compilation issued related to jpegtrans-cffi. > Attempts to install any available versions on my XUbuntu system crap out > with this C compiler error message: > > In file included from > jpegtran/__pycache__/_cffi__xd2d84bdexcdb1023.c:267: > src/epeg_private.h:71:17: warning: ‘_jpeg_init_source’ declared > ‘static’ but never defined [-Wunused-function] >71 | METHODDEF(void) _jpeg_init_source(j_decompress_ptr cinfo); > | ^ > src/epeg_private.h:72:20: warning: ‘_jpeg_fill_input_buffer’ declared > ‘static’ but never defined [-Wunused-function] >72 | METHODDEF(boolean) _jpeg_fill_input_buffer(j_decompress_ptr > cinfo); > |^~~ > src/epeg_private.h:73:17: warning: ‘_jpeg_skip_input_data’ declared > ‘static’ but never defined [-Wunused-function] >73 | METHODDEF(void) _jpeg_skip_input_data(j_decompress_ptr cinfo, > long num_bytes); > | ^ > src/epeg_private.h:74:17: warning: ‘_jpeg_term_source’ declared > ‘static’ but never defined [-Wunused-function] >74 | METHODDEF(void) _jpeg_term_source(j_decompress_ptr cinfo); > | ^ > src/epeg_private.h:76:17: warning: ‘_jpeg_init_destination’ declared > ‘static’ but never defined [-Wunused-function] >76 | METHODDEF(void) _jpeg_init_destination(j_compress_ptr cinfo); > | ^~ > src/epeg_private.h:77:20: warning: ‘_jpeg_empty_output_buffer’ declared > ‘static’ but never defined [-Wunused-function] >77 | METHODDEF(boolean) _jpeg_empty_output_buffer (j_compress_ptr > cinfo); > |^ > src/epeg_private.h:78:17: warning: ‘_jpeg_term_destination’ declared > ‘static’ but never defined [-Wunused-function] >78 | METHODDEF(void) _jpeg_term_destination (j_compress_ptr cinfo); > | ^~ Those are all warnings. Are there any errors that follow them? > ... > This seems like a rather odd error message for a presumably sort-of-stable > PyPI package. Looking at the version dependencies I see 2.6, 2.7, 3.3 or > PyPy. I thought nmybe I needed to try with Python2... Create a Conda > environment, attempt to install jpegdupes, only to discover it's Python 3 > only. > > So, I'm kind of stuck. Maybe I need to install Python 3.3 and try that? Any > other ideas? > The package doesn't seem to have had a release since 2018, but the GitHub repository has had changes as recently as a month ago. You might have better luck cloning the repo and building that. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
Python added to PATH, cannot be directly accessed, cannot install pip
Hello team at python.org,
I've asked this question on a forum and tried to figure it out myself, but
I'm at a dead end. I don't know if you guys answer questions like this but
I have no where else to turn to.
I am using a Lenovo Laptop using Windows. I'm trying to install
get-pip.py, and when I enter "python get-pip.py" into the Command Prompt,
it says "Python was not found; run without arguments to install from the
Microsoft Store, or disable this shortcut from Settings > Manage App
Execution Aliases."
So for a week, I've been trying to add Python to PATH, so I can install
get-pip.py to Python.
I've added the exact file location for Python to Path in both User
Variables and System Variables. I've executed Manage App Execution
Aliases, turned off both App Installer python.exe and App Installer
python3.exe. Still can't install pip, Python was still not found. I've
tried different keywords ("py get-pip.py", python3 get-pip.py", etc.).
Still doesn't work.
Python is added to PATH and I can still run Python scripts, but I can't
find Python directly through the Command Prompt, and I cannot install
get-pip.py to Python.
For reference, I have Python version 3.9.6 and I installed Python directly
from the site (I did not use Anaconda).
Can you guys help me with this? Or do I need to delete Python and
reinstall it?
Sincerely, Will
--
https://mail.python.org/mailman/listinfo/python-list
Package conflicts trying to install jpegdupes package
I'd like to use the jpegdupes package <https://pypi.org/project/jpegdupes/> but can't seem to get past compilation issued related to jpegtrans-cffi. Attempts to install any available versions on my XUbuntu system crap out with this C compiler error message: In file included from jpegtran/__pycache__/_cffi__xd2d84bdexcdb1023.c:267: src/epeg_private.h:71:17: warning: ‘_jpeg_init_source’ declared ‘static’ but never defined [-Wunused-function] 71 | METHODDEF(void) _jpeg_init_source(j_decompress_ptr cinfo); | ^ src/epeg_private.h:72:20: warning: ‘_jpeg_fill_input_buffer’ declared ‘static’ but never defined [-Wunused-function] 72 | METHODDEF(boolean) _jpeg_fill_input_buffer(j_decompress_ptr cinfo); |^~~ src/epeg_private.h:73:17: warning: ‘_jpeg_skip_input_data’ declared ‘static’ but never defined [-Wunused-function] 73 | METHODDEF(void) _jpeg_skip_input_data(j_decompress_ptr cinfo, long num_bytes); | ^ src/epeg_private.h:74:17: warning: ‘_jpeg_term_source’ declared ‘static’ but never defined [-Wunused-function] 74 | METHODDEF(void) _jpeg_term_source(j_decompress_ptr cinfo); | ^ src/epeg_private.h:76:17: warning: ‘_jpeg_init_destination’ declared ‘static’ but never defined [-Wunused-function] 76 | METHODDEF(void) _jpeg_init_destination(j_compress_ptr cinfo); | ^~ src/epeg_private.h:77:20: warning: ‘_jpeg_empty_output_buffer’ declared ‘static’ but never defined [-Wunused-function] 77 | METHODDEF(boolean) _jpeg_empty_output_buffer (j_compress_ptr cinfo); |^ src/epeg_private.h:78:17: warning: ‘_jpeg_term_destination’ declared ‘static’ but never defined [-Wunused-function] 78 | METHODDEF(void) _jpeg_term_destination (j_compress_ptr cinfo); | ^~ ... This seems like a rather odd error message for a presumably sort-of-stable PyPI package. Looking at the version dependencies I see 2.6, 2.7, 3.3 or PyPy. I thought nmybe I needed to try with Python2... Create a Conda environment, attempt to install jpegdupes, only to discover it's Python 3 only. So, I'm kind of stuck. Maybe I need to install Python 3.3 and try that? Any other ideas? Thx, Skip -- https://mail.python.org/mailman/listinfo/python-list
Re: help me please. "install reppy"
See here for a discussion around this issue: https://github.com/seomoz/reppy/issues/90 This project requires a C++ build environment to be setup on your computer. The fact that your compiler is reporting that `std=c++11` as an unknown option shows that you don't have a C++ build environment set up. As you will see, at the end of the issue above, they link to this issue: https://github.com/Benny-/Yahoo-ticker-symbol-downloader/issues/46 In that second issue, a user reports: > hey all. I solved the issue by installing Build tools for visual c++ 2015 (v14). The link does not work. > You have to look for build tools for visual studio 2017 (v15) and look at the options in the installer. As a side note, you might consider using this robots.txt parser from the standard library instead. It's already installed and ready to go, and doesn't use very-overkill C++ dependencies! Good luck! On Thu, Jul 22, 2021 at 8:44 PM たこしたこし wrote: > I get an error so please help. > I don't know what to do. > > Windows 10 > Python 3.9.6 > > from takashi in Japan > -- > https://mail.python.org/mailman/listinfo/python-list > -- https://mail.python.org/mailman/listinfo/python-list
Re: help me please. "install reppy"
Oops, forgot the link to the standard library robots.txt parser. Here are the docs! https://docs.python.org/3/library/urllib.robotparser.html *sorry for the noise* On Thu, Jul 22, 2021 at 11:34 PM Jack DeVries wrote: > See here for a discussion around this issue: > https://github.com/seomoz/reppy/issues/90 > > This project requires a C++ build environment to be setup on your > computer. The fact that your compiler is reporting that `std=c++11` as an > unknown option shows that you don't have a C++ build environment set up. As > you will see, at the end of the issue above, they link to this issue: > > https://github.com/Benny-/Yahoo-ticker-symbol-downloader/issues/46 > > In that second issue, a user reports: > > hey all. I solved the issue by installing Build tools for visual c++ > 2015 (v14). The link does not work. > > You have to look for build tools for visual studio 2017 (v15) and look > at the options in the installer. > > As a side note, you might consider using this robots.txt parser from the > standard library instead. It's already installed and ready to go, and > doesn't use very-overkill C++ dependencies! > > Good luck! > > > On Thu, Jul 22, 2021 at 8:44 PM たこしたこし wrote: > >> I get an error so please help. >> I don't know what to do. >> >> Windows 10 >> Python 3.9.6 >> >> from takashi in Japan >> -- >> https://mail.python.org/mailman/listinfo/python-list >> > -- https://mail.python.org/mailman/listinfo/python-list
