-
Notifications
You must be signed in to change notification settings - Fork 638
Add support for the mf4 io format #554
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.
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
Merged
Merged
Changes from all commits
Commits
Show all changes
43 commits
Select commit
Hold shift + click to select a range
bee6d4d
add extra dependency
danielhrisca 4c3d917
Merge branch 'develop' of https://github.com/hardbyte/python-can into…
danielhrisca 1fc9bf2
add mf4 io writer
danielhrisca 07c0a4c
Merge remote-tracking branch 'remotes/upstrem/develop' into mf4_io
danielhrisca ad33863
update asammdf requirement
danielhrisca b6f73af
add missing comma in setup.py
danielhrisca 70f1be4
Merge branch 'develop' of https://github.com/hardbyte/python-can into…
danielhrisca 26cd255
changes after initial review
danielhrisca 74e8472
simplify append call
danielhrisca 59c3db9
add MF4Reader class
danielhrisca efdfdc9
start testing
danielhrisca 38d67ac
passes tests
danielhrisca a11440b
update documentation
danielhrisca b736542
update docs and CI scripts
danielhrisca c2db9f6
retrigger build
danielhrisca 3953060
Merge branch 'develop' into mf4_io
felixdivo 72469fc
Merge branch 'develop' into mf4_io
felixdivo ddbb985
Merge branch 'develop' of https://github.com/hardbyte/python-can into…
danielhrisca 08cd68c
Merge branch 'develop' into mf4_io
felixdivo b1e7d5c
Merge branch 'develop' of https://github.com/hardbyte/python-can into…
danielhrisca 2a2e77e
update setup.py according to review
danielhrisca a2937bb
Merge branch 'mf4_io' of https://github.com/danielhrisca/python-can i…
danielhrisca be0d168
remove debug save file
danielhrisca 9f7e6b4
install and test mf4
danielhrisca 2d74d3c
Merge branch 'develop' into mf4_io
felixdivo 368c505
changes after review
danielhrisca afd20d7
Merge branch 'develop' into mf4_io
danielhrisca dff0f69
Merge branch 'develop' into mf4_io
felixdivo a8abbf0
updates after review
danielhrisca 74b6c6f
Merge branch 'develop' into mf4_io
hardbyte 8c60906
Merge branch 'develop' into mf4_io
felixdivo 3be4d52
Merge branch 'develop' into mf4_io
felixdivo 70614d9
Merge branch 'develop' into mf4_io
felixdivo 29b293a
Merge branch 'develop' into mf4_io
felixdivo b155217
Merge branch 'develop' into mf4_io
felixdivo 683f464
Merge branch 'develop' into mf4_io
felixdivo d70b2bf
Merge branch 'develop' of https://github.com/hardbyte/python-can into…
danielhrisca 11ca866
Merge branch 'develop' into mf4_io
danielhrisca bb4813c
Merge branch 'develop' of https://github.com/hardbyte/python-can into…
danielhrisca c9a4a57
add cython requirement
danielhrisca 3a3a7d9
Merge branch 'mf4_io' of https://github.com/danielhrisca/python-can i…
danielhrisca 7085a3d
Merge branch 'develop' into mf4_io
felixdivo 74a2759
Merge branch 'mf4-io' into mf4_io
felixdivo File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe this is not the right way to configure the tests. Maybe we should simply not support the combination of MF4 & PyPy (as mentioned above). This could be done by only installing
travis_retry pip install .[test]
and instead changingsetup.py
to:A very simple not in the docs should be added as well:
.. note:: *MF4* is currently only supported on CPython and not on PyPy.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://www.python.org/dev/peps/pep-0508/#environment-markers
'mf4; platform_python_implementation == "CPython"'
Maybe? Untested, but definitely want to get away from arbitrary code relating to setup. Also maybe
!= "PyPy"
depending on intent.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@altendky This does not seem to work on my machine: I get
python-can 3.2.0 does not provide the extra 'mf4'
on CPython 3.6. Removing the spaces did not help either.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@danielhrisca Sorry for the long delay. With the above change, this should be ready to finally be merged.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@felixdivo, I think maybe I misread the code there. Sorry. The point is to document dependencies in a way that can be retrieved regardless of what Python is being used to run setup.py. For example, what I wrote (or something like it) can go into a wheel intact and be processed when the wheel is installed.
if is_cpython:
would be processed when the wheel is built and then when the wheel is used it would be fixed according to the Python used to create the wheel. This is also quite relevant to locking dependencies.But... I was thinking at a different layer. I don't know that there's a tidy all around solution for this yet. Applying the environment markers to each dependency of the mf4 extra could make it a no-op at least and then it could be unconditionally (code-wise) included wherever. Maybe that's what I would do, I'm not quite sure.
It would be nice if the extra could be made conditionally available but my naive attempt didn't work.
https://gist.github.com/altendky/357e6a19691912593080f18ddcc39235
It would also be nice if setup.py could reference its own extras as dependencies like
.[mf4]
or such but last I played with that I didn't find anything that worked.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I got that idea, but it's largely unsupported for now. :( I was just trying what is implemented and what not. That shortcoming of
setup.py
is really annoying as well. -.-