@Ap.using_scope()

[CEXT-Dan]

adds a scope to a function

import traceback
from pyrx import Ap, Db
 
class LifeTime:
    def __init__(self, name):
        self.name = name
        print(f"Object {self.name} created")
 
    def __del__(self):
        print(f"Object {self.name} destroyed")
 
@Ap.Command()
def doit1():
    try:
        database = LifeTime("1")
        @Ap.using_scope()
        def using_1() -> None: #this can be any name
            entity2 = LifeTime("2")
            entity3 = LifeTime("3")
            entity4 = LifeTime("4")
            
        @Ap.using_scope()
        def using_2() -> None:
            entity5 = LifeTime("5")
            entity6 = LifeTime("6")
            entity7 = LifeTime("7")
 
    except Exception as err:
        traceback.print_exception(err)

Command: DOIT1
Object 1 created
Object 2 created
Object 3 created
Object 4 created
Object 2 destroyed
Object 3 destroyed
Object 4 destroyed
Object 5 created
Object 6 created
Object 7 created
Object 5 destroyed
Object 6 destroyed
Object 7 destroyed
Object 1 destroyed

[CEXT-Dan]

intended for side databases

import traceback
from pyrx import Ap, Db

@Ap.Command()
def doit2():
    try:
        db = Db.Database(False, True)
        db.readDwgFile("E:\\temp\\Floor Plan Sample1.dwg")
        db.closeInput(True)

        @Ap.using_scope()
        def using_1():
            ms = db.modelSpace()
            ents = [Db.Entity(id) for id in ms.objectIds(Db.Entity.desc())]
            types = [ent.isA().dxfName() for ent in ents]
            print(len(types))
            
        @Ap.using_scope()
        def using_2():
            ms = db.modelSpace()
            ents = [Db.Entity(id) for id in ms.objectIds(Db.Entity.desc())]
            types = [ent.isA().dxfName() for ent in ents]
            print(len(types))

    except Exception as err:
        traceback.print_exception(err)

[CEXT-Dan]

to be published in v2.2.31

[gswifort]

Do I understand correctly that the Ap.using_scope() decorator simply executes the decorated function? I don't quite understand the test below - you're checking if the loaded database contains arcs, but that's not the subject of the test...? If you want to check if the decorator actually called the using function, this test will always succeed (provided the database contains arcs) - if the function doesn't execute, the test will still succeed because the assert statement is inside the function (which won't be executed).

PyRx/tests/test_core/test_PyDb/test_Database.py

Lines 365 to 374 in 4c53df8

	def test_using_decorator(self):
	sdb = Db.Database(False, True)
	sdb.readDwgFile(str(MEDIA_DIR / "sidedb.dwg"))
	sdb.closeInput(True)
	@Ap.using_scope()
	def using() -> None:
	ms = sdb.modelSpace()
	crvs = [Db.Curve(id) for id in ms.objectIds(Db.Curve.desc())]
	assert(len(crvs) != 0)

[CEXT-Dan]

Hi, so I was looking for a way to control when objects are garbage collected
Paul recommended that I use a decorator, that just calls itself to introduce a new scope. So in this example, A represents that database, and I want it to be destroyed last.

Regarding the test, if it does not crash CAD, then it passes. However, I see your point, I can improve the tests

class A:
    def __init__(self, name):
        self.name = name
        print(f"Object {self.name} created")

    def __del__(self):
        print(f"Object {self.name} destroyed")

def foo():
    one = A("one")
    @Ap.using_scope()
    def _() -> None:
        two = A("two")
        three = A("three")

Object one created
Object two created
Object three created
Object two destroyed
Object three destroyed
Object one destroyed

[CEXT-Dan]

def one():
    sdb = Db.Database(False, True)
    sdb.readDwgFile("E:\\temp\\Floor Plan Sample1.dwg")
    sdb.closeInput(True)
    crvs = []
    @Ap.using_scope()
    def _() -> None:
        ms = sdb.modelSpace()
        crvs.extend([Db.Curve(id) for id in ms.objectIds(Db.Curve.desc())])         
    print(len(crvs) != 0)
    
def two():
    sdb = Db.Database(False, True)
    sdb.readDwgFile("E:\\temp\\Floor Plan Sample1.dwg")
    sdb.closeInput(True)
    crvs = []
    ms = sdb.modelSpace()
    crvs.extend([Db.Curve(id) for id in ms.objectIds(Db.Curve.desc())])         
    print(len(crvs) != 0)
    # crash because sdb is deleted before ms can close 

[CEXT-Dan]

# python (without any scope)
Object one created
Object two created
Object three created
Object one destroyed
Object two destroyed
Object three destroyed

# C++
Object one created
Object two created
Object three created
Object three destroyed
Object two destroyed
Object one destroyed

[gswifort]

👌

[CEXT-Dan]

I have a question, how can I add new stuff, for example, this decorator, but not introduce a new namespace? How can I have both pure python and C++ in the same module, from the perspective of the user?

@Ap.using_scope, or just @using_scope

I just want stuff to be there without having to hunt for it, i.e. I rarely use @command, I’m too lazy to type import command. if that make sense

[gswifort]

Sorry, I don't understand.

[CEXT-Dan]

Okay, probably not possible, something like this would be cool

from pyrx import Ap, Db, Ed

def foo():
    Ap.SomeClassOrFunctionInPureC()
    Ap.SomeClassOrFunctionInPurePython()

[gswifort]

It's enough to do it in pyrx/__init__.py, but you would still need to update the pyi files.

[CEXT-Dan]

Okay, I’ll goof around with that, I don’t want to break the code just yet
I want to run performance test with @Ap.using_scope() and the same in Python.
I’m also going to be traveling over the next couple months