Re: [Numpy-discussion] Help needed GDB

[Amardeep Singh]

Hi All,

I was able to fix it but one thing i am not getting.
it is building with python 2.

I need python 3  enabled gdb.

./configure --with-python.  --> how to make it to use python 3 installed on
my machine?

thx




On Tue, Dec 29, 2020 at 1:55 PM Amardeep Singh  wrote:

> Hi All,
>
> I am trying to debug c code of numpy via gdb.Can someone help me with this?
> i am getting " Python scripting is not supported in this copy of GDB". How
> to install python supported gdb on win10?
>
>
> https://numpy.org/doc/stable/dev/development_environment.html
>
> I am following the steps in the docs. machine is windows 10.
>
> Debugging
> 
>
> Another frequently asked question is “How do I debug C code inside
> NumPy?”. First, ensure that you have gdb installed on your system with the
> Python extensions (often the default on Linux). You can see which version
> of Python is running inside gdb to verify your setup:
>
> (gdb) python>import sys>print(sys.version_info)>endsys.version_info(major=3, 
> minor=7, micro=0, releaselevel='final', serial=0)
>
>
>
>
> $ gdb -v
> GNU gdb (GDB) 7.6.1
> This GDB was configured as "mingw32".
>
> $ gdb
> (gdb) python
> >import sys
> >print(sys.version_info)
> >end
> (gdb) Python scripting is not supported in this copy of GDB.
>
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Help needed GDB

[Amardeep Singh]

Hi All

when i. try to use python3 installed on my macbook i get this.

checking for libmpfr... no

configure: WARNING: MPFR is missing or unusable; some features may be
unavailable.

checking whether to use python... /usr/local/bin/python3

checking for python... no

configure: error: no usable python found at /usr/local/bin/python3



These are the commands i ran


1) /Users/amardeepsingh/Downloads/gdb-9.2/configure
--with-python=/usr/local/bin/python3


2) make




my mac


 % which python3


/Library/Frameworks/Python.framework/Versions/3.9/bin/python3

% ls -lrt /usr/local/bin/python3

lrwxr-xr-x  1 root  wheel  69 Dec 29 14:37 /usr/local/bin/python3 ->
../../../Library/Frameworks/Python.framework/Versions/3.9/bin/python3








On Tue, Dec 29, 2020 at 4:04 PM Amardeep Singh  wrote:

> Hi All,
>
> I was able to fix it but one thing i am not getting.
> it is building with python 2.
>
> I need python 3  enabled gdb.
>
> ./configure --with-python.  --> how to make it to use python 3 installed
> on my machine?
>
> thx
>
>
>
>
> On Tue, Dec 29, 2020 at 1:55 PM Amardeep Singh 
> wrote:
>
>> Hi All,
>>
>> I am trying to debug c code of numpy via gdb.Can someone help me with
>> this?
>> i am getting " Python scripting is not supported in this copy of GDB".
>> How to install python supported gdb on win10?
>>
>>
>> https://numpy.org/doc/stable/dev/development_environment.html
>>
>> I am following the steps in the docs. machine is windows 10.
>>
>> Debugging
>> 
>>
>> Another frequently asked question is “How do I debug C code inside
>> NumPy?”. First, ensure that you have gdb installed on your system with the
>> Python extensions (often the default on Linux). You can see which version
>> of Python is running inside gdb to verify your setup:
>>
>> (gdb) python>import sys>print(sys.version_info)>endsys.version_info(major=3, 
>> minor=7, micro=0, releaselevel='final', serial=0)
>>
>>
>>
>>
>> $ gdb -v
>> GNU gdb (GDB) 7.6.1
>> This GDB was configured as "mingw32".
>>
>> $ gdb
>> (gdb) python
>> >import sys
>> >print(sys.version_info)
>> >end
>> (gdb) Python scripting is not supported in this copy of GDB.
>>
>
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] proposal for NumPy sponsorship guidelines (NEP 46)

[Ralf Gommers]

Hi all,

I just opened https://github.com/numpy/numpy/pull/18084, "NumPy Sponsorship
Guidelines". Below are the most important parts for review (for Related
Work, References, etc. see the PR). Please bring up broader points here,
and small/textual feedback on the PR.

