Posted by: Anonymous Coward
on December 10, 2004 09:26 AM
Well, if you are really concerned that your application should call a specific version of python, you'd invoke it explicitly, say
#!/usr/bin/python2.1
That way, should the default python change to say 2.3 (which would happen in sarge), applications relying on custom modules built on that particular version of Python would still work.
By default, `python` is a hard link to the default version of Python offered by the distribution.
If you used the default invocation, say #!/usr/bin/python for Python or #!/usr/bin/perl for Perl programs, don't expect that the package manager would upgrade custom-made modules for you. The good thing is that Debian has meta-packages for the modules too, e.g.
python-reportlab depends on python2.3-reportlab. But there are also packages python2.2-reportlab and python2.1-reportlab so there's no real confusion.
The concept of meta packages is quite good when the names of the package change - this way you avoid breakage of the system.
Learn about Linux
Download Linux
Get Linux help
Re:thanks for the good info!
Posted by: Anonymous Coward on December 10, 2004 09:26 AM#!/usr/bin/python2.1
That way, should the default python change to say 2.3 (which would happen in sarge), applications relying on custom modules built on that particular version of Python would still work.
By default, `python` is a hard link to the default version of Python offered by the distribution.
If you used the default invocation, say
#!/usr/bin/python for Python or #!/usr/bin/perl for Perl programs, don't expect that the package manager would upgrade custom-made modules for you. The good thing is that Debian has meta-packages for the modules too, e.g.
python-reportlab depends on python2.3-reportlab. But there are also packages python2.2-reportlab and python2.1-reportlab so there's no real confusion.
The concept of meta packages is quite good when the names of the package change - this way you avoid breakage of the system.
#