Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

On Fri, Nov 13, 2009 at 09:59, Sriram Srinivasan wrote: > you were thinking wrong. If suppose this feature is introduced it doesn't > mean python will become batteries removed! > you can ship the python release with the 'standard library packages' already > installed. > so what we get here is batt

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

On Nov 13, 2009, at 6:23 PM, Greg Ewing wrote: Martin v. Löwis wrote: > Some of the Python maintainers have recently started objecting to this > setup, asking that the standard library should be split into separate > packages that are released and distributed independent of Python. Other

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

Martin v. Löwis wrote: > Some of the Python maintainers have recently started objecting to this > setup, asking that the standard library should be split into separate > packages that are released and distributed independent of Python. Others > of us feel strongly that such a change should not be

[Python-Dev] standard libraries don't behave like standard 'libraries'

> Sriram, > > Please take this discussion to catalog-sig - python-dev isn't the place > (the fact that many of us didn't immediately know the *right* place for > the discussion indicates where PyPI sits on our personal active level of > interest). > > You should find more interested (and knowledgab

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

On Fri, Nov 13, 2009 at 6:44 PM, Steven D'Aprano wrote: > On Fri, 13 Nov 2009 09:36:10 pm Anand Balachandran Pillai wrote: > > > It could be something as simple as a "require" keyword which could > > pull in the depdencies if not found. Perhaps at the top of your > > module, > > > > require (stu

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

On Fri, 13 Nov 2009 09:36:10 pm Anand Balachandran Pillai wrote: > It could be something as simple as a "require" keyword which could >  pull in the depdencies if not found. Perhaps at the top of your > module, > >  require (stuff, '1.27') >  import stuff So Python, the *language*, has to become

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

Sriram Srinivasan wrote: > http://pypi.python.org/pypi?%3Aaction=search&term=library&submit=search > > > this lists all the packages with the term 'library' in it. Sriram, Please take this discussion to catalog-sig - pytho

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

http://pypi.python.org/pypi?%3Aaction=search&term=library&submit=search this lists all the packages with the term 'library' in it. -- Regards, Sriram. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

as people like to compare languages take ruby for example (i am confident that there will be no flame war here ;) ) we have PyPI they have RAA we have ? they have rubyforge i am seeing the rubyforge site now on my other tab, i find Communications (365 projects) Database (245 projects) Desktop E

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

On 13 Nov 2009, at 11:36 , Anand Balachandran Pillai wrote: > I think the recent postings on "CPAN for Python" in this list also stems > from similar thoughts. No. The CPAN for Python messages (in and out of the list) are about third-party packages and a better way to manage (and a better experie

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

On Fri, Nov 13, 2009 at 1:08 AM, "Martin v. Löwis" wrote: > > I am not an expert, I am just another python learner. These are just my > > views on the state of the standard libraries and to > > make them state-of-the-art..! ;) > > If I understand correctly, you want the (current) standard library

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

On Fri, Nov 13, 2009 at 9:35 AM, Kevin Teague wrote: > > It's also worth noting that there are three issues with respect to standard > library packaging which are all orthologous: > >  * Packaging for metadata: The standard library could be packaged so that > there is consistent metadata about the

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

you were thinking wrong. If suppose this feature is introduced it doesn't mean python will become batteries removed! you can ship the python release with the 'standard library packages' already installed. so what we get here is batteries included and ability to be changed after it is discharged! ;)

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

On Nov 12, 2009, at 11:57 AM, Jesse Noller wrote: On Thu, Nov 12, 2009 at 2:38 PM, "Martin v. Löwis" wrote: I am not an expert, I am just another python learner. These are just my views on the state of the standard libraries and to make them state-of-the-art..! ;) If I understand correct

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

On Thu, Nov 12, 2009 at 2:38 PM, "Martin v. Löwis" wrote: >> I am not an expert, I am just another python learner. These are just my >> views on the state of the standard libraries and to >> make them state-of-the-art..! ;) > > If I understand correctly, you want the (current) standard library to

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

Sriram Srinivasan schrieb: > I guess why every programming language has some kind of a 'standard > library' built in within it. In my view it must not be called as a > 'library' at all. what it does > is like a 'bunch of built-in programs ready-made to do stuff'. > > Lets see what a 'library' does

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

> I am not an expert, I am just another python learner. These are just my > views on the state of the standard libraries and to > make them state-of-the-art..! ;) If I understand correctly, you want the (current) standard library to be separated from the Python implementation, and available separa

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

2009/11/12 Sriram Srinivasan : > In python we have the PyPI which is equivalent to the http://devpacks.org > but in PyPI the packages are all user made applications. > What I want is similar to PyPI but for the python standard libraries, so > that they (libraries) are as add-on as possible. They a

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

Matthew Wilkes wrote: > There are plenty of other ways to manage this, most people use systems > like virtualenv or buildout, but that's a discussion for the normal > python mailing list, not the development one. Indeed. Please take this to python-list (it isn't even a coherent enough suggestion f

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

Oh, I see. use library 1.1.5 versus use library 1.1.6 #thats all now i get all features That's part of pkg_resources. It looks like this: pkg_resources.require("mylibrary==1.1.6") import mylibrary There are plenty of other ways to manage this, most people use systems like virtualenv o

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

ok let me make it more clear.. forget how you use python now.. i am talking about __futuristic__ python programming. these are just my ideas.. more over i can say imaginations. there is no more python2.x or python3.x or python y.x releases. there is only updates of python and standard library say

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

On 2009-11-12, at 1136, Sriram Srinivasan wrote: standard libraries i meant the standard libraries used. and what i asked for is for(in python) both the standard-libraries and the standard libraries used. c the term (intra and inter library management) which includes the default standard li

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

> I disagree. It has a package management system for libraries, not for the > standard libraries. The point is that the Python standard library is > supplied > as part of Python itself, as is e.g. the C++ standard library as part of a > C++ compiler. > > standard libraries i meant the standard libr

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

On Thursday 12 November 2009, Sriram Srinivasan wrote: > I don't know if you have used Dev-C++. It has a 'package management' > mechanism for the standard libraries. I disagree. It has a package management system for libraries, not for the standard libraries. The point is that the Python standard

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

> > I don't really understand your requirements, but it sound like you want a > package management system. The standard library just provides a standard set > of tools (it is the books not the book management system - although part of > what you want is in the standard library in the form of distut

Re: [Python-Dev] standard libraries don't behave like standard 'libraries'

Sriram Srinivasan wrote: I guess why every programming language has some kind of a 'standard library' built in within it. In my view it must not be called as a 'library' at all. what it does is like a 'bunch of built-in programs ready-made to do stuff'. Lets see what a 'library' does: 1. offe

[Python-Dev] standard libraries don't behave like standard 'libraries'

I guess why every programming language has some kind of a 'standard library' built in within it. In my view it must not be called as a 'library' at all. what it does is like a 'bunch of built-in programs ready-made to do stuff'. Lets see what a 'library' does: 1. offers books for customers 1.1 l