Cheers,
Ralf



Abstract


This NEP provides guidelines on how the NumPy project will acknowledge
financial and in-kind support.


Motivation and Scope


In the past few years the NumPy project has gotten significant financial
support, as well as dedicated work time for maintainers to work on NumPy.
There
is a need to acknowledge that support - funders and organizations expect or
require
it, it's helpful when looking for new funding, and it's the right thing to
do.
Furthermore, having a clear policy for how NumPy acknowledges support is
helpful when searching for new support.

This NEP is aimed at both the NumPy community - who can use it when looking
for
support and acknowledging existing support - and at past, current and
prospective sponsors, who often want or need to know what they get in return
for their support (other than a healthier NumPy).

The scope of this proposal includes:

- direct financial support, employers providing paid time for NumPy
maintainers
  and regular contributors, and in-kind support such as free hardware
resources or
  services.
- where and how NumPy acknowledges support (e.g., logo placement on the
website).
- the amount and duration of support which leads to acknowledgement.
- who in the NumPy project is responsible for sponsorship related topics,
and
  how to contact them.


How NumPy will acknowledge support
--

There will be two different ways to acknowledge financial and in-kind
support,
one to recognize significant active support, and another one to recognize
support received in the past and smaller amounts of support.

Entities who fall under "significant active supporter" we'll call Sponsor.
The minimum level of support given to NumPy to be considered a Sponsor are:

- $30,000/yr for unrestricted financial contributions
- $60,000/yr for financial contributions for a particular purpose
- $100,000/yr for in-kind contributions

The rationale for the above levels is that unrestricted financial
contributions
are typically the most valuable for the project, and the hardest to obtain.
The opposite is true for in-kind contributions. The dollar value of the
levels
also reflect that NumPy's needs have grown to the point where we need at
least
a few paid developers in order to effectively support our user base and
continue to move the project forward. Financial support at or above these
levels is needed to be able to make a significant difference.

Sponsors will get acknowledged through:

- a small logo displayed on the front page of the NumPy website
- prominent logo placement on https://numpy.org/about/
- logos displayed in talks about NumPy by maintainers
- announcements of the sponsorship on the NumPy mailing list and the
numpy-team
  Twitter account

In addition to Sponsors, we already have the concept of Institutional
Partner
(defined in NumPy's
`governance document `__),
for entities who employ a NumPy maintainer and let them work on NumPy as
part
of their official duties. The governance document doesn't currently define a
minimum amount of paid maintainer time needed to be considered for
partnership.
Therefore we propose that level here, roughly in line with the sponsorship
levels:

- 6 person-months/yr of paid work time for one or more NumPy maintainers or
  regular contributors

Institutional Partners get the same benefits as Sponsors, in addition to
what
is specified in the NumPy governance document.

Finally, a new page on the website (https://numpy.org/funding/, linked from
the
About page) will be added to acknowledge all current and previous sponsors,
partners, and any other entities and individuals who provided $5,000 or
more of
financial or in-kind support. This page will include relevant details of
support (dates, amounts, names and purpose); no logos will be used on this
page. The rationale for the $5,000 minimum level is to keep the amount of
work
maintaining the page reasonable; the level is the equivalent of, e.g., one
GSoC
or a person-week's worth of engineering time in a Western country, which
seems
like a reasonable lower limit.


Implementation
--

The following content changes need to be made:

- Add a section with small logos towards the bottom of the `numpy.org
  `__ website.
- Create a full list of historical and current support and deploy it to
  https://numpy.org/funding.
- Update the NumPy governance document for changes to Institutional Partner
  eligibility requirements and benefits.
- Update https://numpy.org/about with details on how to get in touch with
the
  NumPy project about sponsorship related matters (see next section).


A NumPy

Re: [Numpy-discussion] Help needed GDB

[Amardeep Singh]

Hi All

I was able to fix.

>import sys

>print(sys.version_info)

>end

sys.version_info(major=3, minor=9, micro=1, releaselevel='final', serial=0)

(gdb) quit




https://github.com/crosstool-ng/crosstool-ng/issues/1308


 this was the issue.


The solution is to open /gdb/python/python-config.py and comment out these
two lines:

 if getvar('LINKFORSHARED') is not None:
  libs.extend(getvar('LINKFORSHARED').split())










