\o/
> On 26 juil. 2015, at 4:37 PM, Larry Hastings wrote:
>
>
> On behalf of the Python development community and the Python 3.5 release
> team, I'm delighted to announce the availability of Python 3.5.0b4. Python
> 3.5.0b4 is scheduled to be the last beta release; the next release will be
Thank you for your confirmation,
I am going to read the devguide.
> On 25 oct. 2015, at 7:50 PM, Raymond Hettinger
> wrote:
>
>
>>> On Oct 25, 2015, at 12:33 PM, Raymond Hettinger
>>> wrote:
>>>
>>> On Oct 22, 2015, at 10:02 AM, Brett Cannon wrote:
>>>
>>> So my question is, the byte cod
Hi all
Because the deadline is imminent and because we have only received some
proposals, we have extended the current deadline. The new submission deadline is
2015-12-20.
Call For Proposals
==
This is the official call for sessions for the Python devroom at FOSDEM 2016.
FOSDEM
Hi all
Because the deadline is imminent and because we have only received some
proposals, we have extended the current deadline. The new submission deadline is
2015-12-20.
Call For Proposals
==
This is the official call for sessions for the Python devroom at FOSDEM 2016.
FOSDEM
Just inform you that the deadline for the CfP of the PythonFOSDEM will
finish this evening.
If you have a last talk to submit, please do it.
Call For Proposals
==
This is the official call for sessions for the Python devroom at FOSDEM 2016.
FOSDEM is the Free and Open source So
On 01/10, Brett Cannon wrote:
> For those of you who have not heard, I made the decision a little over a
> week ago to move Python's development from our home-grown workflow to one
> hosted on GitHub (mainly for code hosting and code review; we're keeping
> bugs.python.org for our issue tracker). T
Hi everyone,
With my talk "Exploring our Python Interpreter", I think this VIM plugin
can be useful for the community. It's a syntax highlighter for the C API
of CPython 3.5 and 3.6. I used Clang for the parsing and automatically
generated the keywords for VIM.
PyObject and the others typede
Hi all,
How are you? I am fine ;-) and you?
So, on this morning I was playing with the github interface and the
pull requests of CPython and I have discovered the advanced search of
Github and I think this one is really useful for us and certainly for
the core-dev.
So, I was interested by somes
On 10/20, Victor Stinner wrote:
Le ven. 19 oct. 2018 à 19:01, Stephane Wirtel a écrit :
total: 49 PRs
is:open is:pr review:approved status:success label:"awaiting merge" -label:"DO-NOT-MERGE"
label:""LA signed""
I merged many PRs and closed a few (
Good morning/afternoon/evening/night ;-)
In the documentation of os.system [1], there is this paragraph, where we
suggest to use subprocess instead of os.system.
"""
The subprocess module provides more powerful facilities for spawning new
processes and retrieving their results; using that module
os.system when we only need a call without portability, just a
quick code.
+1 for subprocess for the portability.
Thank you so much for your patience/time and your explanations.
Stéphane
On 10/24, Stephane Wirtel wrote:
Good morning/afternoon/evening/night ;-)
In the documentation of os.system
In this PR [https://github.com/python/cpython/pull/3382] "Remove reference to
address from the docs, as it only causes confusion", opened by Chris
Angelico, there is a discussion about the right term to use for the
address of an object in memory.
If you are interested by the topic, you could comm
Hi all,
When we receive a PR about the documentation, I think that could be
interesting if we could have a running instance of the doc on a sub
domain of python.org.
For example, pr-1-doc.python.org or whatever, but by this way the
reviewers could see the result online.
The workflow would b
On 11/04, Ned Deily wrote:
On Nov 4, 2018, at 08:38, Stephane Wirtel wrote:
When we receive a PR about the documentation, I think that could be
interesting if we could have a running instance of the doc on a sub
domain of python.org.
For example, pr-1-doc.python.org or whatever, but by
On 11/04, Julien Palard wrote:
Considering feedback from Ned, what about building this as an
independent service? We don't really need to interface with python.org
at all, we just need some hardware, a domain, some code to interface
with github API and... to start it's probably enough? It would b
On 11/05, Chris Angelico wrote:
On Mon, Nov 5, 2018 at 2:11 AM Julien Palard via Python-Dev
wrote:
Considering feedback from Ned, what about building this as an independent
service? We don't really need to interface with python.org at all, we just need
some hardware, a domain, some code to i
On 11/04, Steve Dower wrote:
On 04Nov2018 0718, Chris Angelico wrote:
On Mon, Nov 5, 2018 at 2:11 AM Julien Palard via Python-Dev
wrote:
Considering feedback from Ned, what about building this as an independent
service? We don't really need to interface with python.org at all, we just need
On 11/04, Serhiy Storchaka wrote:
04.11.18 17:00, Julien Palard via Python-Dev пише:
Considering feedback from Ned, what about building this as an independent
service? We don't really need to interface with python.org at all, we just need
some hardware, a domain, some code to interface with gi
On 11/05, Chris Angelico wrote:
On Mon, Nov 5, 2018 at 2:33 AM Stephane Wirtel wrote:
On 11/05, Chris Angelico wrote:
>On Mon, Nov 5, 2018 at 2:11 AM Julien Palard via Python-Dev
> wrote:
>>
>> Considering feedback from Ned, what about building this as an independent
servic
On 11/05, Steven D'Aprano wrote:
On Sun, Nov 04, 2018 at 04:12:39PM +0100, Stephane Wirtel wrote:
My workflow is the following steps:
git wpr XYZ
cd ../cpython-XYZ
./configure --prefix=$PWD-build --with-pydebug --silent
make -j 4 -s
make PYTHON=../python -C Doc/ venv
make -C Doc/
On 11/04, Mariatta Wijaya wrote:
I think the intent is just uploading the output HTML and static assets.
Yep, it's my idea, just upload the output html and static assets,
nothing else.
I agree having the temporary output of PR docs build is useful, but I don't
think a python.org domain is nece
On 11/04, Mariatta Wijaya wrote:
This will make review turnout quicker, since I can potentially review and
view the output from anywhere (phone while on a beach) instead of waiting
until I'm back home, open a computer, and then verify the output myself.
Yep, last week I was at a dinner at PyCon.
On 11/04, Paul Ganssle wrote:
Oh, sorry if I misunderstood the concern. Yes, I agree that putting this
under python.org would not be a good idea.
Either hosting it on a hosting provider like netlify (or azure if that's
possible) or a dedicated domain that could be created for the purpose
(e.g. p
On 11/04, Ned Deily wrote:
On Nov 4, 2018, at 10:12, Stephane Wirtel wrote:
3. On this after-noon, I have reviewed a PR, and I was in the same case,
download the PR, build python, compile the doc and run the local server.
My workflow is the following steps:
git wpr XYZ
cd ../cpython-XYZ
Mariatta,
Do you think we could add a webhook for the build of the documentation
for each PR where the build of the doc works?
Stéphane
--
Stéphane Wirtel - https://wirtel.be - @matrixise
___
Python-Dev mailing list
Python-Dev@python.org
https://mail
Really sorry Serhiy, hope the best for you, take care. Firstly the most
important thing, is your health.
Stéphane
> Le 19 janv. 2019 à 23:25, Mariatta Wijaya a écrit :
>
> Sorry to hear that. Please take care.
>
>> On Sat, Jan 19, 2019, 4:15 AM Serhiy Storchaka > I have virtually completely
Hi all,
After a git pull, I have seen there is a merge for v3.8.0a1 by Łukasz
Langa, why? I think the code should keep a linear commit and in this
case, it's against the "commit&squash" of CPython and Github :/
Thank you for your response.
Stéphane
--
Stéphane Wirtel - https://wirtel.be - @mat
On 02/04, Łukasz Langa wrote:
On 4 Feb 2019, at 11:58, Stephane Wirtel wrote:
Hi all,
After a git pull, I have seen there is a merge for v3.8.0a1 by Łukasz
Langa, why? I think the code should keep a linear commit and in this
case, it's against the "commit&squash" of
On 02/04, Łukasz Langa wrote:
I packaged my first release. *wipes sweat off of face*
Go get it here:
https://www.python.org/downloads/release/python-380a1/
Python 3.8.0a1 is the first of four planned alpha releases of Python 3.8,
the next feature release of Python. During the alpha phase, Pyth
It's unofficial but I used the Dockerfile for 3.7 and created this
Docker image:
https://cloud.docker.com/u/matrixise/repository/docker/matrixise/python
docker pull matrixise/python:3.8.0a1
I am not an expert about the releasing of a Docker image but we could
work with that and try to improv
On 02/04, Stephane Wirtel wrote:
It's unofficial but I used the Dockerfile for 3.7 and created this
Docker image:
https://cloud.docker.com/u/matrixise/repository/docker/matrixise/python
Sorry: here is the right link
https://hub.docker.com/r/matrixise/python
--
Stéphane Wirtel -
Hi Łukasz,
I have some issues with pytest and this release, you can see this BPO
https://bugs.python.org/issue35895
Have a nice day and thank you for your job.
Stéphane
--
Stéphane Wirtel - https://wirtel.be - @matrixise
___
Python-Dev mailing list
Hi Barry,
I was not aware of this image. So it's true that it's very useful.
Thank you very much,
Stéphane
On 02/04, Barry Warsaw wrote:
On Feb 4, 2019, at 05:02, Stephane Wirtel wrote:
Just one idea, we could create a Docker image with this alpha version.
This Docker image cou
On 02/05, Barry Warsaw wrote:
On Feb 5, 2019, at 02:24, Stephane Wirtel wrote:
You’re welcome! I just pushed an update to add 3.8.0a1 to the set of Python’s
(including git head). Do you think there’s a better way to publicize these
images?
I know that Julien Palard wanted a docker image
On 02/06, Petr Viktorin wrote:
On 2/6/19 8:43 AM, Stephane Wirtel wrote:
On 02/05, Barry Warsaw wrote:
On Feb 5, 2019, at 02:24, Stephane Wirtel wrote:
You’re welcome! I just pushed an update to add 3.8.0a1 to the set
of Python’s (including git head). Do you think there’s a better
way to
Sorry Petr,
I didn't see this message with the test suites.
--
Stéphane Wirtel - https://wirtel.be - @matrixise
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/
Hi Petr,
I would like to add this issue from the devguide where I ask if we need
to use python or python3 in the documentation.
https://github.com/python/devguide/issues/208
--
Stéphane Wirtel - https://wirtel.be - @matrixise
___
Python-Dev mailing li
Hi all,
I wanted to test with the new version of SQLite3 3.27.1 and there is no
issue (compiled with a debian:latest docker image and the last version
of 3.27.1).
Sorry, it's not a bug, I wanted to inform you there is no issue with the
last stable version of SQLite3.
Have a nice week-end,
St
Nice, we could start to fix the Android issues with this docker image,
maybe modified with the local repository but really useful.
Thank you so much for your job.
--
Stéphane Wirtel - https://wirtel.be - @matrixise
___
Python-Dev mailing list
Python-De
Hi Xavier,
I get this exception
Timeout (360 seconds) reached; failed to start emulator
---> Device ready.
---> Install Python on the emulator.
/home/pydev/build/python-native/python -B
/home/pydev/abifa/Android/tools/install.py
error: device 'emulator-5556' not found
unzip -q /home/pydev/dist/
Hi,
As you know, Python 3.4 and 3.5 are in security mode and the EOL for
these versions are respectively 2019-03-16 and 2020-09-13.
Number of issues
3.4: 1530 issues
3.5: 1901 issues
But some issues are not related to the security.
Could we update these issues (non-security) to 3.6/3.7 & 3.8?
After discussion with Victor, my proposal will generate noise with the
ML, maybe for nothing.
On 02/20, Stephane Wirtel wrote:
Hi,
As you know, Python 3.4 and 3.5 are in security mode and the EOL for
these versions are respectively 2019-03-16 and 2020-09-13.
Number of issues
3.4: 1530 issues
I am against a mass changing the status of issue, since this will
generate an enormous amount of noise (to me at least). But you are
free to update issues one by one if you can to do some progress with
them.
Sure, I don't want to update them massively, just one by one.
But I prefer to ask befor
Hi Steve,
I reply on the mailing list
On 02/20, Steve Dower wrote:
It'll make same noise, sure, but if we schedule a bulk close of issues
that have not been touched since 3.6 was released then at least it'll be
easy to "mark all as read". And searching for current issues will become
easier.
As
Hi,
What do you think if we suggest a "template" for the new bugs?
For example:
* Python version (exact version)
* Operating System
* on Linux -> Distribution (python can have some patches)
* Add a script for the reproduction of the bug
* Eventually, try with the docker images (on i386,x86_64
+1
> Le 21 févr. 2019 à 21:06, Steve Dower a écrit :
>
>> On 21Feb2019 1117, Barry Warsaw wrote:
>>> On Feb 21, 2019, at 10:34, Raymond Hettinger
>>> wrote:
>>>
>>> I think that anything that raises the cost of filing a bug report will work
>>> to our detriment. Ideally, we want the barriers
Hi Łukasz,
Thank you for your job.
I have created a Merge Request for the docker image of Barry [1].
I also filled an issue [2] for brotlipy (used by httpbin and requests).
The problem is with PyInterpreterState.
Via Twitter, I have proposed to the community to fix the issue [2].
[1]: https:/
Thank you Stéphane! This is now merged and the updated image is available.
Thank you to you Barry.
I have proposed an idea where we could generate the new image without
any human action, excepted when there is a fail with the build
step.
Cheers,
Stéphane
--
Stéphane Wirtel - https://wirtel.
I don't know if Julien Palard is on this mailing list, but maybe he
could be interested by this initiative.
On 04/15, Senthil Kumaran wrote:
Hello Python Developers,
Google is running a program called Season of Docs (
https://developers.google.com/season-of-docs/) to encourage technical
writers
Congratulations Brett,
Thank you so much for this job.
> On 22 juil. 2016, at 10:04 PM, Brett Cannon wrote:
>
> https://github.com/python/devguide
>
> I have also moved all issues over as well and hooked up Read The Docs so that
> there's a mirror which is always up-to-date (vs. docs.python.o
Because the deadline is imminent and because we have only received some
proposals, we will extend the current deadline. The new submission deadline is
2016-12-18.
Call For Proposals
==
This is the official call for sessions for the Python devroom at FOSDEM 2017.
FOSDEM is the Fr
Hi,
Thank you for this post to python-dev.
About my talk, it was a real pleasure to give it at PyCon Canada, and I
hope I could propose it to PyCon US for a larger public.
But the goal behind this talk was to show that we have a good community,
firstly by the external contributors and by the cor
Hi Mariatta,
Thank you, I was really happy to see you at my talk, usually this kind
of talk is boring ;-) just kidding, but usually I prefer a technical talk.
Le 05/12/17 à 16:25, Mariatta Wijaya a écrit :
> I saw the talk in person :) Congrats Stéphane!
>
> You can get the reviews from a spec
On 01/24, Steve Holden wrote:
I've just start using CLion from JetBrains, and I wondered if anyone on the
list is using this product in CPython development. Links to any guidance
would be useful.
regards
Steve Holden
Hi Steve,
I tried to use it for CPython, but it uses CMake and not the autot
This mailing list is for the development of CPython, not for the end
user, please could you move your question on python-l...@python.org ?
Thank you,
Le 22/03/18 à 07:27, Rohit Adhikari a écrit :
> Do we have vlookup function which can be used in dataframe same as used
> in excel.
> Can you pleas
Hello, this week-end is the last two days for the Call For Proposals of
PythonFOSDEM 2017. We have received a lot of topics, but if you want to
become a speaker and that you have a very cool topic to submit, please
don't hesite and send us your proposal.
Deadline is 2016-12-18.
Stephane
Cal
Nice, good news.
On 02/07, Brett Cannon wrote:
To let the non-core devs know, the GitHub migration will be happening this
Friday. For those of you who use the current GitHub mirror to create
patches, do be aware that the hashes will most likely be changing so don't
expect your checkout to work
there is the Peephole for that, it's a small optimizer in the compiler.
On 05/24/2017 08:07 PM, Ben Hoyt wrote:
Hi folks,
I was looking at some `dis` output today, and I was wondering if anyone has
investigated optimizing Python (slightly) by adding special-case bytecodes
for common expressions
58 matches
Mail list logo
