[Python-Dev] Re: EuroPython 2019 sprints
Hello, I'll be at the EuroPython CPython sprints too, happy to help out. On Thu, Jun 13, 2019 at 6:36 PM Steve Dower wrote: > Just letting everyone know that I signed up any core devs who are going > to be at EuroPython to run sprints :) (including myself, since I'll be > there) FWIW, I read this as a done deal, not inviting a confirmation for me. A [recent discourse post] suggests otherwise :) [recent discourse post]: https://discuss.python.org/t/europython-2019-talks-sprints/1900/5?u=encukou ___ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/6BYA75HSN6RX6F5LWAYEKV6PBO3IHKXZ/
[Python-Dev] Re: EuroPython 2019 sprints
On 13/06/2019 18.28, Steve Dower wrote: > Hi all > > Just letting everyone know that I signed up any core devs who are going > to be at EuroPython to run sprints :) (including myself, since I'll be > there) > > Like PyCon US, the sprints at EuroPython will attract many first-time > contributors, so it will be helpful to have as many people who > understand our workflow around to help out. We might also be able to get > some of our own contributions done. > > For those who didn't hear, the EuroPython Society is offering a grant > for core developers to get free attendance at EuroPython (see > https://www.europython-society.org/core-grant). If you take this, it > would be a nice gesture of thanks to help support the sprints! > > And in the meantime, if you see an easy bug on the tracker, please mark > it as "Easy" or "Easy (C)" and post an explanation of how to fix it. > That way we will have a good supply of tasks for new contributors. I'm at EP but I'm leaving on Saturday already. There is a small chance that I can attend the sprints for a couple of hours. Christian ___ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/RA2IGTNPMTMW5GWB52IYMFXCSNTY3CNN/
[Python-Dev] Re: bug(?) - unexpected frames being skipped in extract_stack with closures
If you believe this is a bug then please file an issue at bugs.python.org so it isn't lost. ___ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/6W2WDCPGRGTZM5GCD6QIMYZGQYRNATBP/
[Python-Dev] Re: bug(?) - unexpected frames being skipped in extract_stack with closures
If you believe this is a bug then please open an issue at bugs.python.org so we don't lose track of it. On Fri, Jun 21, 2019 at 11:09 AM Ed Peschko wrote: > Steven, > > Yes and I posted to python-dev for a reason - I'm almost positive that > this is a bug - or at least an inconsistency - in how python handles > stack frames WRT closures in some instances. In fact, the reason I > posted is because we hit this inconsistency in handling production > code - we need to have a reliable stack trace for all the functions we > call in logs so we can better track down issues when they occur and be > able to tie those issues to underlying code. > > If I add a pdb.set_trace() to the location inside the closure, I get a > different - in fact the correct - stack trace. Otherwise, like I said, > the stack trace points back to the place where the closure was > defined, not the actual place the closure was called. > > Unfortunately, it looks like this bug is not in a simple example that > I can readily reproduce (I just tried). so if I see it again i'll try > to simplify it to a point where it still manifests and post that. > > Ed > > On Fri, Jun 21, 2019 at 1:35 AM Steve Holden wrote: > > > > Hi Ed, > > > > Your note probably won't receive any other reply than this, because the > python-dev list is specifically for discussions about the development _of_, > rather than _with_, Python. > > > > A more appropriate forum is probably the Python list ( > [email protected]), about which you can discover more details at > Python-list Info Page. > > > > Kind regards, > > Steve Holden > > > > > > On Thu, Jun 20, 2019 at 3:40 AM Ed Peschko wrote: > >> > >> all, > >> > >> I'm writing a function meant to print out the context of a given > >> function call when executed - for example: > >> > >> 1. def main(): > >> 2. > >> 3. _st = stack_trace_closure("/path/to/log") > >> 4. _st() > >> 5. _st() > >> > >> would print out > >> > >> /path/to/file.py:4 > >> /path/to/file.py:5 > >> > >> for each line when executed. Basic idea is to create a closure and > >> associate that closure with a filename, then run that closure to print > >> to the log without needing to give the filename over and over again. > >> > >> So far so good. But when I write this function, the frames given by > >> getframeinfo or extract_stack skip the actual calling point of the > >> function, instead giving back the *point where the closure was > >> defined*. (in the above example, it would print /path/to/file.py:3, > >> /path/to/file.py:3 instead of incrementing to show 4 and 5). > >> > >> However, when I insert a pdb statement, it gives me the expected > >> calling frame where _st is actually called. > >> > >> What's going on here? It looks an awful lot like a bug to me, like an > >> extra frame is being optimized out of of the closure's stack > >> prematurely. > >> > >> I've tried this in python2.7 and python3.3, both show this. > >> > >> thanks much for any info, > >> > >> Ed > >> > >> code follows: > >> --- > >> > >> def stack_trace_closure(message, file_name=None, frame=3): > >> > >> fh = open(file_name, "w+") > >> > >> def _helper(): > >> return stack_trace(message, frame, fh) > >> > >> return _helper > >> > >> def stack_trace(message _frame, fh): > >> > >> _bt = traceback.extract_stack() > >> > >> fh.write( "%s:%s - %s" % (_bt[_frame][0], _bt[_frame][1], > _message)) > >> ___ > >> Python-Dev mailing list -- [email protected] > >> To unsubscribe send an email to [email protected] > >> https://mail.python.org/mailman3/lists/python-dev.python.org/ > >> Message archived at > https://mail.python.org/archives/list/[email protected]/message/4MKHPCRNAJACKIBMLILMQMUPTEVFD3HW/ > ___ > Python-Dev mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/[email protected]/message/DQBKRUI5ZMU6F3JHIVIZKT32DBOOQOLQ/ > ___ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/UFUE5S27KNZHKVJOUNNN3SM5G6UJ2FHT/
[Python-Dev] Re: Building Standalone Python Applications with PyOxidizer
Day-to-day packaging stuff seems to have migrated from distutils-sig maililng list to https://discuss.python.org/c/packaging. And congrats on the release! ___ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/PXOP4QUK6QSKSIOVHSMJJ3OXJ4XPY4CU/
[Python-Dev] Sponsoring Python development via the PSF
We now have https://www.python.org/psf/donations/python-dev/ for anyone to make donations via the PSF for directly supporting Python development (and we have the Sponsor button at https://github.com/python/cpython pointing to this link). ___ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/VJHE5BT5C3F7HCXLSPLACBH42QRUP45E/
[Python-Dev] Re: Sponsoring Python development via the PSF
That's great! "The PSF will use Python development fundraising to support CPython development and maintenance." Does someone have more info about that? Who will get the money, how, etc.? Victor Le lundi 24 juin 2019, Brett Cannon a écrit : > We now have https://www.python.org/psf/donations/python-dev/ for anyone to make donations via the PSF for directly supporting Python development (and we have the Sponsor button at https://github.com/python/cpython pointing to this link). -- Night gathers, and now my watch begins. It shall not end until my death. ___ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/55CZSDPNPXC7O254TKL5CMXOLU4I3MJH/
[Python-Dev] Re: [RELEASE] Python 3.7.4rc1 and 3.6.9rc1 are now available
On 19. 06. 19 7:19, Ned Deily wrote: Python 3.7.4rc1 and 3.6.9rc1 are now available. 3.7.4rc1 is the release preview of the next maintenance release of Python 3.7, the latest feature release of Python. 3.6.9rc1 is the release preview of the first security-fix release of Python 3.6. Assuming no critical problems are found prior to 2019-06-28, no code changes are planned between these release candidates and the final releases. These release candidates are intended to give you the opportunity to test the new security and bug fixes in 3.7.4 and security fixes in 3.6.9. We strongly encourage you to test your projects and report issues found to bugs.python.org as soon as possible. Please keep in mind that these are preview releases and, thus, their use is not recommended for production environments. You can find the release files, a link to their changelogs, and more information here: https://www.python.org/downloads/release/python-374rc1/ https://www.python.org/downloads/release/python-369rc1/ Hey Ned, I'm working on getting 3.7.4rc1 to Fedora rawhide (the "master branch" of Fedora). If nothing goes wrong with the build, it should land within a day. There are checks in Fedora that should uncover any suspicious test failures of our Python packages, if that happens, we'll report back hopefully before 2019-06-28 AOE. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/PR4EFLGVCBGTJSWXV3B3CMUPWRBRIUSF/
[Python-Dev] Re: Sponsoring Python development via the PSF
Victor Stinner wrote: > That's great! > "The PSF will use Python development fundraising to support CPython > development and maintenance." > Does someone have more info about that? Who will get the money, how, etc.? No because we have to see how much money we get first. ;) Without knowing how much we will get then you can probably assume it will go towards core dev sprint sponsorships like the page states. After that probably the PM role we have been talking about on the steering council to help sunset Python 2, then a PM-like role to help with GitHub issue migration. That's as far as the steering council has discussed things with the PSF in terms of short-term, concrete asks for money and staffing. After that it's my personal speculation, but I would hope something like the Django fellowship program. If we could get enough money to fund like 4 people to work on Python full-time it would be amazing and help us stay on top of things like pull requests. But all of this depends on companies actually giving money in the proper amounts in order to be able to do anything like this. I've been told by companies they have been wanting to donate money for ages but wanted to make sure it was helping Python's development. Well, this is their chance to prove they actually meant it. ;) > Victor > Le lundi 24 juin 2019, Brett Cannon [email protected]... > a écrit : > > We now have https://www.python.org/psf/donations/python-dev/... > > for anyone > > to make donations via the PSF for directly supporting Python development > > (and we have the Sponsor button at https://github.com/python/cpython... > > pointing to this link). > > -- > Night gathers, and now my watch begins. It shall not end until my death. ___ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/BGZI7NPQTCSHI3JNMKTSPV4XM7FPI7HZ/
[Python-Dev] Championing PEP 467
Nick Coghlan, I'm thinking about what you said, over a year ago, about finding a new champion for PEP 467. I think it would be a privilege to work on something like that, which may be used by millions of people over a period of years or decades. However, I have decided that I no longer have the time or interest. This PEP has been open but delayed for years. It was originally written in 2014 (apparently with the expectation that it would be included in Python 3.5). My initial attempt to implement it was in 2016. In 2018, Guido said "It's too late for 3.7 period, but there's no reason it can't be considered for 3.8.", but now 3.8 is already in beta. I didn't realize that this would go on for so long. I was working on a personal project, and at one point I was wishing for something like the proposed iterator methods. I thought the details were already decided and I just had to code the thing, which would take a few weeks or maybe a few months at most. I did not realize what I was getting myself into. I wish the best of luck to whoever decides to finish this effort. ___ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/6OIU5LREUAUQD3H7SEH75IJI7GSXSLVP/