On Tue, Dec 29, 2020 at 4:27 PM Amardeep Singh  wrote:

> Hi All
>
> when i. try to use python3 installed on my macbook i get this.
>
> checking for libmpfr... no
>
> configure: WARNING: MPFR is missing or unusable; some features may be
> unavailable.
>
> checking whether to use python... /usr/local/bin/python3
>
> checking for python... no
>
> configure: error: no usable python found at /usr/local/bin/python3
>
>
>
> These are the commands i ran
>
>
> 1) /Users/amardeepsingh/Downloads/gdb-9.2/configure
> --with-python=/usr/local/bin/python3
>
>
> 2) make
>
>
>
>
> my mac
>
>
>  % which python3
>
>
> /Library/Frameworks/Python.framework/Versions/3.9/bin/python3
>
> % ls -lrt /usr/local/bin/python3
>
> lrwxr-xr-x  1 root  wheel  69 Dec 29 14:37 /usr/local/bin/python3 ->
> ../../../Library/Frameworks/Python.framework/Versions/3.9/bin/python3
>
>
>
>
>
>
>
>
> On Tue, Dec 29, 2020 at 4:04 PM Amardeep Singh 
> wrote:
>
>> Hi All,
>>
>> I was able to fix it but one thing i am not getting.
>> it is building with python 2.
>>
>> I need python 3  enabled gdb.
>>
>> ./configure --with-python.  --> how to make it to use python 3 installed
>> on my machine?
>>
>> thx
>>
>>
>>
>>
>> On Tue, Dec 29, 2020 at 1:55 PM Amardeep Singh 
>> wrote:
>>
>>> Hi All,
>>>
>>> I am trying to debug c code of numpy via gdb.Can someone help me with
>>> this?
>>> i am getting " Python scripting is not supported in this copy of GDB".
>>> How to install python supported gdb on win10?
>>>
>>>
>>> https://numpy.org/doc/stable/dev/development_environment.html
>>>
>>> I am following the steps in the docs. machine is windows 10.
>>>
>>> Debugging
>>> 
>>>
>>> Another frequently asked question is “How do I debug C code inside
>>> NumPy?”. First, ensure that you have gdb installed on your system with the
>>> Python extensions (often the default on Linux). You can see which version
>>> of Python is running inside gdb to verify your setup:
>>>
>>> (gdb) python>import 
>>> sys>print(sys.version_info)>endsys.version_info(major=3, minor=7, micro=0, 
>>> releaselevel='final', serial=0)
>>>
>>>
>>>
>>>
>>> $ gdb -v
>>> GNU gdb (GDB) 7.6.1
>>> This GDB was configured as "mingw32".
>>>
>>> $ gdb
>>> (gdb) python
>>> >import sys
>>> >print(sys.version_info)
>>> >end
>>> (gdb) Python scripting is not supported in this copy of GDB.
>>>
>>
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Help needed GDB

[Amardeep Singh]

Hi Apologies

Once last issue is pending.Any pointers are helpful.

I am following the below docs.



Next you need to write a Python script that invokes the C code whose
execution you want to debug. For instance mytest.py:

import numpy as npx = np.arange(5)np.empty_like(x)

Now, you can run:

$ gdb --args python runtests.py -g --python mytest.py

And then in the debugger:

(gdb) break array_empty_like(gdb) run.  --> once i type run and enter
nothing happens it just gets struck up there.


Make breakpoint pending on future shared library load? (y or [n]) y

Breakpoint 1 (array_empty_like) pending.

(gdb) run

Starting program: /usr/bin/python mytest.py

[New Thread 0x1e03 of process 16513]

[New Thread 0x2303 of process 16513]




thx



On Tue, Dec 29, 2020 at 9:38 PM Amardeep Singh  wrote:

