Re: [cclib-devel] Final release of 0.5

[Noel O'B. <no...@ca...>]

On Wed, 2006-06-21 at 16:08 -0700, Adam Tenderholt wrote:
> > Well, I want to use whatever the standard method is. I create the
> > Windows distribution using standard disutils commands:
> > python setup.py sdist    (to create the .tar.gz for Linux)
> > python setup.py bdist_wininst (to create the windows installer)
> >
> > There's no option (at least with the distutils supplied in Linux) to
> > create a Mac installer. I would expect Mac users to just do as Linux
> > users do. I wouldn't worry about anything more.
> 
> I was thinking there was something like bdist_mpkg, but I guess I was  
> wrong. Maybe that's an option for setup.py when py2app is being used.  
> Do you know if the bdist option just byte-compiles the source for  
> that specific plaform? Just curious. Source distribution makes sense  
> as well for Mac since it's pretty easy to fire up a terminal and run  
> python setup.py install. I suspect anyone using cclib on the Mac is  
> going to be savvy enough to manage this step.

  sdist            create a source distribution (tarball, zip file, etc.)
  register         register the distribution with the Python package index
  bdist            create a built (binary) distribution
  bdist_dumb       create a "dumb" built distribution
  bdist_rpm        create an RPM distribution
  bdist_wininst    create an executable installer for MS Windows

The bdist_wininst installs the source as well as compiling on Windows.
The others I don't know anything about. There's also py2exe.

> > Sounds good. The more generic stuff you can put into cclib the better.
> > You should also take a look at Viewmol.
> 
> Viewmol looks promising, esp since it's GPL. That should mean there  
> isn't a problem adapting part of that code and including it in  
> PyMOlyze, provided I leave any copyright statements intact, right?

Ah...I wouldn't be so sure about that. So check it out at Groklaw or
whereever. I think the author would have no problem sharing code with
us/you if you asked nicely - I think he's very involved in OSS, although
not so active with Viewmol anymore.

> > That would be good, but maybe there are ways to do this that aren't
> > KDE-specific. e.g. some sort of python ssh library
> 
> Interesting point, although there are other uses of KIO-slaves like  
> the zip and gz. I can imagine that being somewhat useful if people  
> compress their files after analyzing them, and decide to take another  
> look.
Aha, but don't forget to think about using a python gzip library...it's
somewhere in the standard library, I think.

> > I recommend running ccget on every output file you can find. If you're
> > brave you could try:
> > ccget `find . | grep .out` which would run ccget on every .out file in
> > your directory structure (recursively). You'll soon find out if there
> > are any problems.
> 
> So all my Gaussian files except one worked ok. The one that didn't  
> threw a logging error, so I think it's probably a broken file. I can  
> upload it if you want.
> 
> ADF, unfortunately, had a lot of problems. Several of the files  
> didn't have any attributes to print, which I find odd because I'd  
> expect *something*. A few just completely crapped out with  
> IndexErrors or TypeErrors. Is there a limit to the filesizes we  
> should be uploading? Or should I just put it on a website somewhere  
> for you to access?
Ok, we're going to have to sort this out somehow. I think you're right
that we cannot be putting everything up on SVN. Here are some ideas.

In the short term, we need to share log files easily between us, and
keep track of what log files there are for testing, and write unit tests
for them. If we're not going to use SVN we need to use email, I guess;
we could share a gmail a/c between us, with log files as attachments and
the body explains what the bug is, and which SVN revision the bug occurs
with. We could integrate this with the bug tracker on SF in the medium
term, once we get bug submissions externally; in that case, the body of
the gmail email would only need to be a reference to the bug number.

Every so often we can make a release of example log files, basically a
tar.gz of the Data directory.

I'll send you the gmail account address and password off list.

Regards,
 Noel

> Adam
> 
> 
> All the advantages of Linux Managed Hosting--Without the Cost and Risk!
> Fully trained technicians. The highest number of Red Hat certifications in
> the hosting industry. Fanatical Support. Click to learn more
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
> _______________________________________________
> cclib-devel mailing list
> ccl...@li...
> https://lists.sourceforge.net/lists/listinfo/cclib-devel