Access to the Python results is currently down, but has anyone
actually accessed the Coverity scan results any time recently? Or who
even has access anymore?
Hello Python Committers,
As usual we will hold a Python Language Summit before the PyCon US conference.
The language summit will be in the conference hotel, to discuss the ongoing development of the Python language. It will be held on the *Wednesday* before the conference (Wednesday 7th March), a change from previous years.
The language summit is an invite only event. All Python core developers, plus selected others, are invited. If you would like to attend, for all or part of the day, please respond off list to me so I can keep a track of numbers.
If you have topics you would like to see on the agenda please also let me know.
I'll send more details on the event, times and the location within the venue, nearer the date.
All the best,
Michael Foord
--
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
Hello all,
The Python language summit at PyCon 2012 will soon be upon us.
I have one volunteer to act as a scribe for the event and write up notes afterwards. It would be best to have at least one more person taking notes and able to write them up, as one person won't get all of the discussion of interest.
Do we have anyone willing to setup "video streaming", similar to what will be done for the PSF meeting? If anyone is willing to take this on, Marc-Andre should be able to help with the technical details.
We're not usually short of topics to discuss, but the only specific idea for the summit agenda I have so far is "namespace packages". We have two competing PEPs for Python 3.3, so it makes a good topic for discussion.
Experimental packages are another potential topic. We have some candidates for packages that some would like to see in the standard library, but marked in the documentation as experimental and with reduced guarantees on API stability.
Another topic worthy of discussion is the proposed changes to the release cycle, if no decision has been made by the summit.
If you have any other topics you think would be good to discuss please let me know.
All the best,
Michael Foord
--
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
Hi Michael:
Thank-you for submitting your contributor agreement.
It has been added to the online PSF bug tracker.
Pat Campbell
PSF Secretary
On Thu, Jan 12, 2012 at 1:26 PM, Michael Goderbauer <contact(a)m-goderbauer.de
> wrote:
> Hello,
>
> attached you will find my signed contributor agreement.
>
> Regards,
> Michael Goderbauer
>
--
Pat Campbell
PSF Administrator/Secretary
patcam(a)python.org
Hi Jyotirmoy:
Thank-you for submitting your contributor agreement.
Your contributor agreement form has been added to the online
PSF bug tracker.
Pat
On Sun, Jan 8, 2012 at 12:22 AM, Jyotirmoy Bhattacharya <
jyotirmoy(a)jyotirmoy.net> wrote:
> Please find attached a scan of my signed contributor agreement.
>
> Regards,
> Jyotirmoy Bhattacharya
>
--
Pat Campbell
PSF Administrator/Secretary
patcam(a)python.org
I think, there is something wrong with state of hg.python.org at the moment.
On a fresh clone from hg.python.org
$hg clone ssh://hg@hg.python.org/cpython cpython
If I do, hg branches, the 3.2 is shown as inactive. Did something
change recently?
(env27)bash-3.2$ hg branches
default 74263:8f7c4b16c8d7
2.7 74256:789d59773801
3.2 74262:b8f978aa2614 (inactive)
3.1 74253:fb5707168351 (inactive)
2.6 73245:62fa61f2ee7d (inactive)
2.5 73244:b48e1b48e670 (closed)
3.0 68249:4cd9f5e89061 (closed)
legacy-trunk 68241:b77918288f7d (closed)
2.4 68239:ceec209b26d4 (closed)
2.3 68237:364638d6434d (closed)
2.2 68235:61b0263d6881 (closed)
2.1 68233:e849d484029f (closed)
2.0 68231:5fd74354d73b (closed)
The problem is when I clone cpython to 3.2, update 3.2, make changes,
commit , it creates a new head when I try to commit, it asks me to
merge
Workflow (which is supposed to work seamlessly and had been working
till my last commit a week ago).
$hg clone cpython 3.2
$cd 3.2
$hg update 3.2
$hg branch
3.2
$#make changes
$hg commit
# gives a msg saying one head created. Which is wrong.
$hg push
...
searching for changes
abort: push creates new remote heads!
(did you forget to merge? use push -f to force)
Was there any wrong merge? Or am I doing something wrong?
--
Senthil
