aitbc
816e258d4c
Development Artifact Cleanup: ✅ BROTHER_NODE REORGANIZATION: Moved development test node to appropriate location - dev/test-nodes/brother_node/: Moved from root directory for better organization - Contains development configuration, test logs, and test chain data - No impact on production systems - purely development/testing artifact ✅ DEVELOPMENT ARTIFACTS IDENTIFIED: - Chain ID: aitbc-brother-chain (test/development chain) - Ports: 8010 (P2P) and 8011 (RPC) - different from production - Environment: .env file with test configuration - Logs: rpc.log and node.log from development testing session (March 15, 2026) ✅ ROOT DIRECTORY CLEANUP: Removed development clutter from production directory - brother_node/ moved to dev/test-nodes/brother_node/ - Root directory now contains only production-ready components - Development artifacts properly organized in dev/ subdirectory DIRECTORY STRUCTURE IMPROVEMENT: 📁 dev/test-nodes/: Development and testing node configurations 🏗️ Root Directory: Clean production structure with only essential components 🧪 Development Isolation: Test environments separated from production BENEFITS: ✅ Clean Production Directory: No development artifacts in root ✅ Better Organization: Development nodes grouped in dev/ subdirectory ✅ Clear Separation: Production vs development environments clearly distinguished ✅ Maintainability: Easier to identify and manage development components RESULT: Successfully moved brother_node development artifact to dev/test-nodes/ subdirectory, cleaning up the root directory while preserving development testing environment for future use.
64 lines
2.0 KiB
Python
Executable File
64 lines
2.0 KiB
Python
Executable File
|
|
__all__ = ['BaseLoader', 'FullLoader', 'SafeLoader', 'Loader', 'UnsafeLoader']
|
|
|
|
from .reader import *
|
|
from .scanner import *
|
|
from .parser import *
|
|
from .composer import *
|
|
from .constructor import *
|
|
from .resolver import *
|
|
|
|
class BaseLoader(Reader, Scanner, Parser, Composer, BaseConstructor, BaseResolver):
|
|
|
|
def __init__(self, stream):
|
|
Reader.__init__(self, stream)
|
|
Scanner.__init__(self)
|
|
Parser.__init__(self)
|
|
Composer.__init__(self)
|
|
BaseConstructor.__init__(self)
|
|
BaseResolver.__init__(self)
|
|
|
|
class FullLoader(Reader, Scanner, Parser, Composer, FullConstructor, Resolver):
|
|
|
|
def __init__(self, stream):
|
|
Reader.__init__(self, stream)
|
|
Scanner.__init__(self)
|
|
Parser.__init__(self)
|
|
Composer.__init__(self)
|
|
FullConstructor.__init__(self)
|
|
Resolver.__init__(self)
|
|
|
|
class SafeLoader(Reader, Scanner, Parser, Composer, SafeConstructor, Resolver):
|
|
|
|
def __init__(self, stream):
|
|
Reader.__init__(self, stream)
|
|
Scanner.__init__(self)
|
|
Parser.__init__(self)
|
|
Composer.__init__(self)
|
|
SafeConstructor.__init__(self)
|
|
Resolver.__init__(self)
|
|
|
|
class Loader(Reader, Scanner, Parser, Composer, Constructor, Resolver):
|
|
|
|
def __init__(self, stream):
|
|
Reader.__init__(self, stream)
|
|
Scanner.__init__(self)
|
|
Parser.__init__(self)
|
|
Composer.__init__(self)
|
|
Constructor.__init__(self)
|
|
Resolver.__init__(self)
|
|
|
|
# UnsafeLoader is the same as Loader (which is and was always unsafe on
|
|
# untrusted input). Use of either Loader or UnsafeLoader should be rare, since
|
|
# FullLoad should be able to load almost all YAML safely. Loader is left intact
|
|
# to ensure backwards compatibility.
|
|
class UnsafeLoader(Reader, Scanner, Parser, Composer, Constructor, Resolver):
|
|
|
|
def __init__(self, stream):
|
|
Reader.__init__(self, stream)
|
|
Scanner.__init__(self)
|
|
Parser.__init__(self)
|
|
Composer.__init__(self)
|
|
Constructor.__init__(self)
|
|
Resolver.__init__(self)
|