From: Roman S. <rn...@on...> - 2001-09-05 05:43:26
|
Hi! I've made setup.py and MANIFEST.in for the PythonCardPrototype. (For now Kevin posted them as attachments) Now (if Python 2.x is properly installed) it is possible to make source and binary distros this way (in the root directory of the source distro): python setup.py sdist python setup.py bdist_rpm python setup.py bdist_wininst python setup.py bdist --format=zip Right now, Distutil support is not full: setup.cfg with meta-information fields specific to different binary distribution methods is missing. Sincerely yours, Roman A.Suzi -- - Petrozavodsk - Karelia - Russia - mailto:rn...@on... - |
From: Andy T. <an...@cr...> - 2001-09-09 08:46:25
|
Roman Suzi wrote: > Hi! > > I've made setup.py and MANIFEST.in for the PythonCardPrototype. > (For now Kevin posted them as attachments) And I've made some minor cosmetic changes and posted them into cvs. I've also had to include a README.txt in the root directory (distutils requires one apparently), but I just copied the one from the docs directory. > > Now (if Python 2.x is properly installed) it is possible to > make source and binary distros this way (in the root directory > of the source distro): > > python setup.py sdist > python setup.py bdist_rpm > python setup.py bdist_wininst > python setup.py bdist --format=zip We don't need to bdist (yet) as we have no binary (i.e. needing some sort of compilation step) components in PythonCard. I have created two source distributions, one for Windows and one for *nix. Before making them the 'official' releases for the project I've posted them on the web site for initial testing by the subscribers to this list. You can get the source distributions at http://pythoncard.sourceforge.net/dist/ To install from one of these distributions; - Copy the appropriate file to your machine - Unpack it to a temporary directory (using WinZip on Windows or "tar -xzf PythonCardPrototype-0.4.4.5.tar.gz" on *nix) - This will create a directory called "PythonCardPrototype-0.4.4.5", cd to that directory, then; - Run the standard distutils install command ("python setup.py install") - The framework code will then be installed as a module in your Python set up (in the directory $PYTHON_HOME/PythonCardPrototype) - The sample applications will be installed in a PythonCard directory in the share directory under your Python Home. - Finally, you can remove the working directory you created by unpacking the distribution above. > > > Right now, Distutil support is not full: setup.cfg with meta-information > fields specific to different binary distribution methods is missing. > As I said, we don't need this yet so we have a complete set up. If we ever get to the stage of performing some come of compile step at least Roman has an idea of what we need to do. I will post the steps to created these distributions tomorrow, for those who want to act as release managers when we cut a new version. In the meantime, if these distributions are OK perhaps someone could post them to the file release system on SourceForge. > > > Sincerely yours, Roman A.Suzi > As ever, any and all feedback is welcome. Regards, Andy -- ----------------------------------------------------------------------- From the desk of Andrew J Todd esq. "Shave my poodle!" |
From: Roman S. <rn...@on...> - 2001-09-09 16:02:24
|
On Sun, 9 Sep 2001, Andy Todd wrote: >Roman Suzi wrote: > > Hi! > > > > I've made setup.py and MANIFEST.in for the PythonCardPrototype. > > (For now Kevin posted them as attachments) > >And I've made some minor cosmetic changes and posted them into cvs. >I've also had to include a README.txt in the root directory (distutils >requires one apparently), but I just copied the one from the docs directory. Well. I've just got tar.gz with soource distribution. I noticed that MANIFEST file should not be there! Only MANIFEST.in It is created as a result of setup.py. The presence of MANIFEST could have some side effects on people who forgot to delete it when switching to version. So, the general advice is to run setup.py sdist to get source distribution right. Distutils strip all CVS's and things like that automatically, so it is OK to run them in the chkedout directory. > > Now (if Python 2.x is properly installed) it is possible to > > make source and binary distros this way (in the root directory > > of the source distro): Sincerely yours, Roman Suzi -- _/ Russia _/ Karelia _/ Petrozavodsk _/ rn...@on... _/ _/ Sunday, September 09, 2001 _/ Powered by Linux RedHat 6.2 _/ _/ "Another case of Cherry Coke down the programming hatch!" _/ |
From: Andy T. <an...@cr...> - 2001-09-09 23:20:38
|
Roman Suzi wrote: > On Sun, 9 Sep 2001, Andy Todd wrote: > > >>Roman Suzi wrote: >> >>>Hi! >>> >>>I've made setup.py and MANIFEST.in for the PythonCardPrototype. >>>(For now Kevin posted them as attachments) >>> >>And I've made some minor cosmetic changes and posted them into cvs. >>I've also had to include a README.txt in the root directory (distutils >>requires one apparently), but I just copied the one from the docs directory. >> > > Well. I've just got tar.gz with soource distribution. > > I noticed that MANIFEST file should not be there! Only MANIFEST.in > It is created as a result of setup.py. The presence of MANIFEST could > have some side effects on people who forgot to delete it > when switching to version. > I just checked the tar.gz and zip versions from http://pythoncard.sourceforge.net/dist and they only include the MANIFEST.in file. I'm not even sure we need this in a source distribution anyway as it is only used when creating the archive and is ignored when you unpack it and run 'python setup.py install'. But I'd be glad to hear your thoughts on the matter ... > So, the general advice is to run > > setup.py sdist Actually, I'm running 'python setup.py sdist --formats=gztar,zip' to get both source distributions. We don't want to exclude anyone here ;-) > > to get source distribution right. Distutils strip all CVS's and things > like that automatically, so it is OK to run them in the chkedout > directory. Which is what I have done. > > >>>Now (if Python 2.x is properly installed) it is possible to >>>make source and binary distros this way (in the root directory >>>of the source distro): >>> > > Sincerely yours, Roman Suzi > Regards, Andy -- ----------------------------------------------------------------------- From the desk of Andrew J Todd esq. "Shave my poodle!" |
From: Kevin A. <al...@se...> - 2001-09-09 18:01:50
|
> - Run the standard distutils install command ("python setup.py install") This is one of my pet peeves about distutils. The default is always "setup.py install" but if you only have one Python installation (on Windows at least) you should just be able to run "setup.py" from the Explorer without specifying the "install" command-line option. Perhaps we should provide a setup_install.bat file for Windows? Would it be okay to actually modify "setup.py" so that if the user didn't specify a command-line option it would default to "install" ? We'll need an installation for PyCrust as well. Patrick, is this something you want to tackle for the 0.6 PyCrust release? ka |
From: Roman S. <rn...@on...> - 2001-09-09 18:31:29
|
On Sun, 9 Sep 2001, Kevin Altis wrote: >> - Run the standard distutils install command ("python setup.py install") > >This is one of my pet peeves about distutils. The default is always >"setup.py install" but if you only have one Python installation (on Windows >at least) you should just be able to run "setup.py" from the Explorer >without specifying the "install" command-line option. Perhaps we should >provide a setup_install.bat file for Windows? Would it be okay to actually >modify "setup.py" so that if the user didn't specify a command-line option >it would default to "install" ? I wished Distutils to have some window popup with options for those people who do not hesitate to run things before looking what they are. Just after second line of setup.py: ----------------------------------------- WIN_DEFAULT_COMMAND = "install" import sys if len(sys.argv) == 1 and sys.platform.startswith("win"): sys.argv.append(WIN_DEFAULT_COMMAND) ----------------------------------------- >We'll need an installation for PyCrust as well. Patrick, is this something >you want to tackle for the 0.6 PyCrust release? Sincerely yours, Roman Suzi -- _/ Russia _/ Karelia _/ Petrozavodsk _/ rn...@on... _/ _/ Sunday, September 09, 2001 _/ Powered by Linux RedHat 6.2 _/ _/ "Another case of Cherry Coke down the programming hatch!" _/ |
From: Kevin A. <al...@se...> - 2001-09-09 18:53:21
|
Okay, you got me. I'll shut up now. ka > -----Original Message----- > From: pyt...@li... > [mailto:pyt...@li...]On Behalf Of Roman > Suzi > Sent: Sunday, September 09, 2001 11:30 AM > To: pyt...@li... > Subject: RE: [Pythoncard-users] PythonCard and Distutils > > > On Sun, 9 Sep 2001, Kevin Altis wrote: > > >> - Run the standard distutils install command ("python setup.py > install") > > > >This is one of my pet peeves about distutils. The default is always > >"setup.py install" but if you only have one Python installation > (on Windows > >at least) you should just be able to run "setup.py" from the Explorer > >without specifying the "install" command-line option. Perhaps we should > >provide a setup_install.bat file for Windows? Would it be okay > to actually > >modify "setup.py" so that if the user didn't specify a > command-line option > >it would default to "install" ? > > I wished Distutils to have some window popup with options for those > people who do not hesitate to run things before looking what they are. > > Just after second line of setup.py: > ----------------------------------------- > WIN_DEFAULT_COMMAND = "install" > import sys > if len(sys.argv) == 1 and sys.platform.startswith("win"): > sys.argv.append(WIN_DEFAULT_COMMAND) > ----------------------------------------- > > >We'll need an installation for PyCrust as well. Patrick, is this > something > >you want to tackle for the 0.6 PyCrust release? > > Sincerely yours, Roman Suzi > -- > _/ Russia _/ Karelia _/ Petrozavodsk _/ rn...@on... _/ > _/ Sunday, September 09, 2001 _/ Powered by Linux RedHat 6.2 _/ > _/ "Another case of Cherry Coke down the programming hatch!" _/ > > > _______________________________________________ > Pythoncard-users mailing list > Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/pythoncard-users > |
From: Andy T. <an...@cr...> - 2001-09-09 23:24:05
|
Roman Suzi wrote: > On Sun, 9 Sep 2001, Kevin Altis wrote: > > >>>- Run the standard distutils install command ("python setup.py install") >>> >>This is one of my pet peeves about distutils. The default is always >>"setup.py install" but if you only have one Python installation (on Windows >>at least) you should just be able to run "setup.py" from the Explorer >>without specifying the "install" command-line option. Perhaps we should >>provide a setup_install.bat file for Windows? Would it be okay to actually >>modify "setup.py" so that if the user didn't specify a command-line option >>it would default to "install" ? >> > > I wished Distutils to have some window popup with options for those > people who do not hesitate to run things before looking what they are. > > Just after second line of setup.py: > ----------------------------------------- > WIN_DEFAULT_COMMAND = "install" > import sys > if len(sys.argv) == 1 and sys.platform.startswith("win"): > sys.argv.append(WIN_DEFAULT_COMMAND) > ----------------------------------------- > I'll apply this patch to setup.py and test it with the next release of the prototype, thanks. > >>We'll need an installation for PyCrust as well. Patrick, is this something >>you want to tackle for the 0.6 PyCrust release? >> > > Sincerely yours, Roman Suzi > Regards, Andy -- ----------------------------------------------------------------------- From the desk of Andrew J Todd esq. "Shave my poodle!" |
From: Andy T. <an...@cr...> - 2001-09-10 12:03:33
|
Andy Todd wrote: > Roman Suzi wrote: > >> On Sun, 9 Sep 2001, Kevin Altis wrote: >> >> >>>> - Run the standard distutils install command ("python setup.py >>>> install") >>>> >>> This is one of my pet peeves about distutils. The default is always >>> "setup.py install" but if you only have one Python installation (on >>> Windows >>> at least) you should just be able to run "setup.py" from the Explorer >>> without specifying the "install" command-line option. Perhaps we should >>> provide a setup_install.bat file for Windows? Would it be okay to >>> actually >>> modify "setup.py" so that if the user didn't specify a command-line >>> option >>> it would default to "install" ? >>> >> >> I wished Distutils to have some window popup with options for those >> people who do not hesitate to run things before looking what they are. >> >> Just after second line of setup.py: >> ----------------------------------------- >> WIN_DEFAULT_COMMAND = "install" >> import sys >> if len(sys.argv) == 1 and sys.platform.startswith("win"): >> sys.argv.append(WIN_DEFAULT_COMMAND) >> ----------------------------------------- >> > I've updated the setup.py to keep the sample applications with the framework code rather than in their own seperate directory. I've also been playing around with binary distributions, and have managed to create a self extracting .exe for windows. Unfortunately this only contains the top level of files, so if anyone would like to point out how I get the whole directory structure included I'd appreciate it. I've updated the files in http://pythoncard.sourceforge.net/dist and would appreciate as much testing and feedback as possible. Thanks in advance, Andy -- ----------------------------------------------------------------------- From the desk of Andrew J Todd esq. "Shave my poodle!" |
From: Patrick K. O'B. <po...@or...> - 2001-09-09 19:22:12
|
This definitely needs to be done. I will do it myself if nobody wants to volunteer. If someone does volunteer, I'd like to learn how it all works. And what about a real installer, such as Inno Setup, in addition to distutils? I think these are what Neil and Robin use: http://www.jrsoftware.org/isinfo.htm http://www.bhenden.org/istool/ --- Patrick K. O'Brien Orbtech (http://www.orbtech.com) "I am, therefore I think." -----Original Message----- From: pyt...@li... [mailto:pyt...@li...]On Behalf Of Kevin Altis Sent: Sunday, September 09, 2001 1:03 PM To: pyt...@li... Subject: RE: [Pythoncard-users] PythonCard and Distutils <snip> We'll need an installation for PyCrust as well. Patrick, is this something you want to tackle for the 0.6 PyCrust release? ka |
From: Andy T. <an...@cr...> - 2001-09-09 22:47:40
|
Patrick, Patrick K. O'Brien wrote: > This definitely needs to be done. I will do it myself if nobody wants to > volunteer. If someone does volunteer, I'd like to learn how it all works. I'll give this a bash if you like, now that I'm a seasoned packager ;-) Shouldn't be too much trouble, I'll keep you informed on progress. > And what about a real installer, such as Inno Setup, in addition to > distutils? I think these are what Neil and Robin use: > > http://www.jrsoftware.org/isinfo.htm > > http://www.bhenden.org/istool/ > Good idea, but maybe when both projects are out of the prototype stage? Not that I would want anyone to not try them out though ... > --- > Patrick K. O'Brien > Orbtech (http://www.orbtech.com) > "I am, therefore I think." > > -----Original Message----- > From: pyt...@li... > [mailto:pyt...@li...]On Behalf Of Kevin > Altis > Sent: Sunday, September 09, 2001 1:03 PM > To: pyt...@li... > Subject: RE: [Pythoncard-users] PythonCard and Distutils > > <snip> > > We'll need an installation for PyCrust as well. Patrick, is this something > you want to tackle for the 0.6 PyCrust release? > > ka > > Regards, Andy -- ----------------------------------------------------------------------- From the desk of Andrew J Todd esq. "Shave my poodle!" |
From: Patrick K. O'B. <po...@or...> - 2001-09-09 23:31:50
|
That would be wonderful. Thanks, Andy. --- Patrick K. O'Brien Orbtech (http://www.orbtech.com) "I am, therefore I think." -----Original Message----- From: pyt...@li... [mailto:pyt...@li...]On Behalf Of Andy Todd Sent: Sunday, September 09, 2001 5:45 PM To: pyt...@li... Subject: Re: [Pythoncard-users] PythonCard and Distutils Patrick, Patrick K. O'Brien wrote: > This definitely needs to be done. I will do it myself if nobody wants to > volunteer. If someone does volunteer, I'd like to learn how it all works. I'll give this a bash if you like, now that I'm a seasoned packager ;-) Shouldn't be too much trouble, I'll keep you informed on progress. |