Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8712125
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 13, 20262026-06-13T05:02:51+00:00 2026-06-13T05:02:51+00:00

I recently stumbled on this kickass python extension package, Brian Hears that will solve

  • 0

I recently stumbled on this kickass python extension package, Brian Hears that will solve all my coding issues. Problem is, some of the functions return memory addresses instead of expected results. For example:

>>> Parameterize(source, 256, 128)

Out[1]: <Parameterize.Parameterize at 0xda445f8>

I’ve never seen this before (and don’t know its proper name); however, the internet tells me that it’s a representation of the memory address of where my result is stored.

I’m really just interested in the result itself. How does one usually go about extracting the actual data from the address in python, or rather the numpy array that the function should (or at least i think it should) return?

Thanks in advance.

EDIT: Added name and link of package

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-13T05:02:52+00:00Added an answer on June 13, 2026 at 5:02 am

    It is returning an object. You should do

     p = Parameterize(source, 256, 128)
     res = p.usefull_attribute
    

    and then get your results from the object attributes/properties. You can use python’s self-documentation (dir(p), help(p) (as pointed out in other answers + comments)) to get python to tell you what attributes/methods your object has.

    What it is printing out is the default string representation of your object, this is it’s type and location.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

So I recently stumbled upon this great library for handling HTTP requests in Python;
I recently stumbled upon this in a project I'm working on. In package A
I recently stumbled upon this interesting concept that may save me much testing efforts.
I'm refactoring some code that a friend wrote and recently stumbled across this function:
Recently I stumbled across this pretty slick JS library called nodeJS that acts like
I've recently stumbled over this expression: True == False in (False,) It evaluates to
Recently stumbled upon a stock video footage site http://www.pond5.com/stock-video-footage/1/*.html , and saw that they
I recently stumbled across an article that claims Microsoft is banning the memcpy() function
we recently stumbled over a behaviour of NHibernate that gave us a real headache
I was recently looking to practice utilizing dictionaries in python and stumbled across these

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.