> Hi All
>
> I was able to fix.
>
> >import sys
>
> >print(sys.version_info)
>
> >end
>
> sys.version_info(major=3, minor=9, micro=1, releaselevel='final', serial=0)
>
> (gdb) quit
>
>
>
>
> https://github.com/crosstool-ng/crosstool-ng/issues/1308
>
>
>  this was the issue.
>
>
> The solution is to open /gdb/python/python-config.py and comment out these
> two lines:
>
>  if getvar('LINKFORSHARED') is not None:
>   libs.extend(getvar('LINKFORSHARED').split())
>
>
>
>
>
>
>
>
>
>
> On Tue, Dec 29, 2020 at 4:27 PM Amardeep Singh 
> wrote:
>
>> Hi All
>>
>> when i. try to use python3 installed on my macbook i get this.
>>
>> checking for libmpfr... no
>>
>> configure: WARNING: MPFR is missing or unusable; some features may be
>> unavailable.
>>
>> checking whether to use python... /usr/local/bin/python3
>>
>> checking for python... no
>>
>> configure: error: no usable python found at /usr/local/bin/python3
>>
>>
>>
>> These are the commands i ran
>>
>>
>> 1) /Users/amardeepsingh/Downloads/gdb-9.2/configure
>> --with-python=/usr/local/bin/python3
>>
>>
>> 2) make
>>
>>
>>
>>
>> my mac
>>
>>
>>  % which python3
>>
>>
>> /Library/Frameworks/Python.framework/Versions/3.9/bin/python3
>>
>> % ls -lrt /usr/local/bin/python3
>>
>> lrwxr-xr-x  1 root  wheel  69 Dec 29 14:37 /usr/local/bin/python3 ->
>> ../../../Library/Frameworks/Python.framework/Versions/3.9/bin/python3
>>
>>
>>
>>
>>
>>
>>
>>
>> On Tue, Dec 29, 2020 at 4:04 PM Amardeep Singh 
>> wrote:
>>
>>> Hi All,
>>>
>>> I was able to fix it but one thing i am not getting.
>>> it is building with python 2.
>>>
>>> I need python 3  enabled gdb.
>>>
>>> ./configure --with-python.  --> how to make it to use python 3 installed
>>> on my machine?
>>>
>>> thx
>>>
>>>
>>>
>>>
>>> On Tue, Dec 29, 2020 at 1:55 PM Amardeep Singh 
>>> wrote:
>>>
 Hi All,

 I am trying to debug c code of numpy via gdb.Can someone help me with
 this?
 i am getting " Python scripting is not supported in this copy of GDB".
 How to install python supported gdb on win10?


 https://numpy.org/doc/stable/dev/development_environment.html

 I am following the steps in the docs. machine is windows 10.

 Debugging
 

 Another frequently asked question is “How do I debug C code inside
 NumPy?”. First, ensure that you have gdb installed on your system with the
 Python extensions (often the default on Linux). You can see which version
 of Python is running inside gdb to verify your setup:

 (gdb) python>import 
 sys>print(sys.version_info)>endsys.version_info(major=3, minor=7, micro=0, 
 releaselevel='final', serial=0)




 $ gdb -v
 GNU gdb (GDB) 7.6.1
 This GDB was configured as "mingw32".

 $ gdb
 (gdb) python
 >import sys
 >print(sys.version_info)
 >end
 (gdb) Python scripting is not supported in this copy of GDB.

>>>
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] NumPy-Discussion Digest, Vol 171, Issue 39

[Brian Soto]

