distutils change breaks code, Pyfort
So this is clearly an incompatible change. According with the procedures in PEP 5, there should be a warning issued before aborting setup. Later (major) releases of Python, or distutils, could change the warning into an error. Nevertheless, I agree with the change in principal. Distutils can and should enforce a certain amount of policy; among this, having a version number sounds like a reasonable requirement - even though its primary use is for building (and uploading) distributions. Are you saying that Pyfort does not have a version number? On SF, I can get version 6.3... Regards, Martin
Pyfort is the kind of package the change was intended for, and it does have a version number. But I have other packages, that cannot stand on their own, that are part of a bigger suite of packages, and dist is never going to be used. They don't have a MANIFEST, etc. The setup.py file is used instead of a Makefile. I don't think that it is logical to require a version number that is not used in that case. We also raise the "entry fee" for learning to use Distutils or starting a new package. In the case of Pyfort there is NO setup.py, it is just running a command on the fly. But I've already fixed it with version 6.3. I think we have all focused on the public distribution problem but in fact Distutils is just great as an internal tool for building large software projects and that is how I use it. I agree that if I want to use sdist, bdist etc. that I need to set the version. But then, I need to do other things too in that case. -----Original Message----- From: Martin v. Loewis [mailto:martin@loewis.home.cs.tu-berlin.de] Sent: Saturday, March 24, 2001 4:47 PM To: paul@pfdubois.com Cc: python-dev@python.org Subject: distutils change breaks code, Pyfort
So this is clearly an incompatible change. According with the procedures in PEP 5, there should be a warning issued before aborting setup. Later (major) releases of Python, or distutils, could change the warning into an error. Nevertheless, I agree with the change in principal. Distutils can and should enforce a certain amount of policy; among this, having a version number sounds like a reasonable requirement - even though its primary use is for building (and uploading) distributions. Are you saying that Pyfort does not have a version number? On SF, I can get version 6.3... Regards, Martin
"PFD" == Paul F Dubois <paul@pfdubois.com> writes:
PFD> I think we have all focused on the public distribution PFD> problem but in fact Distutils is just great as an internal PFD> tool for building large software projects and that is how I PFD> use it. I've used it this way too, and you're right, it's great for this. Esp. for extensions, it's much nicer than fiddling with Makefile.pre.in's etc. So I think I agree with you about the version numbers and other required metadata -- or at least, there should be an escape. -Barry
Pyfort is the kind of package the change was intended for, and it does have a version number. But I have other packages, that cannot stand on their own, that are part of a bigger suite of packages, and dist is never going to be used. They don't have a MANIFEST, etc. The setup.py file is used instead of a Makefile. I don't think that it is logical to require a version number that is not used in that case. We also raise the "entry fee" for learning to use Distutils or starting a new package. In the case of Pyfort there is NO setup.py, it is just running a command on the fly. But I've already fixed it with version 6.3. I think we have all focused on the public distribution problem but in fact Distutils is just great as an internal tool for building large software projects and that is how I use it. I agree that if I want to use sdist, bdist etc. that I need to set the version. But then, I need to do other things too in that case. -----Original Message----- From: Martin v. Loewis [mailto:martin@loewis.home.cs.tu-berlin.de] Sent: Saturday, March 24, 2001 4:47 PM To: paul@pfdubois.com Cc: python-dev@python.org Subject: distutils change breaks code, Pyfort
So this is clearly an incompatible change. According with the procedures in PEP 5, there should be a warning issued before aborting setup. Later (major) releases of Python, or distutils, could change the warning into an error. Nevertheless, I agree with the change in principal. Distutils can and should enforce a certain amount of policy; among this, having a version number sounds like a reasonable requirement - even though its primary use is for building (and uploading) distributions. Are you saying that Pyfort does not have a version number? On SF, I can get version 6.3... Regards, Martin
"PFD" == Paul F Dubois <paul@pfdubois.com> writes:
PFD> I think we have all focused on the public distribution PFD> problem but in fact Distutils is just great as an internal PFD> tool for building large software projects and that is how I PFD> use it. I've used it this way too, and you're right, it's great for this. Esp. for extensions, it's much nicer than fiddling with Makefile.pre.in's etc. So I think I agree with you about the version numbers and other required metadata -- or at least, there should be an escape. -Barry
participants (3)
-
barry＠digicool.com -
Martin v. Loewis -
Paul F. Dubois