Re: [Python-Dev] Python Language Summit at EuroPython: 19th June
Hi Michael, Sorry for the late reply; it's been kinda busy around here. If there are places left, I'll definitely be there at the summit. Congratulations on your impending doom! (And sorry to hear that you might not be there in Florence.) Mark On Sat, Apr 16, 2011 at 3:50 PM, Michael Foord wrote: > Hello all, > > This is an invite to all core-python developers, and developers of > alternative implementations, to attend the Python Language Summit at > EuroPython. The summit will be on June 19th and EuroPython this year will be > held at the beautiful city of Florence in Italy. > > http://ep2011.europython.eu/ > > If you are not a core-Python developer but would like to attend then please > email me privately and I will let you know if spaces are available. If you > are a core developer, or you have received a direct invitation, then please > respond by private email to let me know if you are able to attend. A maybe > is fine, you can always change your mind later. Attending for only part of > the day is fine. > > We expect the summit to run from 10am - 4pm with appropriate breaks. > > Like previous language summits it is an opportunity to discuss topics like, > Python 3 adoption, PEPs and changes for Python 3.3, the future of Python > 2.7, documentation, package index, web site, etc. > > If you have topics you'd like to discuss at the language summit please let > me know. > > Volunteers for taking notes at the language summit, for posting to > Python-dev and the Python Insiders blog after the event, would be much > appreciated. > > All the best, > > Michael Foord > > N.B. Due to my impending doom (oops, I mean impending fatherhood) I am not > yet 100% certain I will be able to attend. If I can't I will arrange for > someone else to chair. > > -- > http://www.voidspace.org.uk/ > > May you do good and not evil > May you find forgiveness for yourself and forgive others > May you share freely, never taking more than you give. > -- the sqlite blessing http://www.sqlite.org/different.html > > ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Python Support on OpenVMS
Hi Folks, I am Sandeep Mathew from OpenVMS engineering in Hewlett-Packard. I have worked on various components of the OpenVMS operating system including MONITOR, TDF, EXEC, LIBRTL, DCL and SYSMAN. I happened to read this blog post about dropping OpenVMS support for further releases of python here: http://blog.python.org/2011/05/python-33-to-drop-support-for-os2.html. I am willing to spend time and effort to ensure that python remains supported on OpenVMS. Please let me know what needs to be done for continued OpenVMS Support in Python. Looking forward to working with the Python community. Regards Sandeep Mathew ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Python Support on OpenVMS
Welcome Sandeep, > I am willing to spend time and effort to ensure that python remains supported > on OpenVMS. Please let me know what needs to be done for continued > OpenVMS Support in Python. Looking forward to working with the Python > community. The first thing would be to check whether the current development tree (the future Python 3.3) compiles and works fine for OpenVMS. Given that 3.x has had many changes compared to 2.x, this is not guaranteed. Instructions for getting the source tree are here: http://docs.python.org/devguide/setup.html Once the interpreter compiled fine, the second step is to run the test suite: http://docs.python.org/devguide/runtests.html Any compilation errors and test suite failures should be reported to the bug tracker (http://bugs.python.org/), preferably with patches since I doubt any of us would be able to fix the issues themselves. If you have any questions, don't hesitate to ask. Regards Antoine. ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-checkins] cpython (2.7): (Merge 3.1) Issue #12012: ssl.PROTOCOL_SSLv2 becomes optional
Le 11/05/2011 20:08, Victor Stinner a écrit : >>> (Merge 3.1) Issue #12012: ssl.PROTOCOL_SSLv2 becomes optional >> “(Merge 3.1)” is inaccurate for 2.7. > Ah, why? I did not use "hg merge" command (but hg export|hg import), but > it's a "merge" between two branches. Which term would you use? I prefer to use merge only to refer to hg merges. The 2.7 and 3.x lines are independent, so I wouldn’t put any marker in the commit message, just use the same as the message used in 3.1. Regards ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-checkins] Python Regression Test Failures doc (1)
Hi, Le 08/05/2011 22:00, Neal Norwitz a écrit : > rm -rf build/* > rm -rf tools/sphinx > rm -rf tools/pygments > rm -rf tools/jinja2 > rm -rf tools/docutils > Checking out Sphinx... > svn: PROPFIND request failed on '/projects/external/Sphinx-0.6.5/sphinx' > svn: PROPFIND of '/projects/external/Sphinx-0.6.5/sphinx': Could not resolve > hostname `svn.python.org': Host not found (http://svn.python.org) > make: *** [checkout] Error 1 I always wonder about these messages. They’re mostly error messages recently; what are python-checkins subscribers supposed to do in reaction? In non-error mode, what are they useful for? Thanks in advance for enlightening me. Regards ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-checkins] cpython (3.1): Fix for issue 10684: Folders get deleted when trying to change case with
Hi,
Le 06/05/2011 11:32, ronald.oussoren a écrit :
> http://hg.python.org/cpython/rev/26da299ca88e
> summary:
> Fix for issue 10684: Folders get deleted when trying to change case with
> shutil.move (case insensitive file systems only)
>
> -except OSError:
> +except OSError as exc:
> if os.path.isdir(src):
> if _destinsrc(src, dst):
> raise Error("Cannot move a directory '%s' into itself '%s'."
> % (src, dst))
Is this change a debugging leftover?
Regards
___
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Summary of Python tracker Issues
ACTIVITY SUMMARY (2011-05-06 - 2011-05-13)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open2784 ( +1)
closed 21069 (+52)
total 23853 (+53)
Open issues with patches: 1198
Issues opened (36)
==
#6011: python doesn't build if prefix contains non-ascii characters
http://bugs.python.org/issue6011 reopened by haypo
#11786: ConfigParser.[Raw]ConfigParser optionxform()
http://bugs.python.org/issue11786 reopened by eric.araujo
#11873: test_regexp() of test_compileall fails occassionally
http://bugs.python.org/issue11873 reopened by haypo
#11977: Document int.conjugate, .denominator, ...
http://bugs.python.org/issue11977 reopened by georg.brandl
#12019: Dead or buggy code in importlib.test.__main__
http://bugs.python.org/issue12019 opened by eric.araujo
#12020: Attribute error with flush on stdout,stderr
http://bugs.python.org/issue12020 opened by Jimbofbx
#12021: mmap.read requires an argument
http://bugs.python.org/issue12021 opened by rich-noir
#12022: AttributeError should report the same details when raised by l
http://bugs.python.org/issue12022 opened by dholth
#12024: 2.6 svn and hg branches are out of sync
http://bugs.python.org/issue12024 opened by barry
#12026: Support more of MSI api
http://bugs.python.org/issue12026 opened by markm
#12028: threading._get_ident(): remove it in the doc and make it publi
http://bugs.python.org/issue12028 opened by haypo
#12029: ABC registration of Exceptions
http://bugs.python.org/issue12029 opened by acooke
#12034: check_GetFinalPathNameByHandle() suboptimal
http://bugs.python.org/issue12034 opened by pitrou
#12037: test_email failures under Windows with the eol extension activ
http://bugs.python.org/issue12037 opened by pitrou
#12038: assertEqual doesn't display newline differences quite well
http://bugs.python.org/issue12038 opened by pitrou
#12040: Expose a Process.sentinel property (and fix polling loop in Pr
http://bugs.python.org/issue12040 opened by pitrou
#12042: What's New multiprocessing example error
http://bugs.python.org/issue12042 opened by davipo
#12043: Update shutil documentation
http://bugs.python.org/issue12043 opened by sandro.tosi
#12045: external shell command executed twice in ctypes.util._get_sona
http://bugs.python.org/issue12045 opened by pitrou
#12046: Windows build identification incomplete
http://bugs.python.org/issue12046 opened by loewis
#12048: Python 3, ZipFile Bug In Chinese
http://bugs.python.org/issue12048 opened by yaoyu
#12049: expose RAND_bytes() function of OpenSSL
http://bugs.python.org/issue12049 opened by haypo
#12050: unconsumed_tail of zlib.Decompress is not always cleared on de
http://bugs.python.org/issue12050 opened by Takeshi.Yoshino
#12053: Add prefetch() for Buffered IO (experiment)
http://bugs.python.org/issue12053 opened by jcon
#12055: doctest not working on nested functions
http://bugs.python.org/issue12055 opened by dabrahams
#12057: HZ codec has no test
http://bugs.python.org/issue12057 opened by haypo
#12059: hashlib does not handle missing hash functions correctly
http://bugs.python.org/issue12059 opened by Ian.Wienand
#12060: Python doesn't support real time signals
http://bugs.python.org/issue12060 opened by haypo
#12063: tokenize module appears to treat unterminated single and doubl
http://bugs.python.org/issue12063 opened by Devin Jeanpierre
#12065: test_ssl failure when svn.python.org fails to resolve
http://bugs.python.org/issue12065 opened by r.david.murray
#12066: Empty ('') xmlns attribute is not properly handled by xml.dom.
http://bugs.python.org/issue12066 opened by atamyrat
#12067: Doc: remove errors about mixed-type comparisons.
http://bugs.python.org/issue12067 opened by terry.reedy
#12068: test_logging failure in test_rollover
http://bugs.python.org/issue12068 opened by pitrou
#12069: test_signal.test_without_siginterrupt() failure on AMD64 OpenI
http://bugs.python.org/issue12069 opened by haypo
#12070: Unlimited loop in sysconfig._parse_makefile()
http://bugs.python.org/issue12070 opened by haypo
#12071: test_concurrent_futures.test_context_manager_shutdown() hangs
http://bugs.python.org/issue12071 opened by haypo
Most recent 15 issues with no replies (15)
==
#12071: test_concurrent_futures.test_context_manager_shutdown() hangs
http://bugs.python.org/issue12071
#12069: test_signal.test_without_siginterrupt() failure on AMD64 OpenI
http://bugs.python.org/issue12069
#12066: Empty ('') xmlns attribute is not properly handled by xml.dom.
http://bugs.python.org/issue12066
#12063: tokenize module appears to treat unterminated single and doubl
http://bugs.python.org/issue12063
#12059: hashlib does not handle missing hash functions correctly
http://bugs.python.org/issue12059
#12055: doctest not working on nested functions
htt
Re: [Python-Dev] Problems with regrtest and with logging
Le 11/05/2011 21:45, Vinay Sajip a écrit : > Éric Araujo netwok.org> writes: >> I thought that if we set the level on the logger, we would prevent >> third-party code to get some messages. E.g., we set level to INFO but >> pip uses some packaging functions and would like to get DEBUG messages. > Then pip can set the level of the packaging logger as it wishes, perhaps in > response to command-line arguments for verbosity. It'd be easier for pip to do > that, regardless of which handlers are attached. And pip itself might be being > used, say by virtualenv. It's hard in general to say what the top-level code > will be, and generally that's the code which should set the handlers. Okay. I’ll go ahead and remove handlers (except for the command-line script), and set the level on the logger. If it turns out that the code in packaging incorrectly resets the level set by calling code, we’ll fix it later; now we want to fix the tests to produce the patch that will add packaging to CPython. > The levels set by a library for its loggers are merely defaults. The conflict here is that there’s a class setting the logging level on instantiation, which could reset the level set by calling code. Thanks again for your messages (and blog). ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Problems with regrtest and with logging
On Sat, May 7, 2011 at 3:51 AM, Éric Araujo wrote: > regrtest helpfully reports when a test leaves the environment unclean > (sys.path, os.environ, logging._handlerList) A quick follow-up: I talked about regrtest with RDM on IRC, and I will use the context manager that detects changes in the “if __name__ == '__main__'” blocks of our test files to find the guilty ones. Some warnings are subtle to track down: the test runs a command which instantiates a class which calls a function and here’s the code that sets an environment variable. In the future, I’ll take part in the efforts to reimplement parts of regrtest with new unittest features. Right now it’s quite painful to have to use either unittest to run just one file or regrtest to get the warnings. Cheers ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Summary of Python tracker Issues
The summary mails part 1 was declared as US-ASCII, 8bit, but it contained a UTF-8 character: > #12056: "???" (HORIZONTAL ELLIPSIS) should be an alternative syntax fo > http://bugs.python.org/issue12056 closed by benjamin.peterson This is handled without any problem by Python 3000 due to David Murrays patch of issue 11605 for 3.2 and 3.3. (It however broke my obviously insufficient non-postman thing :(, and it's of course not a valid mail, strictly speaking. So i report this just in case your stricken MUAs simply do the right thing and noone recognizes it at all.) May the juice be with you -- Steffen, sdaoden(*)(gmail.com) ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