https://arxiv.org/pdf/1405.0506.pdf
> >
> >
> >
> > Disclaimer - University of Cape Town This email is subject to UCT
> policies
> > and email disclaimer published on our website at
> > http://www.uct.ac.za/main/email-disclaimer or obtainable from +27 21 650
> > 9111. If this email is not related to the business of UCT, it is sent by
> > the sender in an individual capacity. Please report security incidents or
> > abuse via https://csirt.uct.ac.za/page/report-an-incident.php.
> > ___
> > NumPy-Discussion mailing list
> > NumPy-Discussion@python.org
> > https://mail.python.org/mailman/listinfo/numpy-discussion
> >
>
>
> --
> Robert Kern
> -- next part --
> An HTML attachment was scrubbed...
> URL: <
> https://mail.python.org/pipermail/numpy-discussion/attachments/20201228/f4bbd564/attachment-0001.html
> >
>
> --
>
> Message: 2
> Date: Tue, 29 Dec 2020 13:55:03 +0800
> From: Amardeep Singh 
> To: numpy-discussion@python.org
> Subject: [Numpy-discussion] Help needed GDB
> Message-ID:
> <
> cajmcdx6dgoh_fkdhkxqb1_gpldyw3+0pmg_ne_t5bbhezmm...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi All,
>
> I am trying to debug c code of numpy via gdb.Can someone help me with this?
> i am getting " Python scripting is not supported in this copy of GDB". How
> to install python supported gdb on win10?
>
>
> https://numpy.org/doc/stable/dev/development_environment.html
>
> I am following the steps in the docs. machine is windows 10.
>
> Debugging
> <https://numpy.org/doc/stable/dev/development_environment.html#debugging>
>
> Another frequently asked question is ?How do I debug C code inside NumPy??.
> First, ensure that you have gdb installed on your system with the Python
> extensions (often the default on Linux). You can see which version of
> Python is running inside gdb to verify your setup:
>
> (gdb) python>import
> sys>print(sys.version_info)>endsys.version_info(major=3, minor=7,
> micro=0, releaselevel='final', serial=0)
>
>
>
>
> $ gdb -v
> GNU gdb (GDB) 7.6.1
> This GDB was configured as "mingw32".
>
> $ gdb
> (gdb) python
> >import sys
> >print(sys.version_info)
> >end
> (gdb) Python scripting is not supported in this copy of GDB.
> -- next part --
> An HTML attachment was scrubbed...
> URL: <
> https://mail.python.org/pipermail/numpy-discussion/attachments/20201229/268f82ab/attachment-0001.html
> >
>
> --
>
> Message: 3
> Date: Mon, 28 Dec 2020 22:38:07 -0800
> From: Robert McLeod 
> To: python-announce-l...@python.org,  Discussion of Numerical Python
> , pyd...@googlegroups.com
> Subject: [Numpy-discussion] ANN: NumExpr 2.7.2
> Message-ID:
> <
> caefuwwv0t8acczbs7n56zxtpzebgmfvqq7whjhgxvfttgo6...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> 
> Announcing NumExpr 2.7.2
> 
>
> Hi everyone,
>
> It's been awhile since the last update to NumExpr, mostly as the existing
> scientific
> Python tool chain for building wheels on PyPi became defunct and we have
> had to
> redevelop a new one based on `cibuildwheel` and GitHub Actions. This
> release also
> brings us support (and wheels for) Python 3.9.
>
> There have been a number of changes to enhance how NumExpr works when NumPy
> uses MKL as a backend.
>
> Project documentation is available at:
>
> http://numexpr.readthedocs.io/
>
> Changes from 2.7.1 to 2.7.2
> ---
>
> - Support for Python 2.7 and 3.5 is deprecated and will be discontinued
> when
>   `cibuildwheels` and/or GitHub Actions no longer support these versions.
> - Wheels are now provided for Python 3.7, 3.5, 3.6, 3.7, 3.8, and 3.9 via
>   GitHub Actions.
> - The block size is now exported into the namespace as
> `numexpr.__BLOCK_SIZE1__`
>   as a read-only value.
> - If using MKL, the number of threads for VML is no longer forced to 1 on
> loading
>   the module. Testing has shown that VML never runs in multi-threaded mode
> for
>   the default BLOCKSIZE1 of 1024 elements, and forcing to 1 can have
> deleterious
>   effects on NumPy functions when built with MKL. See issue #355 for
> details.
> - Use of `ndarray.tostring()` in tests has been switch to
> `ndarray.tobytes()`
>   for future-proofing deprecation of `.tostring()`, if the version of NumPy
> is
>   greater than 1.9.
> - Added a utility method `get_num_threads

Re: [Numpy-discussion] NumPy-Discussion Digest, Vol 171, Issue 39

[Robert Kern]

On Tue, Dec 29, 2020 at 5:35 PM Brian Soto  wrote:

> I'm still learning proper mailing list etiquette so I'm not sure if this
> is where I should respond.
>

FWIW, if you want to reply to conversations regularly, it's more ergonomic
all around to subscribe regularly and not use the digests. But if you only
occasionally want to jump in, using the digest is fine. It helps everyone
if you change the subject line back to that of the thread that you are
replying to and trimming the digest to just the email you are responding to.

Thank you! I hope this is helpful.

-- 
Robert Kern
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion