Re: [MeshPy] packaging meshpy
by Andreas Kloeckner
On Fri, 24 Dec 2010 16:23:33 +0100, Nico Schlömer <nico.schloemer(a)gmail.com> wrote:
> This is on recent Ubuntu
>
> ===================== *snip* =====================
> Python 2.6.6 (r266:84292, Sep 15 2010, 16:22:56)
> [GCC 4.4.5] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import setuptools
> >>> setuptools.__file__
> '/usr/lib/python2.6/dist-packages/setuptools/__init__.pyc'
> ===================== *snap* =====================
>
> and on recent Gentoo
>
> ===================== *snip* =====================
> Python 2.6.5 (release26-maint, Sep 2 2010, 09:11:59)
> [GCC 4.4.3] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import setuptools
> >>> setuptools.__file__
> '/usr/lib64/python2.6/site-packages/setuptools/__init__.pyc'
> ===================== *snap* =====================
>
> The file location could be *anything. Isn't there a hook that tells
> you which one you are using?
> I could imagine, for example, that running your things through
> setuptools will result in an exception somewhere. Should that be the
> case, then why not catch that, and exit gracefully with an appropriate
> error message.
Turns out I lied. Recent git already has a better check:
if not hasattr(setuptools, "_distribute"):
Would you like me to roll a new release of MeshPy to make your packaging
easier?
Andreas
9 years
Re: [MeshPy] packaging meshpy
by Andreas Kloeckner
On Tue, 14 Dec 2010 03:28:14 +0100, Nico Schlömer <nico.schloemer(a)gmail.com> wrote:
> > I agree with you, and this would be possible for Triangle. For TetGen, I
> > actually ship a patched version (and upstream doesn't like my patch), so
> > this would be more difficult. To compound the difficulty for Triangle:
> > the upstream package doesn't build a library by default. Given this
> > situation, shipping the libraries is IMO likely the easiest way.
>
> Right. Well, I know at least two other packages now that use TetGen,
> and guess what: They all bundle it. :/ Well, I guess I shouldn't care
> too much about it at the moment.
> Triangle's "build system" is indeed a bit broken and would require
> fixing, but that's for another time.
>
> >> if 'distribute' not in setuptools.__file__:
> >>
> >> supposed to find? I could crosscheck that against what is installed by
> >> default with Gentoo.
> >
> > http://wiki.tiker.net/DistributeVsSetuptools
>
> Yes. Well. I guess at least Debian and Gentoo actually provide
> "distribute" now when you install "setuptools", see the comment
>
> Update 8/11/2010: When you install setuptools in Debian unstable
> nowadays, you actually get distribute.
>
> so checking for that file name is probably no good way to detect
> inconsistencies anymore.
To follow up on this: I think this is a good enough way. See here:
Python 2.6.5+ (release26-maint, Jul 6 2010, 14:48:45)
[GCC 4.4.4] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import setuptools
>>> setuptools.__file__
'/home/andreas/pool/lib/python2.6/site-packages/distribute-0.6.10-py2.6.egg/setuptools/__init__.pyc'
This is on recent Debian.
Andreas
9 years
setting boundary conditions
by Islam El Salawi
Hi there,
I just succeeded in reading in a cgns mesh from icem in hedge, by converting its points and elements to the according format. Now I need to know how to assign boundary conditions. The geometry is a 3d dummy test cube, which siedelengths are 4 units. I want one face to be the inflow area, the adverse face should be assigned as outflow. The other four faces are walls, characterized as no slip boundaries.
Thanks
Islam
--
GRATIS! Movie-FLAT mit über 300 Videos.
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome
9 years, 1 month
Re: [MeshPy] packaging meshpy
by Andreas Kloeckner
Hi Nico,
On Fri, 10 Dec 2010 20:45:22 +0100, Nico Schlömer <nico.schloemer(a)gmail.com> wrote:
> First off, I see that TetGen and Triangle are bundled in the build.
> While that's handy for the one-shot user, package maintainers are
> usually somewhat skeptical about that. The reason for this is mainly
> that the bundled libraries are libraries in their own right, and may
> as well be installed on the system independently. Making use of system
> libraries avoids having libraries installed several times on one
> system, avoid the license mix-up, avoid falling behind on releases of
> bundled libraries.
I agree with you, and this would be possible for Triangle. For TetGen, I
actually ship a patched version (and upstream doesn't like my patch), so
this would be more difficult. To compound the difficulty for Triangle:
the upstream package doesn't build a library by default. Given this
situation, shipping the libraries is IMO likely the easiest way.
> Also, I noticed that I'm greeted with a warning message and a ten
> seconds delay every time aksetup_helper.py is called. Apparently this
> is to notify the user that he or she is running on an outdated
> setuptools. This is not the case here (I believe). What is the check
>
> if 'distribute' not in setuptools.__file__:
>
> supposed to find? I could crosscheck that against what is installed by
> default with Gentoo.
http://wiki.tiker.net/DistributeVsSetuptools
HTH,
Andreas
9 years, 1 month
