Thanks to visit codestin.com
Credit goes to github.com

Skip to content

BUG: f2py character array variables now broken #6308

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
2sn opened this issue Sep 12, 2015 · 1 comment · Fixed by #19388
Closed

BUG: f2py character array variables now broken #6308

2sn opened this issue Sep 12, 2015 · 1 comment · Fixed by #19388
Assignees
@pearu
Labels
00 - Bug component: numpy.f2py

Comments

@2sn
Copy link
Contributor

2sn commented Sep 12, 2015

in current devel version when a character variable is defined using the asterisk form

character*8  name

and I then use

common name(12)

I get an error message from f2py like

analyzevars: character array "character*8 name(12)" is considered as "character name(12,8)"; "intent(c)" is forced.

if the first definition is changed to

character(8)

then the error goes away.

The old behaviour that is consistent with FORTRAN should be restored.
Any suggestion on bug fix?
@2sn
Copy link
Contributor Author

2sn commented Sep 12, 2015

In [1]: np.version
Out[1]: '1.11.0.dev0+3397fce'

@jnsebgosselin jnsebgosselin mentioned this issue Oct 31, 2018
Merged
4 tasks
@mattip mattip mentioned this issue Dec 3, 2019
Closed
pearu added a commit to pearu/numpy that referenced this issue Jul 2, 2021
@pearu
TST: added test for issue numpy#6308
be282c5
@pearu pearu mentioned this issue Jul 2, 2021
Merged
@pearu pearu self-assigned this Jul 3, 2021
@pearu pearu linked a pull request Jul 3, 2021 that will close this issue
ENH: Support character and character string arrays #19388
Merged
pearu added a commit to pearu/numpy that referenced this issue Sep 1, 2021
@pearu
TST: added test for issue numpy#6308
ad5de48
pearu added a commit to pearu/numpy that referenced this issue Sep 6, 2021
@pearu
ENH: Support character string arrays
bc41ca9 
TST: added test for issue numpy#18684

ENH: f2py opens files with correct encoding, fixes numpy#635

TST: added test for issue numpy#6308

TST: added test for issue numpy#4519

TST: added test for issue numpy#3425

ENH: Implement user-defined hooks support for post-processing f2py data structure. Implement character BC hook.

ENH: Add support for detecting utf-16 and utf-32 encodings.
melissawm pushed a commit to pearu/numpy that referenced this issue Apr 4, 2022
@pearu @melissawm
ENH: Support character string arrays
d41bfa0 
TST: added test for issue numpy#18684

ENH: f2py opens files with correct encoding, fixes numpy#635

TST: added test for issue numpy#6308

TST: added test for issue numpy#4519

TST: added test for issue numpy#3425

ENH: Implement user-defined hooks support for post-processing f2py data structure. Implement character BC hook.

ENH: Add support for detecting utf-16 and utf-32 encodings.
HaoZeke pushed a commit to pearu/numpy that referenced this issue Jun 5, 2022
@pearu @HaoZeke
ENH: Support character string arrays
d4e11c7 
TST: added test for issue numpy#18684

ENH: f2py opens files with correct encoding, fixes numpy#635

TST: added test for issue numpy#6308

TST: added test for issue numpy#4519

TST: added test for issue numpy#3425

ENH: Implement user-defined hooks support for post-processing f2py data structure. Implement character BC hook.

ENH: Add support for detecting utf-16 and utf-32 encodings.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pearu pearu

Labels
00 - Bug component: numpy.f2py
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

ENH: Support character and character string arrays pearu/numpy
3 participants
@pearu @mattip @2sn