Kracekumar
Kracekumar
`def start_with(self, x):` I would suggest this func to be renamed as `def starts_with(self, x):`, this will be better appealing since `python` `strings` already have func named `startswith`
I have django view which calls following function to execute the code. ``` python def execute(code): with tempfile.NamedTemporaryFile() as tmp_file: tmp_file.write(code.encode('utf-8')) tmp_file.flush() print("Input file: {0}".format(tmp_file.name)) TIMEOUT = getattr(settings, 'TIMEOUT', 10)...
Previously Junction worked on Python 2 and Python 3 but deployed only in python 2 in server. From now use only Python 3 in server and remove support for Python...
The functionality is available here https://github.com/pythonindia/junction/blob/e8cefd7910f807873a9f0d7650f6868ccffbeac0/junction/proposals/dashboard.py#L287. You need to create a command line version.
It will be cool to run junction on pypy and see if we can use it production. If the test benchmark is on par with CPython (we love faster one's...
Junction has a large number of filters around `conference, proposals, comment, proposal type, and section`. As long as these filters are on foreign key, performance is fine. The problem arises...
New relic free service provides analysis on code performance and database queries time. This is beneficial for optimization.
Junction doesn't have API to expose proposals public data. There are APIs for `conference, schedule, venue` etc ... Junction needs to have API for the proposals. `Slug: /api/v1/proposals?conference_name=conference_name` API returns...