
Recherche avancée
Autres articles (106)
-
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)
Sur d’autres sites (13726)
-
Terminal text becomes invisible after terminating subprocess
22 mai 2022, par wimAfter terminating an
ffmpeg
subprocess, the terminal gets messed up - typed characters are invisible ! The input still works in that commands can be executed, but keyboard input is not echoed to the terminal.


Issuing shell command
reset
puts everything back to normal (or!reset
from within ipython), so a workaround the issue is callingos.system('reset')
inside the script.


Other things I've tried :
import curses; curses.initscr()
before spawning the subprocess andcurses.endwin()
after termination, which worked somewhat but broke other stuff. Another possibly related issue is that after spawning the child process, the interactive terminal becomes laggy and sometimes fails to capture typed characters.


The code to spawn the process looks like :



with open('/tmp/stdout.log', 'w') as o:
 with open('/tmp/stderr.log', 'w') as e:
 proc = subprocess.Popen([args], stdout=o, stderr=e)




And later to stop it :



proc.terminate()
proc.communicate()




What could be going wrong here ?


-
Anomalie #3429 (Nouveau) : Incohérence du 2è paramètre du critère `{pagination}`
16 avril 2015, par marcimat ☺☮☯♫Hop,
Je viens de tomber sur un truc curieux, reproductible simplement.
Lorsqu’on demandedebutX=@identifiant
à une boucle pagination, cela ne fonctionne que si on a une balise en 1er ou 2è argument du critère pagination :-
{pagination #VAL{10} X}
fonctionne,
-{pagination 10 #VAL{X}}
fonctionne,
- mais pas{pagination 10 X}
;Le nombre 10 est pourtant bien pris en compte dans les 3 situations finalement ; mais pas le ’X’ dans le dernier cas.
Plus précisément le critère pagination croit lire dans le dernier cas un nombre ’10 X’ qu’il transforme en 10 avec un strval(). Mais il perd l’info X.Du coup, la variable créée est debutX dans les premiers cas, et
debut_{NOM_BOUCLE}
dans le dernier.Une solution pourrait être d’accepter (et préférer) l’écriture
{paginaiton N, X}
? -
The new FOMS : Open Media Developers at OVC
13 août 2011, par silviaSince 2007 I have organised the annual Foundations of Open Media Software (FOMS) developers workshop. Last year it was held for the first time in the northern hemisphere, in fact on the two days straight after the Open Video Conference (OVC). This year I’m really excited to announce that the (...)