Fix bug on garbage collection of objects that have not been sent to python.

Author: alejandroinfante

src/PythonBridge-Pharo/PBPharoUiManager.class.st

@@ -7,7 +7,6 @@ Class {
 { #category : #'as yet unclassified' }
 PBPharoUiManager >> notify: aString [
 	Transcript show: aString asString.
-	super notify: aString asString.
 ]
 
 { #category : #hooks }

src/PythonBridge/PBObject.class.st

@@ -67,8 +67,8 @@ PBObject >> basicCreateObjectExpr: anExpression [
 	pythonVariable := varName.
 	self application commandFactory << (
 		self registerIdPyExpression: anExpression).
-	self registerObject
-	
+	self registerObject.
+	self application commandFactory send.
 ]
 
 { #category : #'as yet unclassified' }

src/PythonBridge/PBObjectFinalizationTest.class.st

@@ -25,6 +25,15 @@ PBObjectFinalizationTest >> tearDown [
 	super tearDown
 ]
 
+{ #category : #tests }
+PBObjectFinalizationTest >> testCreateObjectAndGcItBeforeSending [
+	"Bug when the object is garbage collected before sending the command to python, this trigger the gc in Python of an object that hasnt yer been created nor registered. Now we fixed this enforcing the message send in the basicCreateObject, though another way is to registering the object to the command with a hard-reference."
+	PBObject new basicCreateObjectExpr: 5.5.
+	Smalltalk garbageCollect.
+	Smalltalk garbageCollect.
+	self assert: true
+]
+
 { #category : #tests }
 PBObjectFinalizationTest >> testGCSimpleObj [
 	| obj id |