You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a few things we've been cooking up in mixbox that may be incompatible with existing, documented code.
An example is the idgen module [1], which was moved to mixbox, but now accepts different arguments (was a dictionary, now a mixbox.namespaces.Namespace object).
We should try to write adapters where possible and limit the impact of moving to mixbox as much as we can.
I appreciate your work on this. At the moment, I am pretty confused by idgen appearing in maec.utils, mixbox and cybox.utils and not working as expected. I get errors on set_id_namespace: "Must be a Namespace object", and set_id_method(IDGenerator.METHOD_INT) results in UUID instead of integer IDs (except if I use the Master branch).
@abulhol, If you are interested in using python-stix/python-cybox/python-maec, we recommend heading on over to PyPI and downloading an official release (or using pip install maec) rather than trying to use the latest commits from the repository.
If you are running code off of a branch on GitHub (including master) you are working from in-development code (with a x.y.z.dev[number] version number) which may not work the way you want it to :)
There are a few things we've been cooking up in mixbox that may be incompatible with existing, documented code.
An example is the
idgen
module [1], which was moved to mixbox, but now accepts different arguments (was a dictionary, now a mixbox.namespaces.Namespace object).We should try to write adapters where possible and limit the impact of moving to mixbox as much as we can.
[1] http://stix.readthedocs.org/en/stable/overview/id_namespaces.html#id-namespaces
The text was updated successfully, but these errors were encountered: