New pypi release?

[jacobwilliams]

Do you plan on a new pypi release with the latest changes? It's easier to deal with when I can just install using pip (there's been enough bug fixes that I can't even use the pypi one any more with some of my code). Thanks!

[cmacmackin]

There definitely will be. I wanted to get a few more things fixed (#200, #205, #221) before a release, but have been busy with other things lately. I'll try to get that done soon.

…

On 04/03/18 19:30, Jacob Williams wrote: Do you plan on a new pypi release with the latest changes? It's easier to deal with when I can just install using pip (there's been enough bug fixes that I can't even use the pypi one any more with some of my code). Thanks! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <https://github.com/cmacmackin/ford/issues/225>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHxJPfuZrV2AAvyhrWvIbFBQbkQEmi4qks5tbEDjgaJpZM4Sbdnl>.

-- Chris MacMackin cmacmackin.github.io <http://cmacmackin.github.io>

[jacobwilliams]

No worries or rush. Many thanks for all your efforts!

[jacobwilliams]

FYI: you may be aware of this, but I just noticed that the current version of ford on pypi is totally broken (it looks like all my projects that build documentation on Travis-CI and push to github pages are failing). This is odd because it used to work (maybe some dependency changed something that broke it at some point?) I'm not sure when the change happened. The latest master version works fine for me.

[zbeekman]

@jacobwilliams was the Travis-CI issue ever resolved?

[zbeekman]

@cmacmackin FYI, I was about to open a new issue until I discovered that it was fixed on master. It would be really great to publish a PyPI release, even if not 100% of the bugs you wanted to resolve for the next release are finished.

Here is the text of the report I was about to file:

---

It seems that FORD may not like the module function declaration used in submodules. Replacing this with module procedure seems to fix things.

The error message generated is:

Processing documentation comments...
Correlating information from different parts of your project...
Traceback (most recent call last):
  File "/usr/local/bin/ford", line 11, in <module>
    load_entry_point('FORD==5.0.6', 'console_scripts', 'ford')()
  File "/usr/local/Cellar/ford/5.0.6/libexec/lib/python2.7/site-packages/ford/__init__.py", line 357, in run
    main(proj_data,proj_docs,md)
  File "/usr/local/Cellar/ford/5.0.6/libexec/lib/python2.7/site-packages/ford/__init__.py", line 320, in main
    project.correlate()
  File "/usr/local/Cellar/ford/5.0.6/libexec/lib/python2.7/site-packages/ford/fortran_project.py", line 232, in correlate
    for function in module.modfunctions:
AttributeError: 'FortranSubmodule' object has no attribute 'modfunctions'

[cmacmackin]

Fair enough. If you're willing to help, it would be really great if you could assemble some release notes along the lines of what I've done in the past. Longer term, I'm thinking that I'm going to need to pass FORD onto someone else. I'm busy with other things these days and it deserves someone who is able to devote more time to it.

[cmacmackin]

A new release is just out.

[zbeekman]

<3 Thanks Chris!

…

On Sat, Jun 30, 2018 at 8:46 AM Chris MacMackin ***@***.***> wrote: Closed #225 <https://github.com/cmacmackin/ford/issues/225>. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://github.com/cmacmackin/ford/issues/225#event-1709938925>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAREPO_kMx9E9Efz8giG77TPimhlzLl3ks5uB3MpgaJpZM4Sbdnl> .