Made BMConnectionPool as global runtime variable in connectionpool from singleton #2220
No reviewers
Labels
No Label
bug
build
dependencies
developers
documentation
duplicate
enhancement
formatting
invalid
legal
mobile
obsolete
packaging
performance
protocol
question
refactoring
regression
security
test
translation
usability
wontfix
No Milestone
No project
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Bitmessage/PyBitmessage-2024-12-17#2220
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "test2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
If we don't conditionally import the connection pool then this check isn't necessary anymore.
@ -2,21 +2,17 @@
Network subsystem package
"""
how about we use a different name for the object than the class name? How about
network.connectionpool
for instance and we keepnetwork.BMConnectionPool
as the class name?I'm not sure this try/except is needed anymore once we fix the circular imports.
@ -19,2 +13,4 @@
import state
from .announcethread import AnnounceThread
import connectionpool # pylint: disable=relative-import
from .addrthread import AddrThread
I think we can use the object name here, i.e.
connectionpool
as I recommended above.why not
from network import connectionpool
?again here we could use
from network import connectionpool
@ -2,21 +2,17 @@
Network subsystem package
"""
done, renamed as pool
because it will create a new reference/new copy of connectionpool obj which would be different from network one.
same reason as above, and other thing it is also throwing import error