From: Norbert N. <Nor...@gm...> - 2006-08-18 14:05:20
Attachments:
threading-without-smp-setup-bugfix.diff
|
Hi there, in numpy-1.0b2 the logic in setup.py is slightly off. The attached patch fixes the issue. Greetings, Norbert PS: I would have preferred to submit this patch via the sourceforge bug-tracker, but that seems rather confusing: there are tabs "Numarray Patches" and "Numarray Bugs" but no "NumPy bugs" and the tab "Patches" seems to be used for Numeric. Why isn't NumPy handled via the Sourceforge page? |
From: Francesc A. <fa...@ca...> - 2006-08-18 14:34:53
|
A Divendres 18 Agost 2006 15:36, Norbert Nemec va escriure: > PS: I would have preferred to submit this patch via the sourceforge > bug-tracker, but that seems rather confusing: there are tabs "Numarray > Patches" and "Numarray Bugs" but no "NumPy bugs" and the tab "Patches" > seems to be used for Numeric. Why isn't NumPy handled via the > Sourceforge page? Because it has its own development site in: http://projects.scipy.org/scipy/numpy/ Log your bug reports there. Sourceforge is mainly used to distribute tarbal= ls=20 and binary packages of public releases, that's all. Cheers, =2D-=20 >0,0< Francesc Altet =C2=A0 =C2=A0 http://www.carabos.com/ V V C=C3=A1rabos Coop. V. =C2=A0=C2=A0Enjoy Data "-" |
From: Stefan v. d. W. <st...@su...> - 2006-08-18 14:45:15
|
Hi Norbert On Fri, Aug 18, 2006 at 03:36:47PM +0200, Norbert Nemec wrote: > in numpy-1.0b2 the logic in setup.py is slightly off. The attached patc= h > fixes the issue. Please file a ticket so that we don't lose track of this. St=E9fan |
From: Stefan v. d. W. <st...@su...> - 2006-08-19 00:01:13
|
On Fri, Aug 18, 2006 at 04:45:03PM +0200, Stefan van der Walt wrote: > Hi Norbert >=20 > On Fri, Aug 18, 2006 at 03:36:47PM +0200, Norbert Nemec wrote: > > in numpy-1.0b2 the logic in setup.py is slightly off. The attached pa= tch > > fixes the issue. >=20 > Please file a ticket so that we don't lose track of this. Urgh, please excuse me. It seems that I have lost the ability to read more than one paragraph. St=E9fan |
From: Travis O. <oli...@ie...> - 2006-08-18 18:34:58
|
Norbert Nemec wrote: > Hi there, > > in numpy-1.0b2 the logic in setup.py is slightly off. The attached patch > fixes the issue. > > Greetings, > Norbert > > PS: I would have preferred to submit this patch via the sourceforge > bug-tracker, but that seems rather confusing: there are tabs "Numarray > Patches" and "Numarray Bugs" but no "NumPy bugs" and the tab "Patches" > seems to be used for Numeric. Why isn't NumPy handled via the > Sourceforge page? > NumPy development happens on the SVN servers at scipy.org and bug-tracking is handled through the Trac system at http://projects.scipy.org/scipy/numpy We only use sourceforge for distribution. I need more description on why the logic is not right. -Travis |
From: Norbert N. <Nor...@gm...> - 2006-08-20 10:52:03
|
Travis Oliphant wrote: > Norbert Nemec wrote: > >> Hi there, >> >> in numpy-1.0b2 the logic in setup.py is slightly off. The attached patch >> fixes the issue. >> >> Greetings, >> Norbert >> >> PS: I would have preferred to submit this patch via the sourceforge >> bug-tracker, but that seems rather confusing: there are tabs "Numarray >> Patches" and "Numarray Bugs" but no "NumPy bugs" and the tab "Patches" >> seems to be used for Numeric. Why isn't NumPy handled via the >> Sourceforge page? >> >> > NumPy development happens on the SVN servers at scipy.org and > bug-tracking is handled through the Trac system at > > http://projects.scipy.org/scipy/numpy > > We only use sourceforge for distribution. > OK, sorry. I found this myself in the meantime. I even remember that I stumbled over this some time ago already. Problem is: I'm submitting bug-reports, fixes and small patches to so many different projects, that I start mixing up the details of the individual procedures. Furthermore: the TRAC tickets do not seem to allow attachment of patches. Did I miss something there? > I need more description on why the logic is not right. > The original code reads: ----------------------- [...snip...] if nosmp: moredefs = [('NPY_ALLOW_THREADS', '0')] else: moredefs = [] [...snip...] if moredefs: target_f = open(target,'a') for d in moredefs: if isinstance(d,str): target_f.write('#define %s\n' % (d)) else: target_f.write('#define %s %s\n' % (d[0],d[1])) if not nosmp: # default is to use WITH_THREAD target_f.write('#ifdef WITH_THREAD\n#define NPY_ALLOW_THREADS 1\n#else\n#define NPY_ALLOW_THREADS 0\n#endif\n') target_f.close() [...snip...] ---------------- That is: if not nosmp, then moredefs may be empty, in which case NPY_ALLOW_THREADS is not defined at all. My patch ensures that NPY_ALLOW_THREADS is defined in any case, either by putting it in moredefs, or by adding the special conditional define. The conditional "if moredefs" is not needed at all: the file needs to be opened in any case, to define NPY_ALLOW_THREADS one way or other. Greetings, Norbert |
From: Albert S. <fu...@gm...> - 2006-08-20 12:53:49
|
Hello all > <snip> > Furthermore: the TRAC tickets do not seem to allow attachment of > patches. Did I miss something there? After submitting the initial report, you can attach files to the ticket. Regards, Albert |