StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19022529
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-26T07:59:54.080
FavoriteCount
0
LastActivityDate
2013-09-26T07:59:54.080
LastEditDate
LastEditorUserId
0
OwnerUserId
676102
ParentId
17156125
PostTypeId
2
Score
6
ViewCount
0
LastEditorDisplayName
text
Body
I have found a temporary solution to this problem, but it is not optimal. I will continue to work through the f2py source so that I can better understand it and fix the problem within the code itself. Until then, this is my solution which was inspired by <a href="https://github.com/numpy/numpy/issues/3562#issuecomment-24469055">chatcannon's comment to the issue I posted to nympy's github</a>. There are several ways to approach this problem from a temporary standpoint including a couple of ways of modifying the .pyf files. I don't want to have to modify the .pyf files as it becomes very cumbersome as part of a larger package. To avoid this, I added f2py directives to my f90 source. Taking the example from my original question: <pre><code>MODULE test INTEGER, PARAMETER :: a = 1 END MODULE test MODULE test2 USE test INTEGER, PARAMETER :: b = 2 END MODULE test2 </code></pre> simply add an f2py directive in test2 to show f2py how to define <code>test2.a</code>: <pre><code>MODULE test INTEGER, PARAMETER :: a = 1 END MODULE test MODULE test2 USE test !f2py integer, parameter :: a ! THIS EXPOSES `a` in `test2` INTEGER, PARAMETER :: b = 2 END MODULE test2 </code></pre> Importing from the resulting <code>test.so</code> correctly exposes <code>test2.a</code>: <pre><code>In [1]: import test In [2]: print test.test.a 1 In [3]: print test.test.b --------------------------------------------------------------------------- AttributeError Traceback (most recent call last) .../test_solution/<ipython-input-3-798b14f59815> in <module>() ----> 1 print test.test.b AttributeError: b In [4]: print test.test2.a 1 In [5]: print test.test2.b 2 </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POf2py: Exposing parameters from "used" modules
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USVorticity
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POf2py: Exposing parameters from "used" modules
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.