Re: Re: Progress migrating cffi and pycparser to libclang
Hi Etienne, On 5 January 2018 at 10:15, Etienne Robillard wrote: > Forwarding this thread to the CFFI developers... > If you're asking whether we could add libclang as a dependency to CFFI, the answer is no, sorry. I feel that I've already explained exactly this to you several times in private e-mails, so I'm writing down this fact here on the public python-cffi mailing list. Please stop asking the same question. For reference, here's my answer again. CFFI is meant to be used in a certain way. I know from experience that a few people keep thinking about it in a different way---sometimes for good reasons: it is tedious to wrap a very large library even if it is easy to copy-paste-tweak individual function definitions. So to automate the process these people usually want to parse real .h files, using libclang or better pycparser integration or something else; and that's cool. As I said there are already third-party projects that try to do something similar. Usually it is never completely general, but more focused on a particular style of .h files coming from a particular large project. Maybe you'll run into similar issues and make something that works in your case but not in others. Or maybe you'll manage to make it general enough. In all cases this won't be included inside CFFI, but could nevertheless be a successful separate project. Please think about it as a project *above* CFFI, maybe something you'll import and use inside a CFFI build script in order to provide content to ffi.cdef(). A bientôt, Armin. -- https://mail.python.org/mailman/listinfo/python-list
EuroPython 2006: Call for papers
Hi all, A shameless plug and reminder for EuroPython 2006 (July 3-5): * you can submit talk proposals until May 31st. * there is a refereed papers track; deadline for abstracts: May 5th. See the full call for papers below. A bientot, Armin Rigo & Carl Friedrich Bolz EuroPython 2006 CERN, Geneva, 3-5 July Refereed Track: Call for Paper http://www.europython.org EuroPython is the only conference in the Python world that has a properly prestigious peer-reviewed forum for presenting technical and scientific papers. Such papers, with advanced and highly innovative contents, can equally well stem from academic research or industrial research. We think this is an important function for EuroPython, so we are even making some grants available to help people with travel costs. For this refereed track, we will be happy to consider papers in subject areas including, but not necessarily limited to, the following: * Python language and implementations * Python modules (in the broadest sense) * Python extensions * Interoperation between Python and other languages / subsystems * Scientific applications of Python * Python in Education * Benchmarking Python We are looking for Python-related scientific and technical papers of advanced, highly innovative content that present the results of original research (be it of the academic or "industrial research" kind), with proper attention to "state of the art" and previous relevant literature/results (whether such relevant previous literature is itself directly related to Python or not). We do not intend to let the specific subject area block a paper's acceptance, as long as the paper satisfies other requirements: innovative, Python-related, reflecting original research, with proper attention to previous literature. Abstracts = Please submit abstracts of no more than 200 words to the refereeing committee. You can send submissions no later than 5 May 2006. We shall inform you whether your paper has been selected no later than 15 May 2006. For all details regarding the submission of abstracts, please see the EuroPython website (http://www.europython.org). Papers If your abstract is accepted, you must submit your corresponding paper before 17 June 2006. You should submit the paper as a PDF file, in A4 format, complete, "stand-alone", and readable on any standards-compliant PDF reader (basically, the paper must include all fonts and figures it uses, rather than using external pointers to them; by default, most PDF-preparation programs typically produce such valid "stand-alone" PDF documents). Refereeing ====== The refereeing committee, selected by Armin Rigo, will examine all abstracts and papers. The committee may consult external experts as it deems fit. Referees may suggest or require certain changes and editing in submissions, and make acceptance conditional on such changes being performed. We expect all papers to reflect the abstract as approved and reserve the right, at our discretion, to reject a paper, despite having accepted the corresponding abstract, if the paper does not substantially correspond to the approved abstract. Presentation The paper must be presented at EuroPython by one or more of the authors. Presentation time will be either half an hour or an hour, including time for questions and answers, depending on each paper's details, and also on the total number of papers approved for presentation. Proceedings === We will publish the conference's proceedings in purely electronic form. By presenting a paper, authors agree to give the EuroPython conference non-exclusive rights to publish the paper in electronic forms (including, but not limited to, partial and total publication on web sites and/or such media as CDROM and DVD-ROM), and warrant that the papers are not infringing on the rights of any third parties. Authors retain all other intellectual property rights on their submitted abstracts and papers excepting only this non-exclusive license. Subsidised travel = We have funds available to subsidise travel costs for some presenters who would otherwise not be able to attend EuroPython. When submitting your abstract, please indicate if you would need such a subsidy as a precondition of being able to come and present your paper. (Yes, this possibility does exist even if you are coming from outside of Europe. Papers from people in New Zealand who can only come if their travel is subsidised, for example, would be just fine with us...). -- http://mail.python.org/mailman/listinfo/python-list
Re: - E04 - Leadership! Google, Guido van Rossum, PSF
Hi Alex, On Mon, 9 Jan 2006, Alex Martelli wrote: > 50%, yes (the other 50% must come from private contributions, that's a > EU rule for research projects). It used to be thought that some of the > EU money could be used to help pay for sprint participants' travel > expenses, but apparently something has gone wrong on that score > (probably some EU administrative requirement) -- I didn't ever see any > of the travel-expense-help money that was promised to me on one > occasion, so I had to swallow that cost myself. This is not the whole truth. We have some procedure now for funding travel costs, although it's admittedly very bureaucratic :-( Anyway, independently of this, there are some people we are happy to see come back again and again to PyPy sprints even though we know their budget is extremely limited. We have always arranged things for them to minimize the costs. It's nothing like a "congress" where you have to pay XXX/day for having water and cake brought to the tables by the staff at 10am. I can certainly say that attending a PyPy sprint is not expensive at all; I'd expect the major problem to be rather to find a week's free time for it. On the bureaucratic side: Alex, we *have* a procedure at this point, and we have been trying to contact you several time in the past months -- with no success as far as I know, so I'll try via comp.lang.python this time :-) If you still feel like seeing your money back in exchange for some papers to fill and sign, please show up... A bientot, Armin -- http://mail.python.org/mailman/listinfo/python-list
Re: - E04 - Leadership! Google, Guido van Rossum, PSF
Hi Alex, On Mon, 9 Jan 2006, Alex Martelli wrote: > 50%, yes (the other 50% must come from private contributions, that's a > EU rule for research projects). It used to be thought that some of the > EU money could be used to help pay for sprint participants' travel > expenses, but apparently something has gone wrong on that score > (probably some EU administrative requirement) -- I didn't ever see any > of the travel-expense-help money that was promised to me on one > occasion, so I had to swallow that cost myself. This is not the whole truth. We have some procedure now for funding travel costs, although it's admittedly very bureaucratic :-( Anyway, independently of this, there are some people we are happy to see come back again and again to PyPy sprints even though we know their budget is extremely limited. We have always arranged things for them to minimize the costs. It's nothing like a "congress" where you have to pay XXX/day for having water and cake brought to the tables by the staff at 10am. I can certainly say that attending a PyPy sprint is not expensive at all; I'd expect the major problem to be rather to find a week's free time for it. On the bureaucratic side: Alex, we *have* a procedure at this point, and we have been trying to contact you several time in the past months -- with no success as far as I know, so I'll try via comp.lang.python this time :-) If you still feel like seeing your money back in exchange for some papers to fill and sign, please show up... A bientot, Armin -- http://mail.python.org/mailman/listinfo/python-list
Post-EuroPython 2005 PyPy Sprint 1st - 7th July 2005
Post-EuroPython 2005 PyPy Sprint 1st - 7th July 2005 == The next PyPy sprint is scheduled right after EuroPython 2005 in Gothenborg, Sweden. Its main focus is translation to lower level backends but there are also other possible topics. We'll give newcomer-friendly introductions. To learn more about the new PyPy Python-in-Python implementation look here: http://codespeak.net/pypy On a side note, there are a number of sub projects that may be interesting for participating in google's summer-of-code event (deadline June 14th!). The PyPy group is willing to mentor projects that have some link with PyPy, so if you are accepted in such a project, the sprint could also serve as a good meeting and kick-off point. Further down you'll find some examples, but there are certainly more and bigger ones :-) Goals and topics of the sprint -- The main, though not the only, focus of the sprint will be on the "translation" aspect of PyPy. The goal here is to progress towards a completely translated PyPy. How much will already have been done before EuroPython is unknown; as a guess, we will be left with: - completing the "rtyper", the piece of code that assigns low-level C-like types to high-level RPython objects (lists, dicts, instances, etc.) and low-level control flow graphs to high-level ones; - polish off the GenC and GenLLVM back-ends, responsible for turning the low-level C-like flow graphs into real C or LLVM source code. See http://codespeak.net/pipermail/pypy-dev/2005q2/002136.html for more information (10th of June status). Non-translation-related topics are welcome too. Here are some suggestions from the issue tracker (https://codespeak.net/issue/pypy-dev/): - integrate the parser module, possibly making it RPython conformant; - rewrite in Python a C module you are familiar with (partial list of missing/incomplete modules: os, math, array, regular expressions, binascii...) - implement Python 2.3's import hook extensions (zip-imports etc.) - fix Windows-related issues, '%'-formatting rounding errors, add missing docstrings on app-level built-in types and functions, etc. - weakrefs (but this requires discussion and planning on pypy-dev before the sprint! feel free to start such a discussion, though.) Location & Accomodation The sprint will be held in the former Math Center building near the crossing of Gibraltargatan and Eklandagatan. Entrance is on the middle of the side facing Gibraltargatan. The doors to the building are normally locked, so you need the phone number of somebody inside to get in. Instructions on whom to call will be posted on the door. The sprint will be co-located with several other sprints. See the `EuroPython Wiki`_, to find out what other sprints will be running. Nearest, and probably cheapest is to book accomodation at SGS Veckobostäder through the Europython website. This option will be available until about 20 June. .. _`EuroPython special accomodation`: http://www.europython.org/sections/accomodation/special_accomodation .. _`EuroPython Wiki`: http://www.europython.org/sections/sprints_and_wiki Exact times --- The public Pypy sprint is held Friday 1st July - Thursday 7 July 2005. Hours will be from 09:00 until people have had enough. It's a good idea to arrive a day before the sprint starts. (There is a sprint for people who are familiar with the Pypy codebase before Europython as well. This will be held at Jacob & Laura's home on Götabergsgatan 22.) Network, Food, currency Sweden is not part of the Euro zone. One SEK (krona in singular, kronor in plural) is roughly 1/10th of a Euro (9.15 SEK to 1 Euro). There are some pizzerias, kebab places and the like close to the venue. Their food is edible and cheap, but not very good. For good food, you need to go downtown. You need a wireless network card to access the network. You will be issued a login to the Chalmers NOMAD network. This will allow you to use access points all over Chalmers. However, we can likely provide a wireless/ethernet bridge. Sweden uses the same kind of plugs as Germany. 230V AC. Registration etc.pp. Please subscribe to the `PyPy sprint mailing list`_, introduce yourself and post a note that you want to come. Feel free to ask any questions there! .. _`PyPy sprint mailing list`: http://codespeak.net/mailman/listinfo/pypy-sprint -- Armin Rigo & the PyPy team -- http://mail.python.org/mailman/listinfo/python-list
Psyco 1.3 released
Hi all, Psyco 1.3 has been released: http://sourceforge.net/project/showfiles.php?group_id=41036 Includes support for Python 2.4 (and of course still supports Python 2.1 to 2.3). As always it comes with a few bugfixes, including a memory leak when using the profiler. Another good news is that the built-in functions that read the local variables -- locals(), eval(), execfile(), vars(), dir(), input() -- now work correctly! A bientot, Armin -- http://mail.python.org/mailman/listinfo/python-list
