Configuration
This page covers Python Fory instance configuration. pyfory.Fory() defaults to xlang mode with
compatible schema evolution. Native mode is selected explicitly with xlang=False and also defaults
to compatible schema evolution.
Fory Class
The main serialization interface:
class Fory:
def __init__(
self,
xlang: bool = True,
ref: bool = False,
strict: bool = True,
compatible: Optional[bool] = None,
max_depth: int = 50,
max_type_fields: int = 512,
max_type_meta_bytes: int = 4096,
max_schema_versions_per_type: int = 10,
max_average_schema_versions_per_type: int = 3,
policy: DeserializationPolicy = None,
field_nullable: bool = False,
meta_compressor=None,
)
ThreadSafeFory Class
Thread-safe serialization interface using a pooled wrapper:
class ThreadSafeFory:
def __init__(
self, fory_factory=None, **kwargs
)
Parameters
Key Methods
# Serialization (serialize/deserialize are identical to dumps/loads)
data: bytes = fory.serialize(obj)
obj = fory.deserialize(data)
# Alternative API (aliases)
data: bytes = fory.dumps(obj)
obj = fory.loads(data)
# Type registration by id
fory.register(MyClass, type_id=123)
fory.register(MyClass, type_id=123, serializer=custom_serializer)
# Type registration by name
fory.register(MyClass, name="my.package.MyClass")
fory.register(MyClass, name="my.package.MyClass", serializer=custom_serializer)
Xlang And Native Mode Comparison
| Feature | Native mode (xlang=False) | Xlang mode (default) |
|---|---|---|
| Use case | Python-only applications | Multi-language systems |
| Compatibility | Python only | Java, C++, Go, Rust, JavaScript/TypeScript, C#, Swift, Dart, Scala, Kotlin, etc. |
| Supported types | Python object surface | Cross-language compatible types |
| Functions/lambdas | Supported with trusted dynamic deserialization | Not allowed |
| Local classes | Supported with trusted dynamic deserialization | Not allowed |
| Dynamic classes | Supported with trusted dynamic deserialization | Not allowed |
| Schema mode default | Compatible | Compatible |
Xlang Mode
Xlang mode is the default and restricts payloads to types compatible across Fory implementations:
import pyfory
fory = pyfory.Fory(xlang=True, ref=True)
fory.register(MyDataClass, name="com.example.MyDataClass")
data = fory.serialize(MyDataClass(field1="value", field2=42))
Use compatible=False for xlang payloads only when every reader and writer always uses the same schema and you want faster serialization and smaller size. Use it only after verifying that every language uses that schema, or when native types are generated from Fory schema IDL.
Native Mode
import pyfory
fory = pyfory.Fory(xlang=False, ref=True, strict=False)
Native mode supports Python-specific object features such as functions, local classes, methods,
__reduce__, and __getstate__. Compatible mode is still enabled by default. Set
compatible=False only when every reader and writer always uses the same Python
class schema and you want faster serialization and smaller size.
Compatible Mode
Compatible mode is enabled by default for both xlang and native mode. Keep this default when Python classes may evolve independently, when services deploy separately, or when xlang schemas are written by hand in different languages.
For xlang payloads, set compatible=False only after verifying that every language uses the same schema, or when native types are generated from Fory schema IDL.
Example Configurations
Xlang Service
import pyfory
fory = pyfory.Fory(
xlang=True,
ref=False,
strict=True,
max_depth=20,
)
fory.register(UserModel, name="example.User")
Native Mode With Dynamic Types
import pyfory
fory = pyfory.Fory(
xlang=False,
ref=True,
strict=False,
max_depth=1000,
)
Use strict=False only for trusted data, preferably with a policy= deserialization policy.
Security
Treat native-mode bytes from untrusted sources the same way you would treat untrusted pickle bytes.
Native mode can reconstruct Python objects, import modules, invoke reduction hooks, and rebuild
dynamic classes or functions when strict=False.
Production Configuration
Keep strict=True for production payloads unless the whole data source is trusted and a
DeserializationPolicy owns the remaining trust decisions:
import pyfory
fory = pyfory.Fory(
xlang=True,
ref=False,
strict=True,
max_depth=50,
max_type_fields=512,
max_type_meta_bytes=4096,
max_schema_versions_per_type=10,
max_average_schema_versions_per_type=3,
)
fory.register(UserModel, name="example.User")
fory.register(OrderModel, name="example.Order")
Use dynamic native-mode deserialization (strict=False) only for trusted Python-only payloads:
import pyfory
fory = pyfory.Fory(
xlang=False,
ref=True,
strict=False,
max_depth=100,
)
Received remote metadata is also limited:
max_type_fieldslimits the number of fields accepted in one received struct metadata body.max_type_meta_byteslimits the encoded body bytes accepted for one received TypeDef body.max_schema_versions_per_typelimits accepted remote metadata versions for one logical type.max_average_schema_versions_per_typelimits the average across accepted remote types.
These limits do not change strict, policy, dynamic loading, unknown-class handling, or
schema-evolution semantics.
DeserializationPolicy
When strict=False is necessary, use DeserializationPolicy to restrict the dynamic types and
hooks accepted during deserialization:
import pyfory
from pyfory import DeserializationPolicy
dangerous_modules = {"subprocess", "os", "__builtin__"}
class SafeDeserializationPolicy(DeserializationPolicy):
def validate_class(self, cls, is_local, **kwargs):
if cls.__module__ in dangerous_modules:
raise ValueError(f"Blocked dangerous class: {cls.__module__}.{cls.__name__}")
def intercept_reduce_call(self, callable_obj, args, **kwargs):
if getattr(callable_obj, "__name__", "") == "Popen":
raise ValueError("Blocked attempt to invoke subprocess.Popen")
return None
def intercept_setstate(self, obj, state, **kwargs):
if isinstance(state, dict) and "password" in state:
state["password"] = "***REDACTED***"
return None
policy = SafeDeserializationPolicy()
fory = pyfory.Fory(xlang=False, ref=True, strict=False, policy=policy)
Available policy hooks include:
Reference validation hooks reject by raising exceptions and otherwise leave deserialized references unchanged.
Security Checklist
- Keep
strict=Truefor untrusted data. - Register all expected application types before deserialization.
- Use
DeserializationPolicywhenstrict=Falseis necessary. - Keep
max_depthlow enough to reject unexpectedly deep payloads. - Do not treat xlang/native mode choice as a security control.
Related Topics
- Basic Serialization - Using configured Fory
- Type Registration - Registration patterns
- Native Serialization - Python-only object serialization
